You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As far as I can tell (based on certain parts of the source code and the lack of information on this topic), the display names for the different modes in the status bar are hardcoded. It'd be nice if these could be customized in the settings; The ability to remove the leading/trailing dashes (--) or switch the name to lowercase or an abbreviated form (NOR / INS etc.) would be really handy.
Ideally, I'd imagine this could just be implemented from the user end as options like "vim.modeNames.normal": "NOR" or maybe "vim.statusBarModes.normal": "NOR" or something similar.
Currently, from what I've found at least, I don't believe there are "alternative" options or any existing customization of this particular feature; I have searched for related issues and related options in the documentation and found nothing.
The text was updated successfully, but these errors were encountered:
vi013t
changed the title
Allow custom mode names
Allow custom mode names in the status bar
Apr 17, 2024
As far as I can tell (based on certain parts of the source code and the lack of information on this topic), the display names for the different modes in the status bar are hardcoded. It'd be nice if these could be customized in the settings; The ability to remove the leading/trailing dashes (--) or switch the name to lowercase or an abbreviated form (NOR / INS etc.) would be really handy.
Ideally, I'd imagine this could just be implemented from the user end as options like
"vim.modeNames.normal": "NOR"
or maybe"vim.statusBarModes.normal": "NOR"
or something similar.Currently, from what I've found at least, I don't believe there are "alternative" options or any existing customization of this particular feature; I have searched for related issues and related options in the documentation and found nothing.
The text was updated successfully, but these errors were encountered: