-
-
Notifications
You must be signed in to change notification settings - Fork 861
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
Feature Request: re-arrange mode line order #2571
Comments
Do you see any issues with that @yyoncho, also we could take the opportunity to fix that spacing issue in modeline (add space to the left instead of right, something like that) |
I think that we should group all lsp-mode related modeline stuff in a separate variable(e. g. lsp-modeline-string) instead of using global-mode-string and then place it on the modeline probably before the major mode list similar to what evil-mode does(I guess there are other packages doing that). When we do so, we are much more in control to do the proper spacing because only lsp-mode will use that variable. |
For reference, here it is mode-line-format on my side
|
Yeah this looks a good idea, doom-modeline does that similar |
doom-modeline will have to be fixed separately I guess. |
FWIW until the issue is fixed one can use |
#2567 brought in a much-improved progress reporting widget.
But it highlighted for me a niggling issue. All the interesting stuff reported in the mode line by
lsp-mode
comes right at the end of the mode line, where for me most of the time it is invisible. (I use a fairly "vanilla" setup, tweaked slightly with the excellentblackout
package to remove or shorten displayed items)The legacy progress reporting modified the mode lighter, which is far to the left, so visible even when you have many windows open side by side. With the progress added to
global-mode-string
, it has moved to the end.Perhaps we should consider moving the
lsp-mode
information to the left, between vc-info and mode info.Using lsp-mode at: abac0d7
The text was updated successfully, but these errors were encountered: