-
-
Notifications
You must be signed in to change notification settings - Fork 198
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
feat: Add option statusLineSeparator
#1521
feat: Add option statusLineSeparator
#1521
Conversation
Separator used by statusline
package.json
Outdated
}, | ||
"vscode-neovim.statusLineSeparator": { | ||
"type": "string", | ||
"default": " ", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Default should be |
.
Not really sure this should be configurable though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, we may as well pick a good default
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be better to provide an option, for example, I prefer using spaces.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@xiyaowong The problem is that a big focus of this extension is to reduce the lines of code and simplify, because currently it is difficult to maintain. This means thinking critically of features that don't bring much value. In this case, having an option provides small value.
If it would be better to simply have spaces for everyone, that would be fine.
We can merge it, but we should avoid adding configuration options that make little impact.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Many users have different preferences for UI, such as me. The maintenance difficulty is not directly related to the new features and the number of lines of code. I agree that our primary goal is to reduce the code complexity as much as possible, but it is by no means relying on reducing the code and avoiding new configurations.
3d49672
to
8fe0c22
Compare
} else { | ||
this.statusBar.hide(); | ||
} | ||
// Always show the status line |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 for this also. It was weird that the statusbar disappears.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should use -1
Separator used by statusline