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

Support outline and labels resolved from main source file #27

Open
peterdell opened this issue Feb 3, 2025 · 0 comments
Open

Support outline and labels resolved from main source file #27

peterdell opened this issue Feb 3, 2025 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@peterdell
Copy link
Collaborator

peterdell commented Feb 3, 2025

When working with includes, the outline and the label resolution only parse the file that are included into the current file via a source include directive. This has the effect that when editing an included file, the definitions of parent or brother files in the include tree are not visible. This is a major issue in larger projects with multiple include files.

The ideal solution would be to always start the parsing in the main source file, if specified in the include. The parsing should also take open documents in open editors into account. This will require to keep track of the different documents that are already opened. Also the user might want to select in the outline, if the displayed tree should started in the main source file or the current source file.

A minimal solution would be to tread the main source file annotation is source include directive and to only look into saved version of every file.

A simple workaround is to include the main source file in a block that is never assembled.

Image

@peterdell peterdell added the enhancement New feature or request label Feb 3, 2025
@peterdell peterdell self-assigned this Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant