Skip to content

Conversation

@genericptr
Copy link
Owner

@genericptr genericptr commented Jan 10, 2026

@mvancanneyt It was broken since your refactor but I fixed the usage of the includeWorkspaceFoldersAsUnitPaths which was supposed to add unit paths to FPCOptions. This for projects without lazarus so that you can open a workspace and it can find files for you with adding them manually.

My question is, how does this interact with the lazconfig system? I'm looking in PasLS.LazConfig.pas and I don't see how it sets unit paths. Now that this is working I think it's going to conflict with the lazconfig.

@genericptr genericptr linked an issue Jan 10, 2026 that may be closed by this pull request
@mvancanneyt
Copy link
Collaborator

It won't conflict. The two systems are completely parallel. it just means many paths will be supplied twice.

Looking at the diff, it seems to me you simply didn't set the
``ServerSettings.includeWorkspaceFoldersAsUnitPathsorServerSettings.includeWorkspaceFoldersAsIncludePaths`
to true.

But I'd need to investigate more deeply. The diffs are not very clear, mixing formatting and functional changes...

In each case, The lazconfig system needs an update. Today you can simply use '/path/to/workspace/**' and the lazarus codetools will automatically add all subdirectories. So no special code required.

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

Successfully merging this pull request may close these issues.

Workspaces directories in server are not being found

3 participants