Repository navigation
Allow individual status bar messages to clip instead of hide #84258
Description
- Create a status bar item with a message
- If the message does not fit then the entry is hidden. Instead the message should be clipped.
Background: Supporting a feature to show current error in the status - #20183
Activity
bpasero commentedon Nov 8, 2019
I thought about that but I wasn't sure how the impact is for extensions. E.g. if a message is always clipped something like "Delete File Without Confirmation" might become "Delete File..." which hint at a confirmation. Is that clever?
sandy081 commentedon Nov 8, 2019
Yeah.. does not makes sense for actions, but allowing statuses to be clipped is a valid scenario. Also, I do not think we hide buttons instead clip labels at other places right?
[-]Status bar messages should be clipped instead of hiding[/-][+]Allow individual status bar messages to clip instead of hide[/+]bpasero commentedon Nov 8, 2019
Maybe behind an option for the status bar entry.
sandy081 commentedon Nov 8, 2019
Benjamin Pasero (@bpasero) I am looking into this and looks like nothing can be done unless the status bar items do not wrap. Currently status bar item wrap and overflow items are wrapped underneath. Is wrapping necessary ?
17 remaining items
jrieken commentedon Dec 6, 2019
I believe this can be done nicely in CSS. Let's use this as a flex-box learning opportunity.
mlfecho commentedon May 23, 2022
Hi, in case this ticket needs a bump, I just wanted to offer an example where this hide instead of clip behavior is problematic.
The vim extension prints warnings like file permissions in the status bar, and without the visible warning it can look like you're successfully saving a file when you actually aren't.
vscodenpa commentedon Jan 16, 2024
We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!