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
First of all... this library is great and gave me what pretty much nothing else I could find had:
Intuitive opts parsing
Great autogeneration of help pages
Small and portable
Works with bash 3
So thanks!!
Anyway, my issue is what the title says.. some things are hard to sum up in 30 characters or whatever I have until the 80 char limit is passed, and it would be nice if I could have nicely-formatted multiline descriptions of commands and flags. Maybe there's already a way, but I'm not sure what it is!
Disclaimer: I am not very good at bash, I'm just trying to write a tool that works without asking anyone to install something first. :)
The text was updated successfully, but these errors were encountered:
Multiline is not well supported but you can do it by hand if you use the getopt_add_text command, the thing is that you will have to split your descriptions manually.
Here is an example:
getopt_add_flag "--flag2" "Flag with no short name" opt_flag2
getopt_add_text " Some additional description"
Once you have a proper result the behaviour of the lib is quite predictive and should therefore render the same on any screen. Nevertheless the library uses the tab character and there is no guarantee that you will find it defined with the same size on each system.
First of all... this library is great and gave me what pretty much nothing else I could find had:
So thanks!!
Anyway, my issue is what the title says.. some things are hard to sum up in 30 characters or whatever I have until the 80 char limit is passed, and it would be nice if I could have nicely-formatted multiline descriptions of commands and flags. Maybe there's already a way, but I'm not sure what it is!
Disclaimer: I am not very good at bash, I'm just trying to write a tool that works without asking anyone to install something first. :)
The text was updated successfully, but these errors were encountered: