From: Daiki Ueno <ueno@unixuser.org>
To: ding@gnus.org
Subject: Re: plstore questions
Date: Mon, 26 Sep 2011 11:41:19 +0900 [thread overview]
Message-ID: <m3wrcw3xq7.fsf-ueno-ueno-ueno@unixuser.org> (raw)
In-Reply-To: <874o03gegk.fsf@keller.adm.naquadah.org> (Julien Danjou's message of "Fri, 23 Sep 2011 23:02:03 +0200")
Julien Danjou <julien@danjou.info> writes:
> 1. Why isn't `plstore-encrypt-to' a defcustom rather than a defvar?
Since plstore-encrypt-to is marked as permanent local, I think users
don't want to set it with M-x customize.
> 2. In `plstore--insert-buffer', I don't understand this test:
>
> (if (or (eq plstore-select-keys t)
> (and (null plstore-select-keys)
> (not (local-variable-p 'plstore-encrypt-to
> (current-buffer)))))
> (epa-select-keys …
>
> The documentation indicate that if `plstore-select-keys' is to nil and
> if `plstore-encrypt-to' is set to something, then no epa-select-keys.
> But the test does not check if plstore-encrypt-to is set, but checks if
> it is local variable. I don't get why, and that does not make plstore
> acts according to the documentation. Could you enlighten me?
plstore-encrypt-to is supposed to be set through file variable and the
above check is for the case where plstore-encrypt-to is set to nil.
For example, if plstore-select-keys is nil and a file begins with:
;; plstore-encrypt-to: nil
it will skip epa-select-keys dialog and use symmetric encryption. If
there is no such line, it will open the dialog with default recipients
(if any) selected. I agree with that the documentation is a bit
misleading though.
Regards,
--
Daiki Ueno
next prev parent reply other threads:[~2011-09-26 2:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 21:02 Julien Danjou
2011-09-26 2:41 ` Daiki Ueno [this message]
2011-09-26 9:27 ` Julien Danjou
2011-09-27 6:27 ` 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=m3wrcw3xq7.fsf-ueno-ueno-ueno@unixuser.org \
--to=ueno@unixuser.org \
--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).