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

[SUGGESTION] $FILEPATH etc. in LSP Client #284

Closed
NullPlane opened this issue Jun 10, 2024 · 3 comments
Closed

[SUGGESTION] $FILEPATH etc. in LSP Client #284

NullPlane opened this issue Jun 10, 2024 · 3 comments
Assignees
Labels
enhancement New feature or request ready for release

Comments

@NullPlane
Copy link

NullPlane commented Jun 10, 2024

For jdtls specifically they do not enforce but kindly ask to have a project-respective dir in your current working dir or elsewhere. I think some vars in there may be helpful to some LSPs but maybe there are already such and I just did not find them.

@SpartanJ
Copy link
Owner

For the moment we only use $FILENAME which is actually the file path and not the name 😅, I guess I can add $PROJECTPATH, I cannot think any other though. I don't like I used $ALLCAPS, I might add the alternative that we use for the build system, they look like: ${project_root}.

@SpartanJ SpartanJ self-assigned this Jun 10, 2024
@SpartanJ SpartanJ added the enhancement New feature or request label Jun 10, 2024
@NullPlane
Copy link
Author

Ya I actually meant that. The problem is that some lsps want to store data in a given path individual to the project itself and it would be nice to have some kind of way to tell whether there is a single file opened or a folder as a project etc.

@SpartanJ
Copy link
Owner

Added ${project_root} (or $PROJECTPATH) as keywords for commands in LSP, Formatter and Linter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request ready for release
Projects
None yet
Development

No branches or pull requests

2 participants