utf-8 strings and unexpected end-of-input

[zenbro]

Hi!

Every method call with utf-8 string as argument ends with following error:
unexpected end-of-input, expecting keyword_end

ruby -wc returns Syntax OK.

Simple code to reproduce this:

def my_method
  puts 'привет'  # utf-8 string
end

Atom version: 1.12.6
linter-ruby version: 1.2.4
System: macOS 10.12.1
Ruby versions: 2.1.10, 2.2.3, 2.3.3

[zenbro]

Adding # encoding: utf-8 solves the problem.
Btw, ruby installed via rvm.

[zenbro]

Starting atom from terminal also solves the problem.
Seems like problem in environment variables.

[alistairholt]

This is quite irritating. Anyone know why this has recently broken?

[Arcanemagus]

Hmmm, in v1.2.4 the argument sent to Ruby was changed from -E utf-8 to -Eutf-8 (f4a6026) as the first method on my computer (Windows 10 x64 + Ruby v2.3.1p112) attempts to set the language to utf-8 (note the space), which doesn't exist. Maybe Ruby is "special" and handles this differently on different platforms? 😕

@alistairholt what platform are you on?

---

The proper solution is as @zenbro already said: Adding the following at the start of the file:

# encoding: utf-8

This tells Ruby the encoding of the file in the proper method, the argument is only meant to be a fallback to try to catch cases where the developer forgot it.

[timhaines]

@Arcanemagus With Ruby 2.0 utf-8 is the default encoding, and that encoding comment is no longer required.

2.0 Release notes

FWIW I struck this "bug" today too and came looking for a solution. In my case it's thinking ’ is terminating a single quoted string.

[stevehanson]

I'm also seeing this issue. I just quit Atom and restarted from Terminal per @zenbro's recommendation and am not seeing the issue anymore. I'm on MacOS Sierra.

[black-snow]

@timhaines I'm on ruby 2.2.3 and still having this without the encoding-comment.
MacOS Sierra, linter-ruby 1.2.4, atom 1.13.1 x64

[fabien-michel]

/!\ This workaround make linter-ruby to not detect any errors
Workaround : Open the linter-ruby/lib/main.js file and add a space between -E and utf-8 on line 39
const execArgs = ['-wc', '-E utf-8'];

[alistairholt]

@Arcanemagus I'm on macOS Sierra 10.12.3. As @timhaines said, we shouldn't need to add the magic encoding comment as UTF-8 is the default script encoding since Ruby v2.0.

My Ruby (ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-darwin16]) man page shows -E external[:internal]. @fabien-michel 's change fixed my issue.

[wdspkr]

I tried @fabien-michel 's workaround and that actually leads to the linter not working anymore: The unexpected end-of-input error vanishes, but so do all other real errors!

The only way to get the linter working correctly for me right now is @stevehanson 's solution: Restarting atom from the terminal.

[alistairholt]

@wdspkr which platform are you on and which Ruby are you running?

[fabien-michel]

@wdspkr You are true, I've updated my comment to warn readers