From: Jesper Harder <harder@myrealbox.com>
Subject: Re: How to redefine keys?
Date: Mon, 21 Feb 2005 00:10:35 +0100 [thread overview]
Message-ID: <87braebzf8.fsf@Jesper-Harders-Computer.local> (raw)
In-Reply-To: <m34qg6c3s0.fsf@colina.demon.co.uk>
Colin Paul Adams <colin@colina.demon.co.uk> writes:
> Although I have been using gnus for many years, I have not been able
> to rid myself of the habit of always using the r or R keys, even
> though I often should be using the f or F keys.
You culd set `gnus-confirm-mail-reply-to-news' to t. (I don't recall
if this option is present in Gnus 5.9, though)
> (define-key gnus-summary-mode-map "r" gnus-summary-followup)
> (define-key gnus-summary-mode-map "R" gnus-summary-followup-with-original)
This should be:
(define-key gnus-summary-mode-map "r" 'gnus-summary-followup)
(define-key gnus-summary-mode-map "R" 'gnus-summary-followup-with-original)
next prev parent reply other threads:[~2005-02-20 23:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-20 21:36 Colin Paul Adams
2005-02-20 23:10 ` Jesper Harder [this message]
2005-02-21 0:16 ` Glyn Millington
2005-02-21 8:19 ` Matt N. Jones
[not found] ` <cvc5sn$kgs$1@news.sap-ag.de>
2005-02-21 11:12 ` Glyn Millington
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=87braebzf8.fsf@Jesper-Harders-Computer.local \
--to=harder@myrealbox.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).