Line breaking in Ruby

line_break1.rb

# Example 1
# Lets assume following line is longer than 80 cols and I want it to break it

Foobar.some_method.another_on(:with_some => :arg, :and_another => "one")

# Variant 1

Foobar.some_method.another_on(
  :with_some => :arg, :and_another => "one"
)

# Variant 2

Foobar.
  some_method.
  another_on(:with_some => :arg, :and_another => "one")

# Variant 3

Foobar.some_method.another_on(:with_some => :arg,
                              :and_another => "one")

# Variant 4

Foobar.some_method.another_on(:with_some => :arg,
  :and_another => "one")

# What would you do?

line_break2.rb

# Example 2
# Lets assume following line is longer than 80 cols and I want it to break it

@asciicasts = Asciicast.order("created_at DESC").page(params[:page]).per(PER_PAGE)

# Variant 1

@asciicasts = Asciicast.
                order("created_at DESC").
                page(params[:page]).
                per(PER_PAGE)

# Variant 2

@asciicasts = Asciicast.order("created_at DESC").page(params[:page]).
                        per(PER_PAGE)

# Variant 3

@asciicasts =
  Asciicast.order("created_at DESC").page(params[:page]).per(PER_PAGE)

# Variant 4

@asciicasts = Asciicast.order("created_at DESC").page(params[:page]) \
                       .per(PER_PAGE)

# What would you do?

line_break3.rb

# Example 3
# Lets assume following line is longer than 80 cols and I want it to break it

Foobar.some_method.another_on(positional_arg, :with_some => :arg, :and_another => "one", :foo => "barbazzz")

# Huh, now what? :P

File 1: variant 1 if I had to choose, but I'd rather do:

Foobar.some_method.another_on(
  :with_some => :arg,
  :and_another => "one"
)

File 2: variant 1 or 2, but first I'd try to do anything to avoid that, e.g.

@page = params[:page]
@asciicasts = Asciicast.order("created_at DESC").page(@page).per(PER_PAGE)

@psionides +1, that's also the recommended scala style. We're using it in our projects and it's really nice to read :)

@psionides @ktoso: see line_break3.rb also, it's more challenging ;)

same thing, break line after ( and each ,. Consistency in style is important, there's no "what about this case?" ;)

Either as @ktoso says or leave positional_arg in the first line and then each key-value pair on a new line.

Agree on guys opinions above; one note from myself is I really hate breaking lines like in examples:

File 1: variant 3
File 2: variant 1 (what determines indentation here?), 2, 4

Nesting is two spaces per level. Period.

+1 @psionides. I do that in JS as well.