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.

Sign up for GitHub

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

Jump to bottom

Question: reasoning behind only_hint #35

Open
gegoune opened this issue Jan 6, 2021 · 1 comment · May be fixed by #41
Open

Question: reasoning behind only_hint #35

gegoune opened this issue Jan 6, 2021 · 1 comment · May be fixed by #41

Comments

@gegoune
Copy link

gegoune commented Jan 6, 2021

Hi, 8fb7cc4 introduced example statusline. I am struggling to understand why only_hint is in there. What is special about hints that they are not having space prefix? I want to have a space in front of displayed diagnostics and all but hint have one (that is if only hint is displayed). Had to add an ugly workaround in my statusline configuration to get what I want.

I am not displaying symbol (lsp_status.config({status_symbol = ""})) if that makes any difference.
@wbthomason
Copy link
Collaborator

Ah - if I recall correctly, this was because my setup uses a double-wide character for the hint symbol and status symbol, which meant that having a space character between those two made the spacing look off. The default statusline module came right from my statusline setup, so this artifact probably got carried over. I'd be OK merging a change to remove this special casing, as long as we can ensure that the spacing still looks right for the default set of symbols.

@wbthomason wbthomason linked a pull request Mar 3, 2021 that will close this issue
Always add a space after status_symbol #41
Open
@wbthomason wbthomason linked a pull request Mar 3, 2021 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Always add a space after status_symbol nerosnm/lsp-status.nvim
2 participants
@wbthomason @gegoune