Chris Hansen

Sorry for the wait. However, as you said using this code alone in a new project doesn't produce an error. Can you try and produce a reduced test case or...

Unfortunately this package cannot read `*.mod` files for autocomplete information. It only provides autocompletion from source files. Libraries like MPI can be included through [external index files](https://github.com/hansec/autocomplete-fortran#external-index-files), however at the...

The Fortran include files for MPI (and most libraries) only include variable definitions. It would be possible to add those files to the available completions, but it would be limited...

Unfortunately, this package does not include intrinsic functions/subroutines at the moment. There is some support for intrinsics through snippets in the required [language-fortran](https://atom.io/packages/language-fortran) package. This is something I plan to...

Thanks for the report and sorry for the delay. Yes, this shouldn't throw an error since defining multiple "properties" in this way on separate lines is allowed and common place...

Thanks for the suggestion. I have thought about this, but haven't quite decide how useful it would be. In particular I see the following issues: 1) In my experience most...

Interesting, I've never seen that before. Just out of curiosity what is your use case for this feature? I guess there is value in being clear about "where" the value...

Can you try setting the path manually? You can do this by getting the path to `fortls` by running which fortls in a command line. Then use that to set...

Thanks for the suggestion and sorry for the delay. I agree this would be a good feature to have. I'll look into adding it and how it is handled by...

Thanks for the report. Although, I believe that the language server already handles this type of situation. Any functions/subroutines defined in files without modules should be automatically added to the...