Skip to content

Conversation

@TysonAndre
Copy link
Contributor

This prevents more than one language server from starting up at any
point in time.

Fixes #878

pub fn lock_clients_update(&self) -> Fallible<MutexGuard<()>> {
self.clients_mutex
.lock()
.map_err(|err| format_err!("Failed to lock state: {:?}", err))
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This error message shall be update to ... lock client creation

@autozimu
Copy link
Owner

Can you upgrade to take languageId into consideration? Say user invoke vim with vim -p file1.php file2.java, then this change would fail one of the server startup.

Sorry didn't bring up in the first contact.

This prevents more than one language server (per languageId)
from starting up at any point in time.

Fixes autozimu#878
@TysonAndre
Copy link
Contributor Author

Can you upgrade to take languageId into consideration? Say user invoke vim with vim -p file1.php file2.java, then this change would fail one of the server startup.

The review comments have been addressed, this is ready for another look

@autozimu autozimu merged commit cbe7721 into autozimu:next Sep 24, 2019
@autozimu
Copy link
Owner

Thanks!

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.

Multiple language servers get started (and terminated) if vim is started with vim -p

2 participants