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
We use a constant padding instead of a constant width, which causes the description to shift to the left.
One problem is that we can't make a table by combining the two columns first and then gluing the two columns side by side, as the rows in the description might overflow. Hmm, how do we get a proper table...
The text was updated successfully, but these errors were encountered:
fd appears to be doing something extremely strange. It somehow detects the width of the terminal and prints the help accordingly? What sorcery is this? Do we even need to support fd or maybe try using some other test program?
Wide terminal
Narrow terminal
Even narrow terminal
EDIT - Actually this isn't sorcery, it is just alternate behaviour. The program does have to do IO anyways when it prints all the descriptions aligned to the same width (because it has to know the terminal width to compute breaks, to insert newlines and padding), fd's CLI package is just smarter in that it tries to preserve readability. Hmm....
typesanitizer
changed the title
Item table rendering isn't correct when flag overflows
Item table rendering isn't correct when flag overflows onto next line
Nov 22, 2018
For simplicity of testing, it would be better to use hlint or some other "normal" CLI app, instead of fd to avoid getting the results mixed up with fd's own behaviour.
If you look at fd
We use a constant padding instead of a constant width, which causes the description to shift to the left.
One problem is that we can't make a table by combining the two columns first and then gluing the two columns side by side, as the rows in the description might overflow. Hmm, how do we get a proper table...
The text was updated successfully, but these errors were encountered: