GNU bug report logs -
#67520
29.1; Mention headers
Previous Next
Reported by: Dan Jacobson <jidanni <at> jidanni.org>
Date: Wed, 29 Nov 2023 03:51:02 UTC
Severity: normal
Found in version 29.1
Fixed in version 30.1
Done: Eric Abrahamsen <eric <at> ericabrahamsen.net>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
Eli Zaretskii <eliz <at> gnu.org> writes:
>> From: Dan Jacobson <jidanni <at> jidanni.org>
>> Date: Wed, 29 Nov 2023 11:49:18 +0800
>>
>> This docstring should mention the case where the user wants to forward
>> the entire message, including pristine headers.
>>
>> He tries each in vain, finding that none include the headers.
>>
>> C-c C-f runs the command gnus-summary-mail-forward (found in
>> gnus-summary-mode-map), which is an autoloaded interactive
>> native-compiled Lisp function in ‘gnus-msg.el’.
>>
>> It is bound to C-c C-f and S o m.
>>
>> (gnus-summary-mail-forward &optional ARG POST)
>>
>> Forward the current message(s) to another user.
>> If process marks exist, forward all marked messages;
>> if ARG is nil, see ‘message-forward-as-mime’ and ‘message-forward-show-mml’;
>> if ARG is 1, decode the message and forward directly inline;
>> if ARG is 2, forward message as an rfc822 MIME section;
>> if ARG is 3, decode message and forward as an rfc822 MIME section;
>> if ARG is 4, forward message directly inline;
>> otherwise, use flipped ‘message-forward-as-mime’.
>> If POST, post instead of mail.
>> For the "inline" alternatives, also see the variable
>> ‘message-forward-ignored-headers’.
>
> Eric, any comments?
I didn't understand the request. The docstring should mention that none
of the calling options for `gnus-summary-mail-forward' include the all
the original headers?
This bug report was last modified 1 year and 217 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.