-
-
Notifications
You must be signed in to change notification settings - Fork 41
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
bug: Error hovering an associated function #269
Comments
I have a possibly related bug: A function can be Minimal example: program main
! type a or be here:
contains
function a()
!! this shoes up
logical a
a = .true.
end function
logical function b()
!! this doesn't
b = .false.
end function
end program main v2.13.0 in neovim v0.9.0 |
I completely missed this @minhqdao, will have a look |
Traceback:
|
I think the signature is still not ideal i.e. `LOGICAL FUNCTION` but I chose it since it indicates that the associate block variable is the result of a function. Fixes #269
Was the bug I mentioned related, or should I open a new bug report? :) |
Hey @Carltoffel so there is a difference in the hover signatures, but you can always see the documentation. |
Ah, thanks. Then it probably is a problem with the LSP implementation in neovim. |
The inconsistency between the 2 docstrings is tracked in #281. |
I will try and issue a pre-release for v3.0.0 for people to be able to download from PyPi (although the pre-release version will still have a lower precedence over the stable releases, so it won't be installed automatically). In the meantime you can try the latest fortls version which includes a bunch of bug fixes, performance improvements and a new Markdown docstring parser via: pip install git+https://github.com/fortran-lang/fortls.git |
So the new hover results, take the docstrings and assemble them in markdown. Then the client (VSCode, neovim, Emacs, etc. ) Is meant to render that markdown. Not sure why neovim is lagging behind on that https://www.reddit.com/r/neovim/comments/tx40m2/is_it_possible_to_improve_lsp_hover_look/ Currently there is no way to use the old style docs (it was to expensive to maintain both types of docs assembly processes). |
When I use the Modern Fortran plugin in VSCode and hover
hi
in this little piece of code:I get this error message:
The program, however, runs normally and prints:
Specs
13.2.1
, M11.76.2
v3.2.0
, but the same is observed on the pre-release versionv3.4.2023030801
2.13.0
, installed via Homebrew3.11.2
Related Issues: #214, #108
The text was updated successfully, but these errors were encountered: