my primary complaint was the lack of documentation. whatever you do (even if nothing), please document the available options in curl(1).

the suggestion from Daniel to put them in the url is workable but complicates my code, prompting deliberations to move away from curl to something else.

Linus Nielsen's comment re `--pass` is almost attractive but i'm suspicious of changing the grammar of an existing option (the interpretation of `--user` optarg changes with the absence/presence of `--pass`).

i would deprecate (not remove!) `--user` in favor of a new option, let's say `--login`. keep `--user` as is, return `;` into the password character set, whatever. `--user` shapeshifts too much, i can't really use it in my code with user-supplied strings. it is broken, i don't want to use it at all.

---
** [bugs:#1375] --user optarg specced out insufficiently**
**Status:** open
**Created:** Thu May 22, 2014 10:59 AM UTC by Roman Neuhauser
**Last Updated:** Fri May 23, 2014 10:05 AM UTC
**Owner:** Steve Holme
i've read the man page, FAQ, appropriate parts of the manual, and i can't find what to do when my username or password contain colons.
---
Sent from sourceforge.net because curl-tracker@cool.haxx.se is subscribed to https://sourceforge.net/p/curl/bugs/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/curl/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.