From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: .netrc parsing stopped working when not giving port numbers
Date: Thu, 01 Aug 2013 12:45:09 -0400 [thread overview]
Message-ID: <87iozpuzqi.fsf@lifelogs.com> (raw)
In-Reply-To: <m3txj9fp8o.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Thu, 01 Aug 2013 16:40:55 +0200")
On Thu, 01 Aug 2013 16:40:55 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> My change disallows "machine" as a data token. I think that's
>> reasonable, but perhaps I should try harder to catch that case?
LMI> Ideally, all values should be possible.
I refuse empty values on moral grounds :)
LMI> If somebody has a server called "machine", then it would be
LMI> confusing for that not to work. And that's perhaps more likely
LMI> than having a password called "password", which was reported as a
LMI> bug before the rewrite. :-)
I can try harder to make it work. I really didn't imagine it would be a
problem.
Ted
prev parent reply other threads:[~2013-08-01 16:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 9:15 Lars Magne Ingebrigtsen
2013-06-17 10:49 ` Ted Zlatanov
2013-06-17 23:34 ` Ted Zlatanov
2013-08-01 14:40 ` Lars Magne Ingebrigtsen
2013-08-01 16:45 ` Ted Zlatanov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87iozpuzqi.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).