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
{{ message }}
Repository navigation
Feature request: Make help text wrap width configurable #687
While I don't object to making the line-wrapping width configurable, I still stand firmly behind the original decision to default to 80 characters.
As someone who frequently works in split panes and on headless machines, I find long, wrapped lines frustrating. They break visual structure and make terminal output much harder to scan.
On top of that, longer line lengths are generally harder to read. Many style guides, accessibility recommendations, and typographic studies discourage lines much beyond 70–80 characters for exactly that reason.
Bashly encourages (and sometimes enforces) best practices.
If you have command lines that exceed 80 characters, they are probably too long to type comfortably as well. In those cases, I would consider refactoring the interface.
But even if you ultimately do need a longer command, you can still show it cleanly in the examples:
Examples:
download example.com --long option \
--and-more "long options" and \
--even more options and \
--finally some more
This can be represented in bashly.yml using either array syntax:
examples:
- | download example.com --long option \\ \ --and-more "long options" and \\ \ --even more options and \\ \ --finally some more
or string syntax:
examples: | # Download something download example.com --long option \\ \ --and-more "long options" and \\ \ --even more options and \\ \ --finally some more # Another example download ...
That said, I will consider exposing the default width as a configurable option.
Activity
DannyBen commentedon Dec 5, 2025
While I don't object to making the line-wrapping width configurable, I still stand firmly behind the original decision to default to 80 characters.
As someone who frequently works in split panes and on headless machines, I find long, wrapped lines frustrating. They break visual structure and make terminal output much harder to scan.
On top of that, longer line lengths are generally harder to read. Many style guides, accessibility recommendations, and typographic studies discourage lines much beyond 70–80 characters for exactly that reason.
Bashly encourages (and sometimes enforces) best practices.
If you have command lines that exceed 80 characters, they are probably too long to type comfortably as well. In those cases, I would consider refactoring the interface.
But even if you ultimately do need a longer command, you can still show it cleanly in the examples:
Examples: download example.com --long option \ --and-more "long options" and \ --even more options and \ --finally some moreThis can be represented in bashly.yml using either array syntax:
or string syntax:
That said, I will consider exposing the default width as a configurable option.
DannyBen commentedon Dec 5, 2025
Implemented in #688 if you want to test.
DannyBen commentedon Dec 12, 2025
Released in v1.3.5.
Thanks for the suggestion.