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

Fall back to displaying SymbolServer indexing progress on stderr #707

Merged
merged 1 commit into from
May 23, 2020

Conversation

ffevotte
Copy link
Contributor

Users of fully-capable clients (such as VS code) get a sense of the progress being made by SymbolServer while indexing packages. However, clients which don't have the capability to display progress notifications get no information whatsoever. This proposal falls back to simply displaying indexing progress on stderr for such clients.

This helps at least when using the LanguageServer within Emacs via eglot, which allows to easily display the server output for debugging purposes. I'm not sure whether there are other clients for which such additional output would be unwelcome...

Users of fully-capable clients (such as VS code) get a sense of the progress being made by `SymbolServer` while indexing packages. However, clients which don't have the capability to display progress notifications get no information whatsoever. This proposal falls back to simply displaying indexing progress on stderr for such clients.

This helps at least when using the `LanguageServer` within Emacs via `eglot`, which allows to easily display the server output for debugging purposes. I'm not sure whether there are other clients for which such additional output would be unwelcome...
Copy link
Member

@davidanthoff davidanthoff left a comment

Choose a reason for hiding this comment

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

Nice, this is a good idea!

@davidanthoff davidanthoff merged commit 75e7d59 into julia-vscode:master May 23, 2020
@ffevotte ffevotte deleted the patch-1 branch May 23, 2020 19:34
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.

None yet

3 participants