From: Kai Grossjohann <grossjohann@charly.cs.uni-dortmund.de>
Subject: S D r: bad interaction with TM and/or SEMI
Date: 21 Oct 1997 09:50:22 +0200 [thread overview]
Message-ID: <vaflnzntv0h.fsf@petty.ls6.uni-do> (raw)
In all versions of TM and SEMI that I've used recently, I've had
problems with S D r. The symptom now (Gnus 5.5, SEMI 0.X) is that I
get "wrong type argument: keymapp nil" the first time I do S D r and
"Already editing MIME message" the second time.
I venture to guess that this is because Gnus sets up a message buffer
for the resend, complete with all hooks. But there is really no sense
in running the MIME editing setup hook -- either the message is
already MIME-ified, in which case the hook shouldn't run, or it isn't,
in which case the hook shouldn't run, either.
I suggest that message-setup-hook (and similar hooks) be temporarily
set to nil when setting up a message buffer for S D r.
S D b works fine, btw.
kai
--
~/.signature: No such file or directory
next reply other threads:[~1997-10-21 7:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-21 7:50 Kai Grossjohann [this message]
1997-10-21 14:50 ` Colin Rafferty
1997-10-21 15:06 ` Kai Grossjohann
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=vaflnzntv0h.fsf@petty.ls6.uni-do \
--to=grossjohann@charly.cs.uni-dortmund.de \
/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).