From: "Trent W. Buck" <trentbuck@gmail.com>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: 25769@debbugs.gnu.org
Subject: bug#25769: 24.5; netrc-parse assumes machine/login/password all appear on one line
Date: Mon, 20 Feb 2017 11:02:45 +1100 [thread overview]
Message-ID: <20170220000243.GA1935@frey> (raw)
In-Reply-To: <877f4okf0p.fsf@lifelogs.com>
Ted Zlatanov wrote:
> On Fri, 17 Feb 2017 12:22:10 +1100 trentbuck@gmail.com (Trent W. Buck) wrote:
>
> TWB> ...but now I'm finally annoyed enough to actually report this and get a formal WONTFIX.
>
> Please see
> https://lists.gnu.org/archive/html/bug-gnu-emacs/2015-12/msg00266.html
> (the whole discussion is pertinent)
Yes; I see the problem there.
This is a duplicate of that bug report.
> For your bug report specifically, maybe you mean
> `auth-source-netrc-parse'? If you do mean `netrc-parse', please note
> that it's only used in one place in the whole Emacs core AFAIK.
Ah, I didn't realize netrc.el had been replaced by auth-source.el.
As a simple test I tried feeding it my actual ~/.netrc — some entries
are newline delimited, and some are all-on-one-line — but it didn't
seem to find ANY of them:
(auth-source-netrc-parse :file "~/.netrc") ⇒ nil
But if I open .netrc manually, go to point-min, and call
(auth-source-netrc-parse-entries #'identity 999)
…it returns a correctly parsed list, handling comments & newlines between fields perfectly.
I'm a bit puzzled which bit of code is failing to handle newlines.
Am I missing something obvious?
(I haven't read auth.info yet because I've gotta go get it specially
due to the DFSG/GFDL dispute.)
> I would rather not patch or support netrc.el--better to remove it altogether.
Understood, and agreed.
next prev parent reply other threads:[~2017-02-20 0:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 1:22 bug#25769: 24.5; netrc-parse assumes machine/login/password all appear on one line Trent W. Buck
2017-02-17 15:34 ` Ted Zlatanov
2017-02-20 0:02 ` Trent W. Buck [this message]
2017-02-21 2:49 ` Glenn Morris
2021-08-14 14:11 ` Lars 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=20170220000243.GA1935@frey \
--to=trentbuck@gmail.com \
--cc=25769@debbugs.gnu.org \
--cc=tzz@lifelogs.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).