From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: Simplify inline forward headers
Date: Mon, 25 Jun 2007 19:36:56 +0900 [thread overview]
Message-ID: <b4mejk0pbg7.fsf@jpl.org> (raw)
In-Reply-To: <m2ps3kmmjv.fsf@sl392.st-edmunds.cam.ac.uk>
>>>>> In <m2ps3kmmjv.fsf@sl392.st-edmunds.cam.ac.uk> Leo wrote:
> ----- Katsumi Yamaoka (2007-06-25) wrote:-----
>>> I often have to inline forward messages to people who are not using
>>> Gnus. However, almost all headers in the original messages are
>>> included which make the emails look messy.
>>
>>> I wonder how to make inline forward only include headers in
>>> gnus-visible-headers.
>>
>> `gnus-visible-headers' is unlikely to contain some headers which are
>> indispensable for forwarding MIME messages.
> By `forwarding MIME messages' do you mean the non-inline alternatives of
> `gnus-summary-mail-forward'?
I meant just inline, i.e., using MML. But I might have
misunderstood; though I'm not quite sure of it, even if removing
all headers in the case where MML is used, it might cause no
problem if `message-remove-ignored-headers' is performed in the
present way. Please note, Gnus doesn't use MML by default when
forwarding signed or encrypted messages.
> We could use another variable (e.g. message-forward-kept-headers) to
> contain headers that should be kept.
I don't want a new variable which is simply an inverse of an
existing variable.
>> You can modify the `message-forward-ignored-headers' variable instead.
>> I don't have an idea of making it remove more headers by default.
> I want to make something like this to work by modifying
> `message-remove-ignored-headers':
> if message-forward-kept-headers is nil,
> `message-forward-ignored-headers' is used; otherwise,
> message-forward-kept-headers is used.
> Ideas?
I don't know what may become *the default values* that satisfy
many users. Although I humbly think adding "^Received:" to the
default value of `message-forward-ignored-headers' might be a
good idea, I'm satisfied with deleting some headers manually. ;-)
next prev parent reply other threads:[~2007-06-25 10:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-25 2:27 Leo
2007-06-25 4:36 ` Katsumi Yamaoka
2007-06-25 9:05 ` Leo
2007-06-25 9:32 ` Leo
2007-06-25 10:36 ` Katsumi Yamaoka [this message]
2007-06-25 12:54 ` Bjørn Mork
2007-06-25 23:47 ` Katsumi Yamaoka
2007-06-26 7:03 ` Katsumi Yamaoka
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=b4mejk0pbg7.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.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).