From: Karl Kleinpaste <karl@charcoal.com>
Subject: Re: C-c C-a was mml-attach-file, now mail-interactive-insert-alias?
Date: 04 Sep 2000 15:34:18 -0400 [thread overview]
Message-ID: <vxkzolo9cjp.fsf@cinnamon.vanillaknot.com> (raw)
In-Reply-To: Neil Crellin's message of "04 Sep 2000 10:06:45 -0700"
This was discussed a couple months ago. It seems that a change to the
how, where, & when of (require 'mail-abbrevs) has induced this change
as an inadvertent side effect, because the message mode keymap has
already been set up when mail-abbrevs is subsequently sucked in,
changing the keymap. Or maybe it was the other way around; I forget.
Anyhow, "Someone With CVS Write Access" (i.e. not me) ought to take a
peek at the revision history again, or just dig out the previous
discussion on this subject, and apply the small patch to be found
somewhere in that discussion to make the keymap work the right way
again.
In the meantime, learn to love `M-m f'.
next prev parent reply other threads:[~2000-09-04 19:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-04 17:06 Neil Crellin
2000-09-04 18:27 ` Andreas Fuchs
2000-09-04 19:17 ` Kai Großjohann
2000-09-04 19:34 ` Karl Kleinpaste [this message]
2000-09-05 17:29 ` Neil Crellin
2000-09-08 23:48 ` Dave Love
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=vxkzolo9cjp.fsf@cinnamon.vanillaknot.com \
--to=karl@charcoal.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).