search

hansec / fortran-language-server

Fortran Language Server for the Language Server Protocol
MIT License
295 stars 57 forks source link

FORTLS not launching (continued) #144

Open AndreHorst opened 4 years ago

AndreHorst commented 4 years ago

With regard to https://github.com/hansec/fortran-language-server/issues/125#issuecomment-526222951

I have this issue now. Same behaviour when starting VSCode it says:

  'ascii' codec can't decode byte 0xe2 in position 12: ordinal not in range(128)

Adding only the subfolder which contains the source files is working! However, this worked before and is now not working anymore. I'm still using Python 2.7.

VSCode Version: 1.39.2 Commit: 6ab598523be7a800d7f3eb4d92d7ab9a66069390 Date: 2019-10-15T15:33:40.634Z Electron: 4.2.10 Chrome: 69.0.3497.128 Node.js: 10.11.0 V8: 6.9.427.31-electron.0 OS: Linux x64 4.9.0-9-amd64

fortran-language-server Version: 1.10.3

FORTRAN IntelliSense Version: 0.6.0

Modern Fortran Version: 2.1.1

Currently, I do not know how to help further. So please tell me how!

hansec commented 4 years ago

Thanks for the report. Can you try doing a debug initialization with the same root directory where you see the error? This should give you a more complete stack trace to show where exactly the error is occurring. Thanks!

AndreHorst commented 4 years ago

Okay I found the issue! I had some new test-data files which containted a forward slash "/" in the filename (which is not a nice thing, I have to admit). So, it was a folder with a content like this:

output/<test-data/1>.dat output/<test-data/2>.dat output/<test-data/3>.dat

This broke the initialization of the fortls. When I removed all forward slashes from the filenames, everything worked as before. I think this should be a minor bug, since nobody should use forward slashes in filenames .... it was just some temporary test data I received.

Blacklight1138 commented 4 years ago

Thanks for the report. Can you try doing a debug initialization with the same root directory where you see the error? This should give you a more complete stack trace to show where exactly the error is occurring. Thanks!

Sorry, I don't understand how to do a debug initialization. When I use fortls --debug_rootpath in terminal I get "fortls: command not found".