From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: EasyPG support for mml2015.el
Date: Mon, 10 Jul 2006 12:53:01 +0200 [thread overview]
Message-ID: <87wtalwx2q.fsf@latte.josefsson.org> (raw)
In-Reply-To: <3634bd45-288d-4222-bd28-4477704242b8@well-done.deisui.org> (Daiki Ueno's message of "Mon, 10 Jul 2006 19:36:21 +0900")
Daiki Ueno <ueno@unixuser.org> writes:
>> One minor issue here too:
>
>> > +(defvar mml1991-cache-passphrase t
>> > + "If t, cache passphrase.")
>
>> This variable isn't used.
>
> Fixed in the attached patch.
Applied, thanks.
>> And maybe there shouldn't be this many variables that control password
>> caching -- now there is at least in mml1991, mml2015 and in pgg, if I
>> recall correctly.
>
> Should these functions be unified in in mml-sec.el?
Yes, that seems like a good idea, at least for mml1991/mml2015. Maybe
it isn't a good idea for PGG to depend on mml-sec variables though?
Hm. Actually, I think it may be better to use password-cache and
password-cache-expiry from password.el instead. What do you think?
Or better, we put the variables in mml-sec, but the defaults are to
use the values from password.el. Some users may want different
password caching policy for mml-sec than for other passwords, but if a
user changes the password.el values, the defaults change everywhere
else too. I think that causes the least surprises.
I'm not sure..
/Simon
next prev parent reply other threads:[~2006-07-10 10:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 3:54 Daiki Ueno
2006-07-10 9:04 ` Daiki Ueno
2006-07-10 10:08 ` Simon Josefsson
2006-07-10 10:36 ` Daiki Ueno
2006-07-10 10:53 ` Simon Josefsson [this message]
2006-07-11 8:28 ` Daiki Ueno
2006-07-25 5:23 ` Daiki Ueno
2006-07-10 10:03 ` Simon Josefsson
2006-07-12 7:38 ` EasyPG hangs Max Froumentin
2006-07-12 8:16 ` Daiki Ueno
2006-07-12 9:16 ` Max Froumentin
2006-07-13 4:02 ` Daiki Ueno
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=87wtalwx2q.fsf@latte.josefsson.org \
--to=jas@extundo.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).