From: Ted Zlatanov <tzz@lifelogs.com>
To: Andy Moreton <andrewjmoreton@gmail.com>
Cc: 22081-done@debbugs.gnu.org
Subject: bug#22081: 24.5; netrc.el fails parsing authinfo items spread over multiple lines
Date: Tue, 08 Dec 2015 09:06:33 -0500 [thread overview]
Message-ID: <87oae1uj9y.fsf@lifelogs.com> (raw)
In-Reply-To: <86io492sh1.fsf@gmail.com> (Andy Moreton's message of "Tue, 08 Dec 2015 09:35:22 +0000")
On Tue, 08 Dec 2015 09:35:22 +0000 Andy Moreton <andrewjmoreton@gmail.com> wrote:
AM> On Mon 07 Dec 2015, Ted Zlatanov wrote:
>> Without a quoting standard, it's not clear whether strings inside quotes
>> can be multiline and whether the newline itself can be escaped.
AM> The original spec is archaic - there is no quoting standard, only tokens
AM> separated by whitespace. As such, a quote is simply another character.
Right, and therefore we can't support the original spec as long as we
also support the more important single-quoting and double-quoting of strings.
I'm closing this without prejudice because I think we've stated our
positions clearly and it's not a bug, but if you or anyone else want to
propose a patch that can support multiline or the other keywords without
breaking the current functionality, we can reopen.
I would also welcome patches to remove the netrc.el usage.
Thanks
Ted
next prev parent reply other threads:[~2015-12-08 14:06 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
2015-12-08 9:35 ` Andy Moreton
2015-12-08 14:06 ` Ted Zlatanov [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oae1uj9y.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=22081-done@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.