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

feat: Add option statusLineSeparator #1521

Merged
merged 2 commits into from
Oct 11, 2023

Conversation

xiyaowong
Copy link
Collaborator

Separator used by statusline

Separator used by statusline
package.json Outdated
},
"vscode-neovim.statusLineSeparator": {
"type": "string",
"default": " ",
Copy link
Collaborator

@justinmk justinmk Oct 11, 2023

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.

Copy link
Member

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

Copy link
Collaborator Author

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.

Copy link
Member

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.

Copy link
Collaborator Author

@xiyaowong xiyaowong Oct 11, 2023

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.

@theol0403 theol0403 merged commit 374d72f into vscode-neovim:master Oct 11, 2023
8 checks passed
} else {
this.statusBar.hide();
}
// Always show the status line
Copy link
Collaborator

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.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I think we need to adjust the priority. It looks strange right now. It should be displayed in the middle so that it doesn't cause other items to move around.

image

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Should use -1

@xiyaowong xiyaowong deleted the feat/status_line_separator branch October 21, 2023 03:15
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