From: Kai Grossjohann <kai@emptydomain.de>
Subject: Re: bug in message.el, message-forward-make-body-plain
Date: Sun, 19 Dec 2004 23:26:38 +0100 [thread overview]
Message-ID: <86d5x5zzz5.fsf@ketchup.de.uu.net> (raw)
In-Reply-To: <87y8ghyf39.fsf@orebokech.com>
Romain Francoise <romain@orebokech.com> writes:
> The test is weird:
>
> (when (and (not current-prefix-arg)
> message-forward-ignored-headers)
>
> how can current-prefix-arg be nil since you call this function from C-u
> C-c C-f? Its value is '(4) here... unless I'm missing something.
There is a variable message-forward-as-mime which inverts the meaning
of the prefix arg.
I think there is still a problem in the code, though. Hm.
Kai
next prev parent reply other threads:[~2004-12-19 22:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-30 20:08 Ted Stern
2004-12-01 8:19 ` Katsumi Yamaoka
2004-12-01 19:15 ` Ted Stern
2004-12-01 19:48 ` Romain Francoise
2004-12-01 21:39 ` Ted Stern
2004-12-01 21:56 ` Romain Francoise
2004-12-02 8:25 ` Katsumi Yamaoka
2004-12-02 9:09 ` Romain Francoise
2004-12-19 22:26 ` Kai Grossjohann [this message]
2004-12-20 18:06 ` Ted Stern
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=86d5x5zzz5.fsf@ketchup.de.uu.net \
--to=kai@emptydomain.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).