-
Notifications
You must be signed in to change notification settings - Fork 120
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
Tabular compact mode #308
Comments
Thanks for the idea! I like the general look of the output you posted, however there are multiple problems that need to be resolved before we could move forward with development of such an option:
... and that looks a bit cryptic to me. We definitely don't want to classify pages by whether or not we should display them one way or another. I don't really know what to do about that one. |
You clearly arranged these outputs by hand, how would tealdeer find out what the optimal alignment is? Even when composing your examples, you had to make some difficult decisions, like with
But then we could just put in the command name, for |
It's not difficult: for each column you calculate two numbers:
so with the second's column Then there are two more things for extra style points (but even without them the ouptut will already be much better structured than currently)
See the algo above, in my shell alias function it's ~
Same thing, if these things represent a column, you get this alignment automatically from the algorithm, every column will be at least space-padded to
But even if it's not aligned (e.g., a command has dozens of variable-parameter pairs and you only want to have a max of 5 columns), it's not worse than what you have currently, so it's not an issue.
Fine, so you'll not have your ⎀ |
Since, in contrast to other issues, there hasn't been any reaction to this issue from anyone else, I am going to close. I don't think that this additional output mode is needed currently and it would just add more code for too little users demanding the feature. Additionally, the tldr pages are not written with this format in mind, so I think we would just set ourselves up for lots of future layout issues here. Sorry :/ |
What contrast? E.g., your first couple of opened issues in this repo opened since 2018/20 have almost reaction from anyone but the repo owners/collaborators, and still open |
There are issues that we initially disagree with but reconsider if there is enough attention (for example #311). There are also old issues that don't have reactions but we still deem useful. If you disagree with these decisions, you can always create and maintain a fork :) |
You failed to address the point: how would you reconsider with enough attention if you've significantly decreased the chance of getting attention by closing the issue? |
I am afraid I won't. The issue has been open for eight months, now I finally rejected it as I do not see it belonging to either of the two categories of my previous comment. Please check your tone going forward, this is an open source project that @dbrgn and I maintain in our free time for no compensation. You have repeatedly come to my attention for not accepting decisions we make regarding the project and communicating as if a) we are some kind of service that you are a paying customer of and b) your opinion is the ultimate truth. If you are unable to communicate appropriately, we will have to block you from participating in the tealdeer project discussions. |
You can't fit it in those two categories for the reason I've mentioned
And this is an open source comment with valuable design feedback that I've provided in my free time for no compensation Also, I accept your decisions, I just point out the flaws in your arguments supporting those decisions Unfortunately, your tone perception is just as astute - what paying customer would not make any demands to impement a feature? |
It seems that even the compact mode isn't compact enough :), but more importantly, I don't like the style of commands as secondary since I'm used to all cli tools showing commands first and description second
I'd like to suggest a
tabular compact
mode that is also easier to scan since the commands and comments are cleanly separated into columns (and not having to repeat the main commandbrew
helps in increasing the tldr factor ;)):The first column width should have some max limit, so that very long commands would just "overflow", but due to the support of colors it'd still be easy to visually separate them from the description
instead of this
The text was updated successfully, but these errors were encountered: