Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Discussion: bufferline/statusline/picker elements #3712

Closed
sbromberger opened this issue Sep 5, 2022 · 0 comments
Closed

Discussion: bufferline/statusline/picker elements #3712

sbromberger opened this issue Sep 5, 2022 · 0 comments
Labels
A-helix-term Area: Helix term improvements C-discussion Category: Discussion or questions that doesn't represent real issues

Comments

@sbromberger
Copy link
Contributor

Now that #2759 has been merged, it might make sense to take a larger look at how we provide consistent display of elements for bufferline, statusline, and the various pickers. For instance, the file modification indicator is hard-coded in the various "render filename" routines used by all three. I think for consistency we should do something like the following:

  1. create a file-modification-indicator (similar to the read-only-indicator proposed in read only indicator #3709) element that can be placed in statusline
  2. allow bufferline to have a specific configuration like statusline does
  3. allow pickers to have a specific configuration.

Alternately, we can have a common render_filename function that will add these things statically, without customization capability.

@kirawi kirawi added C-discussion Category: Discussion or questions that doesn't represent real issues A-helix-term Area: Helix term improvements labels Sep 6, 2022
@helix-editor helix-editor locked and limited conversation to collaborators Apr 8, 2024
@pascalkuthe pascalkuthe converted this issue into discussion #10267 Apr 8, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
A-helix-term Area: Helix term improvements C-discussion Category: Discussion or questions that doesn't represent real issues
Projects
None yet
Development

No branches or pull requests

2 participants