Keep it work if paren exists after receiver

[pocke]

Update

This PR focus on paren only. The following description is obsolate.

---

This pull request fixes a problem that this gem doesn't work if parens, comments, and/or backslashes exist after the receiver.

It is under WIP because I need to support other nodes such as OPCALL.

Problem

This gem doesn't display ^^^ if any non-space characters that don't make node exist. For example:

(42).time

42
  # comment
  .time

42 \
  .time

The syntaxes don't make RubyVM::AST node, so nd_recv.last_column doesn't mean the position Immediately before the dot.

[ujihisa]

(Another example:

<<"this is a pen"; p 42
this is a pen
  .times

)

[mame]

Thank you for the report. I think it is enough to care only parens.

Actually I was aware that it does not work well when there is a comment or a backslash between the receiver and ., but I believe that such code is rare. Even in such a case, this gem shows no snippet, which is not a big deal, IMO. But I agree that it is good to support (42).time.

[pocke]

Thanks for your replies.

I agree with @mame. The regexps will be too complicated but there are only a few benefits. If we need to support them, it should be solved with RubyVM::AST improvements, such as node.pos(:method_name).first_column, but not regexp.

I'll update this pull request to only support (42).time case.

---

Just FYI, there is the same problem with multiline comment between . and method name. (and It is a super super rare case!)

42.
=begin
comment
=end
  time

[pocke]

I've updated this pr to support only parens, and updated for all nodes that were broken on parens.