Ruby completion still spits out regexes

[jnunemaker]

When I type the following in ruby file:

something do<tab>

I expect this:

something do |<cursor here>|

end

But I get this:

response.each do${1/(^(?<var>\s*[a-z_][a-zA-Z0-9_]*\s*)(,\g<var>)*,?\s*$)|.*/(?1: |)/}variable${1/(^(?<var>\s*[a-z_][a-zA-Z0-9_]*\s*)(,\g<var>)*,?\s*$)|.*/(?1:|)/}

end

Several other tab completion things do the same in ruby.

[jnunemaker]

It has been like this for a while, but I'm trying to be diligent about reporting everything I run into that slows productivity. Feel free to dup it or what not, but I have a terrible time finding related issues in the atom org. Thanks!

[kevinsawicki]

Just to confirm, you would expect:

something do |<cursor here>|

end

and not:

something do
  |<cursor here>|
end

[kevinsawicki]

This shows how bad my ruby is, nevermind.

[kevinsawicki]

I fixed this one but other ones may still have a similar issue until we fully support TextMate snippets, refs #483

[jnunemaker]

The syntax for this is:

something do |some_var|
  puts some_var
end

So ideally it selects the contents between the pipes on the first tab and the second tab would be right before where the puts line is, if that makes sense.

[kevinsawicki]

@jnunemaker Can you grab atom 0.41.0 from atom.io and give it a spin and see if you like the new do snippet?

[jnunemaker]

@kevinsawicki I could 👄 you.

[jnunemaker]

👏 👏 👏 👏 👏 👏 👏 👏 👏 👏 👏 👏 👏 👏 👏 👏 👏 👏

[lock]

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!