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

The WRAP functionality of the status line is annoying for those who have 'wrap' on all the time #3

Closed
xigoi opened this issue Oct 14, 2021 · 5 comments

Comments

@xigoi
Copy link
Contributor

xigoi commented Oct 14, 2021

The default status line has a functionality for showing WRAP next to the mode name when 'wrap' is on. I figure that this is intended to be helpful when you often switch the setting, but I don't think most Neovim users do that. I personally always have 'wrap' on and the indicator is completely redundant. I understand that I could just copy the default config and remove the line, but I'm questioning if it should be included in the default in the first place. I don't think it's generally useful, since you can usually easily tell if 'wrap' is on by looking at the screen. The same applies to SPELL for people who use it.

@echasnovski
Copy link
Owner

Hmmm. That seems like a valid point. I'll sleep on it and return to it tomorrow. Thanks.

@echasnovski
Copy link
Owner

I think you are right here. These options are used in default purely because I tend to use them on and off regularly. I'll think about the most proper way to display them (custom "option" section or just documenting the way) and remove them from default statusline.

@xigoi
Copy link
Contributor Author

xigoi commented Oct 15, 2021

Great. Thinking about it, what if there was a way to modify the default config without having to copy the whole thing into your code? Would that be needlessly complex?

@echasnovski
Copy link
Owner

Great. Thinking about it, what if there was a way to modify the default config without having to copy the whole thing into your code? Would that be needlessly complex?

Yeah, I thought about it and experimented a bit. It feels that enough flexibility (change sections, their highlighting, their truncation width) comes with at least the same amount of configuration code as the default function. Enabling only some of parts to be configured is indeed unnecessary complexity when with only around 20 lines of code user can own the full statusline content.

@echasnovski
Copy link
Owner

Just removed those sections from default content in favor of using custom documented code snippets. Thank you for the suggestion.

echasnovski added a commit that referenced this issue Mar 10, 2022
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

No branches or pull requests

2 participants