-
Notifications
You must be signed in to change notification settings - Fork 66
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
sort the options #80
Comments
If the options were to be sorted, do you think it would be more appropriate to sort by long-name or short-name? |
Long.
The options I use regularly I know by heart (short versions) but when I look for something rarely used I look for the long ones as they are informative (even if I then use the short one).
I assume that’s the way for others too.
Is there any way to support this project? I use csvq in several workflows in my practice and a little company I run on a daily basis and can not imagine doing without it any more.
You may contact me directly off list, but another little (LaTeX related) project has “wish list” on Amazon for hardware, another has a PayPal account, things of that nature.
greetings, el
…--
Dr. Eberhard W. Lisse \ / Obstetrician & Gynaecologist
***@***.*** / * | Telephone: +264 81 124 6733 (cell)
PO Box 8421 Bachbrecht \ / If this email is signed with GPG/PGP
10007, Namibia ;____/ Sect 20 of Act No. 4 of 2019 may apply
On 13. Aug 2022, 02:56 +0200, Yuki ***@***.***>, wrote:
If the options were to be sorted, do you think it would be more appropriate to sort by long-name or short-name?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
OK, I'll fix it later. This project does not require financial support for now. |
This fix is included in version 1.17.9 and later. I added features without much thought, so the option names are not consistent, and it may be difficult to find them after all. |
I would find it very helpful if
csvq --help
were to return the Options sorted alphabetically.
el
The text was updated successfully, but these errors were encountered: