From: Ted Zlatanov <tzz@lifelogs.com>
To: Ivan Shmakov <ivan@siamics.net>
Cc: 24274@debbugs.gnu.org, zhtvk@gmx.com,
Viktor Slavkovik <viktor.slavkovik@gmail.com>
Subject: bug#24274: 24.5; Use auth-source library for remote passwords in Rmail
Date: Mon, 22 Aug 2016 09:00:31 -0400 [thread overview]
Message-ID: <871t1h9cwg.fsf_-_@lifelogs.com> (raw)
In-Reply-To: <87inutsyvw.fsf@violet.siamics.net> (Ivan Shmakov's message of "Sun, 21 Aug 2016 19:30:43 +0000, Sat, 20 Aug 2016 19:45:50 +0000")
On Sun, 21 Aug 2016 19:30:43 +0000 Ivan Shmakov <ivan@siamics.net> wrote:
>> I've made an update (attached) to the previous patch. I removed the
>> code indentation spaces and changed the docstring to be more
>> descriptive. Also, I included a function check for the auth-source
>> password which was missing before.
Thank you!
IS> We can call auth-source-forget+ if necessary once we figure it
IS> out; just like it’s done in gnus/nnimap.el and mail/smtpmail.el.
Right, those are the typical uses of auth-source.
IS> The auth-source library allows access to other backends beside
IS> plain ~/.authinfo, which is why I think it makes sense to
IS> mention the library by name here. See the docstring for the
IS> erc-autojoin-channels-alist variable for an example.
Agreed! The authinfo file *format* is a default, but there are actually
three of them: '("~/.authinfo" "~/.authinfo.gpg" "~/.netrc")
Thanks
Ted
next prev parent reply other threads:[~2016-08-22 13:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-20 18:12 bug#24274: 24.5; Use auth-source library for remote passwords in Rmail Viktor Slavkovikj
2016-08-20 19:45 ` Ivan Shmakov
2016-08-21 14:26 ` Viktor Slavkovik
2016-08-21 19:30 ` Ivan Shmakov
2016-08-22 13:00 ` Ted Zlatanov [this message]
2019-06-25 11:54 ` Lars Ingebrigtsen
2020-08-11 14:12 ` Lars Ingebrigtsen
2020-09-07 15:29 ` Antoine Kalmbach
2020-09-07 15:58 ` 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=871t1h9cwg.fsf_-_@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=24274@debbugs.gnu.org \
--cc=ivan@siamics.net \
--cc=viktor.slavkovik@gmail.com \
--cc=zhtvk@gmx.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.