You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the report. I am a bit suprised about that because I though I already covered this case.
Also, when I check the code, in the read_shebang function, I first check if the line starts with #!, then I take the rest of the line and strip. So whether or not there is a space after the #! should work.
I'll try to test that soon but since I don't really use Atom anymore, I don't know when this will be.
Don't hesitate to provide a code change if you figure it out.
I just check those 2 cases you provided and I am not able to reproduce the issue. It works in both cases for me.
Something even more suprising is that it keeps working when I disable my plugin. So I wonder if this plugin is still useful for Atom or if Atom now embeds this feature as "core".
From the examples and tests I see that only examples where a space is after the shebang works.
#! /usr/bin/env python
==> works#!/usr/bin/env python
==> brokenThe latter did not work for me. I have a file with
#!/usr/bin/env ruby
I briefly looked that the code, but fail to find the specific place in the detection regext/splitting that could fix it.
Can you do it?
Background read: https://unix.stackexchange.com/questions/276751/is-space-allowed-between-and-bin-bash-in-shebang
The text was updated successfully, but these errors were encountered: