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
The output of the circleci command appears to be broken in my terminal whenever the window width is below 122 characters, due to the border effect that has been added:
Expected behavior:
The border effect shouldn't break the output. There's only 1 line that "overflows" inside of the box area between 85 and 121 character output width (the --host help text). I would rather have that one line overflowing than every single line on the screen.
Possible solutions:
Don't draw this border at all.
Disable the border if the window size is smaller than the bounding box size
Allow me to disable the border
I don't want to spark a debate around "what is a reasonable window size", but I'm sure most developers don't always run their terminals in full-width or full-screen modes, and breaking output for aesthetic purposes seems like a tradeoff with more negative sides than positive ones?
When did this begin / Was this previously working?:
Whole heartedly agree with this one: the outline makes the CLI extremely hard to use. (Have a MacBook Pro 15" with no external monitor, so not a massively large dev space and most of my console windows aren't full screen.) I basically no longer use the --help locally; exclusively try to read the docs on the repo for how to use the CLI.
Meta:
CircleCI CLI Version:
Operating System:
CircleCI CLI Diagnostic:
Current behavior:
The output of the
circleci
command appears to be broken in my terminal whenever the window width is below 122 characters, due to the border effect that has been added:Expected behavior:
The border effect shouldn't break the output. There's only 1 line that "overflows" inside of the box area between 85 and 121 character output width (the
--host
help text). I would rather have that one line overflowing than every single line on the screen.Possible solutions:
I don't want to spark a debate around "what is a reasonable window size", but I'm sure most developers don't always run their terminals in full-width or full-screen modes, and breaking output for aesthetic purposes seems like a tradeoff with more negative sides than positive ones?
When did this begin / Was this previously working?:
This seems to have been introduced in #782.
Additional Information:
The text was updated successfully, but these errors were encountered: