@liw I agree, and that's a primary reason why I made "curl -h [option]" output the man page section for just that single option. Saves a lot of searching.
There's really no easy concept otherwise to split up a command line tool's man page into something smaller.
It was always hard for me to find extensive documentation on obscure curl features. Is that because the manpage is too long or does it not have enough information?
I remember wanting to try downloading emails using imap after seeing it is supported by curl. I'm not familiar with the protocol itself and I don't know the curl options from the top of my head so it was difficult to bring those together. I found examples online but couldn't move past trying those. I didn't feel like the manpage was helpful in this specific case. Maybe I also didn't know where to look.
That is a really good resource. I found Chapter 9.11. Reading email. It only shows the most basic examples. I'm sure it's possible to execute a search as well but I couldn't find anything.
Lars Wirzenius
in reply to daniel:// stenberg:// • • •I find manual pages inconvenient when they're that long. That format was designed to fit on a physical paper page. Alas.
(This is not a request to split the curl manpage up, or to remove content. I'm merely an old stodgy grump who likes to complain incessantly.)
daniel:// stenberg://
in reply to Lars Wirzenius • • •@liw I agree, and that's a primary reason why I made "curl -h [option]" output the man page section for just that single option. Saves a lot of searching.
There's really no easy concept otherwise to split up a command line tool's man page into something smaller.
schnedan
in reply to daniel:// stenberg:// • • •hisold
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to hisold • • •hisold
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to hisold • • •hisold
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to hisold • • •