get_project_path() incorrectly determines path about lsp HOT 5 CLOSED

I suspect they'll add support to the Language Server protocol at some point

It appears they've got early work underway on this: microsoft/vscode-languageserver-node@c3a880f

from lsp.

Thanks for the detailed bug report, sounds like commonpath is the intended behaviour.

I am myself not convinced of LSP's shared-root-of-multiple-folders approach, but would only supporting the first folder be an improvement?

from lsp.

would only supporting the first folder be an improvement?

I definitely think so; the way I use Sublime projects typically is by having a main directory with multiple auxiliary directories for easy access (for example, a component of a large system along with the core library for said system). Having all of it integrated would be nice, but in lieu of that, just using the first folder I think is the best behaviour (and matches VS Code's current behaviour).

from lsp.

Filed #81 which switches to the first folder approach; if you'd prefer to keep the common parent approach, I can switch it over to commonpath instead.

from lsp.

(Here's the actual draft spec for multi-root support, btw: https://github.com/Microsoft/vscode-languageserver-node/blob/master/protocol/src/protocol.workspaceFolders.proposed.md )

from lsp.