From: Chris Green <cmg@sourcefire.com>
Subject: Re: Crypto key bindings considered harmful
Date: Tue, 27 May 2003 14:03:23 -0400 [thread overview]
Message-ID: <m3k7ccgtck.fsf@radon.sfeng.sourcefire.com> (raw)
In-Reply-To: <873cj09xgn.fsf@eris.void.at> (Andreas Fuchs's message of "Tue, 27 May 2003 16:14:19 +0000 (UTC)")
Andreas Fuchs <asf@void.at> writes:
> Today, Florian Weimer <fw@deneb.enyo.de> wrote:
>> Key sequences such as 'C-c C-m c' are a *very* bad idea. Guess
>> why. 8-/
>
> Ugh, right.
Yup. When doing crypto in gnus, it's one of the few times I make
myself use the Attachements Menu since it's not going have any
possibility of me just hitting C-c C-c
--
Chris Green <cmg@sourcefire.com>
To err is human, to moo bovine.
next prev parent reply other threads:[~2003-05-27 18:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 12:45 Florian Weimer
2003-05-27 13:13 ` Kai Großjohann
2003-05-27 16:14 ` Andreas Fuchs
2003-05-27 18:03 ` Chris Green [this message]
2003-05-27 18:55 ` Romain FRANCOISE
2003-05-27 21:36 ` Andreas Fuchs
2003-05-27 22:01 ` Simon Josefsson
2003-05-27 22:19 ` lawrence mitchell
2003-05-27 22:34 ` Florian Weimer
2003-05-27 23:06 ` Simon Josefsson
2003-10-18 13:02 ` Lars Magne 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=m3k7ccgtck.fsf@radon.sfeng.sourcefire.com \
--to=cmg@sourcefire.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.
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).