Skip to main content


If there is *any* area that #curl is not best-in-class, we should put in more work and improve curl in that area. While at the same time keep up and polish it in all other aspects.
#curl
in reply to daniel:// stenberg://

Curl is not best-in-class in having man pages that follow the conventions of man pages. It’s not terrible, but not best-in-class.

What bugs me specifically is that the man pages are not properly sentence-spaced. So you’ll see “curl is a tool for transferring data from or to a server using URLs. It supports […]” with a single space after the full stop, but you’ll also see “(e.g. "path1:path2:path3")” with two spaces after the “e.g.”

I haven’t gotten around to submitting an issue anywhere. Should I? Where?

in reply to humm

@humm then you look on old man pages. We have no two-space sequences and I know this because I have checks for it.

So which project do you think ships better manpages than curl?

@humm
in reply to daniel:// stenberg://

I checked version 8.10.0. Better man pages in general, I don’t know—curl’s are pretty good. Other man pages (sometimes) follow man page conventions better. An unsurprising example are the groff man pages.
in reply to humm

@humm I'm 100% sure our manpage generator can be improved. I think you have pretty high requirements when you say this (detail) makes our manpages not qualify as best-in-class. But hey, your opinion is yours.
@humm
in reply to humm

@humm file issues here: github.com/curl/curl/issues
@humm
in reply to daniel:// stenberg://

I think the cron implementation in systemd is better than in curl 😈
in reply to daniel:// stenberg://

Is there any way/tool to figure out which app/service is requesting a download or upload to a command line tool like curl etc. ? This is more a macro view question. Thanks.
in reply to daniel:// stenberg://

Thank you, if you say this, I shouldn't even try. I would be wasting my time. Cheers!