From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 67520@debbugs.gnu.org, Dan Jacobson <jidanni@jidanni.org>
Subject: bug#67520: 29.1; Mention headers
Date: Wed, 29 Nov 2023 07:31:14 -0800 [thread overview]
Message-ID: <87edg8o9tp.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <83o7fc7m6u.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 29 Nov 2023 14:56:09 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Dan Jacobson <jidanni@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?
next prev parent reply other threads:[~2023-11-29 15:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 3:49 bug#67520: 29.1; Mention headers Dan Jacobson
2023-11-29 12:56 ` Eli Zaretskii
2023-11-29 15:31 ` Eric Abrahamsen [this message]
2023-11-30 6:02 ` Dan Jacobson
2023-12-04 1:39 ` Eric Abrahamsen
2023-12-04 3:30 ` Dan Jacobson
2023-12-05 4:26 ` Eric Abrahamsen
2023-12-05 5:06 ` Dan Jacobson
2023-12-06 15:09 ` Eric Abrahamsen
2023-12-08 5:17 ` Dan Jacobson
2023-12-08 17:42 ` Eric Abrahamsen
2023-12-08 22:24 ` jidanni
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87edg8o9tp.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=67520@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jidanni@jidanni.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).