-
Notifications
You must be signed in to change notification settings - Fork 1
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
fortls
could not be spawned when opening atom with a default file
#7
Comments
Hmmm, this is odd. I have the same configuration you have but I have never seen this issue. The only thing I can think of that might cause this is some sort of race condition where the system path is not being set fully before Atom tries to launch |
Thanks a bunch, that fixed the problem! |
Great! I am going to go ahead and close this issue. I will comment here if I am able to track down what might be causing this. Although, I suspect the issue is in an upstream package since it appears to be path related. |
"Can you try setting the path to fortls explicitly in settings and see if that resolves things?" What is the usual location for fortls on MacOS X? |
IDE-Fortran developers,
I have run into a minor bug. If I open up a project with atom, and there is no default source file, everything works great. But let's say I open up from my project file x.f90. Then I close atom. When I reopen that project with atom, x.f90 will be shown in a tab by default. However, in this situation I get a bug
'fortls' could not be spawned
. See the picture below. In this case, IDE-Fortran does not work. However, if I close that default source file, close atom, and reopen atom (now with no default source file), it works fine.My configuration:
macOS 10.13.4
Atom 1.27.2
ide-fortran 0.1.9
fortran-language-server 0.5.0
Let me know if there is any other debug information I can provide.
The text was updated successfully, but these errors were encountered: