Re: I want to add non-RFC passwd to pop and imap

[Alain Magloire]

> 
> Quoting Alain Magloire <address@hidden>, who wrote:
> > > It *should* allow the password as in the other URLs, ftp, http,
> > > etc., now you have to invent another syntax for fully specifying
> > > the resource, and note that Mutt's mechanism is not general
> > > enough, you have no way to specify which imap url the password
> > > is associated with.
> > 
> > Unfortunately, the rationale and the wording of the RFCs
> > were very clear.  But I certainly understand the point you
> > are making and feel the same way.  So if you are proposing
> > to allow in the URL passwd as an extension, I'm all for it
> > if it does not break severly the current semantics in the
> > RFCs.
> 
> I don't think it changes anything, unless you have a colon
> in your user name,

Actually, I do not think is possible to have colon in
usernames on Unix systems, /etc/passwd is a separated colon fields ...

> 
> Yes, I noticed that there isn't a general syntax, but I think it's
> close enough for the our purposes. I do a little checking after,
> for instance pop checks that no path or query was specified after
> the hostname. I think it's backwards compatible.

Ok.  I vaguely remember something like that in the original url parser
ofr pop:// but IIRC it was to catch this:
 pop://address@hidden/

The parser would have put "qnx.com/" in the hostname field.  Since
pop URL does not have any query/paths  it was easier to nuke the trailing
junk.

> 
> > > I'm cleaning up the docs to match the new API before committing. But
> > 
> > Wow!
> 
> And forgot the example .texi this morning, sorry!

*cough* ... *cough* and some ChangeLog entries?
Funny, you are the only programmer I know that takes the time to document
things, but somehow manage to skip the ChangeLogs 8-).

Thanks for taking a stab at this.

--
alain