From: Robert Pluim <rpluim@gmail.com>
To: Damien Cassou <damien@cassou.me>
Cc: 49243@debbugs.gnu.org
Subject: bug#49243: 27.2; [PATCH] Merge auth-source-pass changes from upstream
Date: Fri, 02 Jul 2021 15:48:12 +0200 [thread overview]
Message-ID: <87o8bkddyb.fsf@gmail.com> (raw)
In-Reply-To: <87mtr4lu1b.fsf@cassou.me> (Damien Cassou's message of "Fri, 02 Jul 2021 15:33:36 +0200")
>>>>> On Fri, 02 Jul 2021 15:33:36 +0200, Damien Cassou <damien@cassou.me> said:
Damien> Robert Pluim <rpluim@gmail.com> writes:
>> That last bit was me, not Lars. I was trying to nudge you to go look
>> at the 'developers' section of the auth-source info manual and bring
>> its documentation in line with the implementation, since it currently
>> doesnʼt say anything about multiple hosts.
Damien> I've just checked. The info manual says:
Damien> -- Function: auth-source-search &rest spec &key type max host user port
Damien> secret require create delete &allow-other-keys
Damien> This function searches (or modifies) authentication backends
Damien> according to SPEC. See the function’s doc-string for details.
Damien> And the docstring says:
Damien> A string value is always matched literally. A symbol is matched as
Damien> its string value, literally. All the SPEC values can be single values
Damien> (symbol or string) or lists thereof (in which case any of the search
Damien> terms matches).
Ah, I didnʼt go back to the docstring
Damien> I think this is good enough.
Yes
Damien> "Success is the ability to go from one failure to another without
Damien> losing enthusiasm." --Winston Churchill
:-)
Robert
--
next prev parent reply other threads:[~2021-07-02 13:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-27 16:02 bug#49243: 27.2; [PATCH] Merge auth-source-pass changes from upstream Damien Cassou
2021-06-28 13:08 ` Robert Pluim
2021-06-30 13:09 ` Lars Ingebrigtsen
2021-06-30 16:09 ` Damien Cassou
2021-06-30 17:56 ` Robert Pluim
2021-07-02 13:33 ` Damien Cassou
2021-07-02 13:48 ` Robert Pluim [this message]
2021-07-02 10:54 ` 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=87o8bkddyb.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=49243@debbugs.gnu.org \
--cc=damien@cassou.me \
/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).