From: Ted Zlatanov <tzz@lifelogs.com>
To: Andy Moreton <andrewjmoreton@gmail.com>
Cc: 22081@debbugs.gnu.org
Subject: bug#22081: 24.5; netrc.el fails parsing authinfo items spread over multiple lines
Date: Mon, 07 Dec 2015 13:15:59 -0500 [thread overview]
Message-ID: <87twnuunts.fsf@lifelogs.com> (raw)
In-Reply-To: <86d1uiqrbe.fsf@gmail.com> (Andy Moreton's message of "Mon, 07 Dec 2015 14:14:13 +0000")
On Mon, 07 Dec 2015 14:14:13 +0000 Andy Moreton <andrewjmoreton@gmail.com> wrote:
AM> On Sat 05 Dec 2015, Ted Zlatanov wrote:
>> On Fri, 04 Dec 2015 14:25:00 +0000 Andy Moreton <andrewjmoreton@gmail.com> wrote:
>> My more important point was that there's no standard (or library) for
>> parsing netrc files. In particular, quoting is not specified as I
>> mentioned. The BSD spec is ambiguous and allowing multi-line entries
>> would not serve any practical purpose.
AM> The spec clearly defines that tokens are separated with SPACE TAB or
AM> NEWLINE, which seems unambiguous to me.
Without a quoting standard, it's not clear whether strings inside quotes
can be multiline and whether the newline itself can be escaped.
AM> Disallowing NEWLINE as a token separator means you are not parsing an
AM> extension of the existing format, but something incompatible with it.
AM> That's fine as it offers useful features, but it should use a different
AM> file name to make it clear that it is not the same format.
Fortunately `auth-sources' defaults to ~/.authinfo and ~/.authinfo.gpg
before ~/.netrc right now.
Ted
next prev parent reply other threads:[~2015-12-07 18:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 10:20 bug#22081: 24.5; netrc.el fails parsing authinfo items spread over multiple lines Vasilij Schneidermann
2015-12-03 13:55 ` Ted Zlatanov
2015-12-03 18:28 ` Glenn Morris
2015-12-04 14:25 ` Andy Moreton
2015-12-05 23:43 ` Ted Zlatanov
2015-12-07 14:14 ` Andy Moreton
2015-12-07 18:15 ` Ted Zlatanov [this message]
2015-12-08 9:35 ` Andy Moreton
2015-12-08 14:06 ` Ted Zlatanov
2015-12-14 17:57 ` Lars Magne Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87twnuunts.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=22081@debbugs.gnu.org \
--cc=andrewjmoreton@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).