-
Notifications
You must be signed in to change notification settings - Fork 72
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
Better display of ordinal buffer numbers #19
Comments
Makes sense, I like it. |
Hmm. This puts me in a difficult place. I understand the rational argument, and obviously some number of users will like it… I just don’t like how it looks. 😄 OTOH this overlaps with #16 (which I rejected) and #13: if users could specify their own designs for the tabline, you could do this easily. Hmm. |
@ap not sure if this is useful at all, I've just been hacking around for my own sake, but I've used this to get the superscript numbers...: I've placed this within the 'buftabline#render()' function.
And this as a replacement for the 'screen_num' assignment within the for loop within the above function.
|
Thanks, @asilvadesigns. How to implement it is the easy part, though. The problem is I don’t like how it looks, so if I implement it, then it must be in such a way that I can turn it off for myself. But I also don’t want to just add a configuration switch every time a user asks for a little appearance tweak, because I don’t want to end up dealing with 43 conditionals and 11 lookup tables. So I need a reasonable design for allowing users to fully specify the appearance without hardcoding each option. That’s why this issue is stalled. |
@ap gotcha, that makes sense. I suppose any way I could help give me heads up : ), in any case this is really a great plugin and adds really sweet functionality to vim. |
I propose changing buffer numbers in ordinal mode with subscript notation as in screenshot above:
This has 2 advantages:
I can make a PR if you would like to accept this change.
The text was updated successfully, but these errors were encountered: