From: Jack Vinson <vinson@unagi.cis.upenn.edu>
Subject: Re: message-ignored-forward-headers (was: Re: gnus-summary-mail-forward - included headers)
Date: 08 Oct 1999 13:41:01 -0500 [thread overview]
Message-ID: <wkg0zlwv9e.fsf@chevax.ecs.umass.edu> (raw)
In-Reply-To: Jim Davidson's message of "08 Oct 1999 09:52:49 -0700"
>>>>> "JD" == Jim Davidson <jdavidso@nospam.com> writes:
JD> Jack Vinson <vinson@unagi.cis.upenn.edu> writes:
>>
>> Does this actually work for anyone? I tried to forward a message and
>> discovered that the forwarded part contained all the headers I didn't want
>> anyway.
>>
JD> I'm experiencing the same behavior. It appears that the function
JD> message-forward includes a spurious call to
JD> (message-narrow-to-head)
Yep. Comment out this call at the end of message-forward and all is well.
The *real* problem is that message-narrow-to-head calls (widen) as its
first activity. As a result, the message is narrowed to its TRUE head
instead of the head of the forwarded message.
Lars, which is more important to fix? It looks like all the
message-narrow-to.*-head.* functions call widen first.
--
Jack Vinson
Bart: No one is interested in my underpants.
next prev parent reply other threads:[~1999-10-08 18:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-14 16:24 gnus-summary-mail-forward - included headers Jim Davidson
1999-09-14 16:51 ` Kai Großjohann
1999-09-14 18:20 ` Toby Speight
1999-09-25 9:18 ` Lars Magne Ingebrigtsen
1999-09-30 23:35 ` message-ignored-forward-headers (was: Re: gnus-summary-mail-forward - included headers) Thomas Hungenberg
1999-10-01 17:33 ` Jack Vinson
1999-10-08 16:52 ` Jim Davidson
1999-10-08 18:41 ` Jack Vinson [this message]
1999-11-06 2:13 ` Lars Magne Ingebrigtsen
1999-11-08 22:31 ` [patch] message-forward-as-mime (was: Re: message-ignored-forward-headers (was: Re: gnus-summary-mail-forward - included headers)) Matt Pharr
1999-11-11 19:32 ` Toni Drabik
1999-10-04 22:51 ` gnus-summary-mail-forward - included headers François Pinard
1999-10-05 8:22 ` Kai Großjohann
1999-10-05 14:15 ` Hrvoje Niksic
1999-11-06 3:15 ` Lars Magne Ingebrigtsen
1999-11-09 6:55 ` Dan Christensen
1999-11-09 17:47 ` Matt Pharr
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=wkg0zlwv9e.fsf@chevax.ecs.umass.edu \
--to=vinson@unagi.cis.upenn.edu \
/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).