On Sat, 12 Nov 2016, Isaac Boukris wrote:

>> Do you feel differently?
>
> No, I'm fine with that, but maybe we should consider to mark global
> arguments.

Yes I agree. Even if I don't think we right now very clearly describe what a
global vs local command line argument is and works.

I'm actually in the progress of trying out an overhaul of the command line
option documentation. I want to document each command line option in its own
file, each with its own set of meta data. Global/local could be one type of
data to store. Other meta-data would be for which protocol it applies and we
could also just do generic "tags".

Then from that, we generate the man page (as it looks today with all options
in a single flow) and I want to generate separate web pages for each command
line option. I hope that will allow us to write more documentation per command
line option (which certainly happened when we split out the libcurl option
documentation in a similar fashion) and make it easier to get for example sets
of options that affect certain protocols etc. And make each option documented
more consistently. And have them listed in a properly sorted order. =)

I'm working on some local experiments on how this could be done. I hope to be
able to show it off within a few days if I just get it the way I want to.

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
List admin: https://cool.haxx.se/list/listinfo/curl-users
FAQ:        https://curl.haxx.se/docs/faq.html
Etiquette:  https://curl.haxx.se/mail/etiquette.html