Closed paaguti closed 1 year ago
Alternatively, one could define a couple of hidden files you could create with touch xxx
to mark a directory as a project root and include those in io.get_project_root()
. I'm experimenting with that too.
I'm using .lsp_root
, but .prj_root
could also be a nice candidate... less LSP-oriented, right?
So, I did it ;-). So far checked with my $HOME/bin, where I have "a couple" scripts and it works like a breeze.
I'm glad you were able to get it working for you :)
If I need a directory to be recognized as a project root, I just create a '.hg' or '.git' directory there, even if I have no intention of using version control. It's easier than defining another convention, as is being done here. Too much to keep track of... I might be open to falling back on the file's directory as an LSP root, but I'm concerned that a language server would start creating metadata directories everywhere.
Hmm good point :-) a couple of words in the README wouldn’t harm ;-)
/PA
Enviado desde mi iPhone
El 7 nov 2022, a las 16:05, orbitalquark @.***> escribió:
I'm glad you were able to get it working for you :)
If I need a directory to be recognized as a project root, I just create a '.hg' or '.git' directory there, even if I have no intention of using version control. It's easier than defining another convention, as is being done here. Too much to keep track of... I might be open to falling back on the file's directory as an LSP root, but I'm concerned that a language server would start creating metadata directories everywhere.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.
I also edit scripts outside a control version system and I wanted to be able to use LSP on individual scripts