4 ms·
I can see this being useful, but I'm not looking forward to the list of command line options being even longer. The output of "curl --help" on my system is alre
by justin_oaks 5y ago
I can see this being useful, but I'm not looking forward to the list of command line options being even longer. The output of "curl --help" on my system is already 212 lines long.
I wish the curl command was split such that different protocols had different commands. I REALLY don't want to see a list of FTP specific command line options whenever I'm just trying to look up a lesser-used HTTP option.
That said, this is really a minor gripe compared to just how useful curl has been for me over the years.
- prpl 5y agoI always think of a perm everyone I do “man curl”, which is more often than I’d like.
- jcul 5y agoI don't think I'll be able to forget this going forward any time I check the curl manpage!
- kortex 5y agoI'm already well past the stage of using moar/micro/[rip]grep to scan through curl's manpage and find what I need. OTOH, if you ignore using curl to GET resources to download, >90% of my curl usage is slinging json, and often involves interpolating strings and hence copy-pasting, so this feature would be immediately useful to me. Curl is kind of the swiss army knife of the web so I don't think a long manpage is out of line.
- makapuf 5y agoYes,a multitool like busybox with separate subcommand names would seem nice