From: Jambunathan K <kjambunathan@gmail.com>
To: Richard H Lee <ricardohenrylee@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: ASCII encryption
Date: Mon, 16 Apr 2012 22:19:25 +0530 [thread overview]
Message-ID: <81ipgzei5m.fsf@gmail.com> (raw)
In-Reply-To: <4F8C4967.8090306@gmail.com> (Richard H. Lee's message of "Mon, 16 Apr 2012 17:31:35 +0100")
Richard H Lee <ricardohenrylee@gmail.com> writes:
> On 16/04/12 15:18, Jambunathan K wrote:
>> If `epa-armor' is not supported it should be removed or be made in to a
>> defconst. Or it could be crptically renamed so that people don't
>> discover it accidentally. The info manual can be augmented to mention
>> why the author thinks using it globally is not a good idea.
>>
>> epa-armor is like the biblical forbidden fruit with hints of both
>> pleasure and pain. The ultimate end it achieves is to leave mere
>> mortals in a state of perpetual confusion on private matters.
>
> So I that (setq epa-armor t) in my emacs file is not a good idea?
That's what the last line of the docstring says. It is confusing and
also scary.
,----[ C-h v epa-armor RET ]
| epa-armor is a variable defined in `epa.el'.
| Its value is nil
|
| Documentation:
| *If non-nil, epa commands create ASCII armored output.
|
| You should bind this variable with `let', but do not set it globally.
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
`----
next prev parent reply other threads:[~2012-04-16 16:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-15 15:08 ASCII encryption Richard H Lee
2012-04-16 11:51 ` Bernardo
2012-04-16 12:25 ` Richard H Lee
2012-04-16 14:18 ` Jambunathan K
2012-04-16 16:31 ` Richard H Lee
2012-04-16 16:49 ` Jambunathan K [this message]
2012-04-17 1:17 ` 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=81ipgzei5m.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=ricardohenrylee@gmail.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.