From: Lars Ingebrigtsen <larsi@gnus.org>
To: Jeff Bellegarde <bellegar@gmail.com>
Cc: ding@gnus.org
Subject: Re: Severe limitations in auth-source-macos-keychain-search
Date: Sat, 06 Feb 2016 17:00:46 +1100 [thread overview]
Message-ID: <87zivepecx.fsf@gnus.org> (raw)
In-Reply-To: <m2zivtiqg9.fsf@Jeffs-MBP.home> (Jeff Bellegarde's message of "Mon, 25 Jan 2016 08:17:26 -0800")
Jeff Bellegarde <bellegar@gmail.com> writes:
> I just finished hacking something into shape. I added the following to my
> .gnus. I doubt it's the best solution but it appears to work on my machine.
>
> ;; 1. spec contains lists for `host' and `port'. I use `first' to arbitrarily search for only the first key.
> ;; 2. Use -P to search for port instead of -r. -r requires a 4 character term and disallows a term like 'https'.
> ;; -P seems to work for strings and port numbers.
> (eval-when-compile (require 'cl))
> (defun* auth-source-macos-keychain-search-items (coll type max
> &rest spec
Could you submit at patch for auth-source? I'm sure other people would
also find this useful...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2016-02-06 6:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 8:36 Nikolai Weibull
2016-01-25 14:57 ` Ted Zlatanov
2016-01-25 16:17 ` Jeff Bellegarde
2016-02-06 6:00 ` Lars Ingebrigtsen [this message]
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=87zivepecx.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=bellegar@gmail.com \
--cc=ding@gnus.org \
/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.
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 NNTP newsgroup(s).