all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 56976@debbugs.gnu.org
Subject: bug#56976: 29.0.50; Obsolete netrc.el
Date: Thu, 04 Aug 2022 16:44:36 +0200	[thread overview]
Message-ID: <87a68kgjaj.fsf@gnus.org> (raw)
In-Reply-To: <87r11wdqhl.fsf@gmx.de> (Michael Albinus's message of "Thu, 04 Aug 2022 16:37:26 +0200")

Michael Albinus <michael.albinus@gmx.de> writes:

> *This Tramp* has to work back with Emacs 26. Don't worry, I will check
> the compatibility status after your commit, and adjust as needed.

The problem is that until earlier today, auth-source-netrc-parse just
returned nil if called with no host/user parameters, so I don't know
what the compat check would be.

Perhaps it'd be more convenient if there was a new function like
`auth-source-netrc-parse-all-entries' that tramp.el could check for the
presence of?  Would that help?  (It would just be an alias, probably.)

> I'm scanning all new messages in the groups I read on gmane for some
> buzzwords, like "tramp". Those messages will be presented to me first :-)
>
> Thanks to automated gnus-summary-search-article-forward.

:-)






  reply	other threads:[~2022-08-04 14:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-04 14:16 bug#56976: 29.0.50; Obsolete netrc.el Lars Ingebrigtsen
2022-08-04 14:23 ` Lars Ingebrigtsen
2022-08-04 14:37   ` Michael Albinus
2022-08-04 14:44     ` Lars Ingebrigtsen [this message]
2022-08-04 14:50       ` Michael Albinus
2022-08-04 14:51       ` Lars Ingebrigtsen
2022-08-04 15:00         ` Michael Albinus
2022-08-04 15:08           ` Lars Ingebrigtsen
2022-08-04 17:29             ` Michael Albinus
2022-08-04 17:34               ` Lars Ingebrigtsen
2022-08-04 15:14 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a68kgjaj.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=56976@debbugs.gnu.org \
    --cc=michael.albinus@gmx.de \
    /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.