Skip to content
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

Outline is empty #10

Open
hacklex opened this issue Apr 30, 2023 · 1 comment
Open

Outline is empty #10

hacklex opened this issue Apr 30, 2023 · 1 comment

Comments

@hacklex
Copy link

hacklex commented Apr 30, 2023

Great extension, I've been waiting for long to finally depart from emacs!

I noticed that although ctrl+click / F12 navigation is working, the outline region still says "no symbols defined".

If that's not too much of a problem, can you populate the outline with top-level definitions?

@Johanmyst
Copy link
Contributor

I'm not the developer of this plug-in, but I noticed this as well. However, if I hover over the symbol a second time, the definition is found. I think it is simply because the lookup is only triggered initially when looking it up, and iff it is found, it will only be visible on the next iteration.

However, I also saw this behaviour before (though, the ctrl+click behaviour was also not functional then), and that was due to a lacking *.fst.config.json file. More specifically, the paths that are used in this file are parsed a bit counter-intuitively; in a Low* project with a code, spec, dist, .cache, and .hints directory in the root directory of the project, using relative paths did not work. Though, this could also be because the Low* project is a submodule (and thus subdirectory) in a larger project. However, forcing include paths as absolute paths fixed both the ctrl+click and symbol definition behaviour for me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants