From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Reiner Steib <Reiner.Steib@gmx.de>
Cc: Eli Zaretskii <eliz@gnu.org>, ding@gnus.org, emacs-devel@gnu.org
Subject: Re: Differences between mail-mode and message-mode
Date: Thu, 23 Jul 2009 12:05:07 +0900 [thread overview]
Message-ID: <874ot4w13w.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <8763dktv1l.fsf@marauder.physik.uni-ulm.de>
Reiner Steib writes:
> On Wed, Jul 22 2009, Stephen J. Turnbull wrote:
>
> > Reiner Steib writes:
> >
> > > Obviously the key bindings cannot be resolved without a change for
> > > either mail-mode or message-mode users. Maybe set the bindings
> > > depending on some compatibility variable?
> >
> > How about the presence of Newsgroups?
>
> > > > . In mail-mode C-c C-f C-f moves to FCC; in message-mode C-c C-f C-f
> > > > moves to Followup-To, and C-c C-f C-w moves to FCC.
> >
> > Followup-To is rarely useful in a mail message.
>
> A message-mode buffer can be news, mail or both.
Indeed. That's why I mention "Newsgroups" above. I'm conditioning
all my suggestions on "compatibility with the mail-only MUA that has
been default until now". Ie, they apply only when it's *not* a news
post. (As far as Emacs can tell so far: of course that can change if
the user desires.)
Of course this is a hack. I think it's a shame that Gnus chose to
cater to 1-keystroke savings rather than keep a regular, mnemonic
keymap for default, but any attempt to change the Gnus keymap now will
of course meet a response greatly resembling in all ways the response
of mail-mode advocates to suggestions of change.
next prev parent reply other threads:[~2009-07-23 3:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1MRmmG-0006yL-WB@fencepost.gnu.org>
[not found] ` <E1MRn3w-0003wj-QT@fencepost.gnu.org>
[not found] ` <E1MRxo5-00037n-1N@fencepost.gnu.org>
[not found] ` <878wimdbzp.fsf@catnip.gol.com>
[not found] ` <87tz1av8ik.fsf@bzg.ath.cx>
[not found] ` <83vdlqp0rt.fsf@gnu.org>
2009-07-19 11:41 ` Differences between mail-mode and message-mode (was: message-mode is now default?) Reiner Steib
2009-07-19 12:32 ` Differences between mail-mode and message-mode Sven Joachim
2009-07-19 17:51 ` Eli Zaretskii
2009-07-19 18:11 ` Eli Zaretskii
2009-07-22 7:35 ` Differences between mail-mode and message-mode (was: message-mode is now default?) Stephen J. Turnbull
2009-07-22 18:46 ` Differences between mail-mode and message-mode Reiner Steib
2009-07-23 3:05 ` Stephen J. Turnbull [this message]
2009-07-23 5:03 ` Miles Bader
[not found] ` <jwviqhq14u9.fsf-monnier+emacs@gnu.org>
[not found] ` <E1MSRQV-0006zG-40@fencepost.gnu.org>
[not found] ` <873a8tc92j.fsf@lola.goethe.zz>
[not found] ` <E1MSU0K-0005kX-PZ@fencepost.gnu.org>
2009-07-19 11:56 ` Differences between mail-mode and message-mode - sending mail (was: message-mode is now default?) Reiner Steib
[not found] ` <E1MSO9K-00030v-Go@fencepost.gnu.org>
[not found] ` <87k525mfo7.fsf@catnip.gol.com>
[not found] ` <87eisb715o.fsf@stupidchicken.com>
2009-07-20 20:42 ` message-mode is now default? Reiner Steib
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=874ot4w13w.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=Reiner.Steib@gmx.de \
--cc=ding@gnus.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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).