-
Notifications
You must be signed in to change notification settings - Fork 251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hashbangs containing /bin/env break if no interpreter is specified #509
Comments
Did this happen directly after upgrading? Or have to restarted Atom since then? |
No. I just installed them from zero. I updated atom to the newer version ( I was on the 1.12.6 vs the current 1.12.9) in hopes for the issue to be solved, but it didn't work. |
Is it happening with specific files, or literally at startup? I noticed it's breaking while scanning hashbangs... are there any files open with interpreter directives? If so, could you copy+paste their hashbangs, please? |
Directly on startup, but Atom opens the last working folder on startup, so it can be the files. I am working on some python files with the classic hashbang #!/usr/bin/env |
Oh shit. I never catered for hashbangs that start with Uhm, that being said, the correct hashbang is actually |
I just tested removing the hashbangs and it works like a charm. Ye I know I didn't add the python at the end because I was sharing the beginning of the line, anyways, thanks for the tip! :) So I guess I should either remove all the hashbangs or start Atom on a "#!/usr/bin/env"-free environment until a new release? |
Both would work, but you could also clone from master and use the fix I just pushed until the next release. :) git clone git@github.com:file-icons/atom.git file-icons
cd file-icons
apm install .
apm link . |
That would work too, yep. Thanks! |
Por nada compa! |
[Enter steps to reproduce below:]
Atom Version: 1.12.9
Electron Version: 1.3.13
System: Ubuntu 16.04.1
Thrown From: file-icons package, v2.0.8
Stack Trace
Uncaught TypeError: Cannot read property 'split' of undefined
Commands
Config
Installed Packages
The text was updated successfully, but these errors were encountered: