Dear friends,

The purpose of this email is to carry on a discussion from the end of last
year regarding separate username, password and login options command line
switches as well as some discussion in the following bug report and obtain
some idea of preference for the new switches:

https://sourceforge.net/p/curl/bugs/1375/

As some of you are aware it isn't possible to currently specify a username
with a colon in as that is used to separate the username from the password
in the --user / -u switch. This has sometime caused user of the curl command
lien tool an amount of hassle and frustration especially as it is possible,
through separate options, in libcurl.

In December we introduced --login-options as I had previously added the
ability to specify protocol specific login options to the same --user,
however we reverted that change due to the semi-colon separator breaking
backwards compatibility after I added the separate libcurl options.

The following are possible options for new switches, although we could add
some logic to --user that if a new --password type option is specified that
it doesn't parse --user for the password:

--username
--password
--login-user
--login-username
--login-password

My questions are...

a) Should we add the logic mentioned above to --user or have a separate
option for the username?
b) Does anyone have a preference on what the long arguments should be?
c) What, if any, short arguments should we use? As -u, -U, -p and -P are
already taken.

Note:

--login-options currently doesn't have a short version.

Many thanks in advance.

Kind Regards

Steve
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-users
FAQ: http://curl.haxx.se/docs/faq.html
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2014-05-29