From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 66795@debbugs.gnu.org
Subject: bug#66795: 29.1; debbugs hashcash behavior discrepancy
Date: Wed, 01 Nov 2023 08:37:22 -0700 [thread overview]
Message-ID: <87fs1pa3il.fsf_-_@ericabrahamsen.net> (raw)
In-Reply-To: <87o7gdtudc.fsf@gmx.de> (Michael Albinus's message of "Wed, 01 Nov 2023 15:34:39 +0100")
Michael Albinus <michael.albinus@gmx.de> writes:
> Forward to Eric Abrahamsen; it seems to be rather a Gnus problem
>
> From: Bruno Victal <mirai@makinata.eu>
> Subject: bug#66795: 29.1; debbugs hashcash behavior discrepancy
> To: 66795@debbugs.gnu.org
> Date: Sat, 28 Oct 2023 15:27:11 +0100 (4 days, 1 hour, 8 minutes ago)
>
> 1. Have `(setq message-generate-hashcash t)' in init.el.
> 2. Using debbugs (elpa), open any issue with more than one recipient to
> Cc. (e.g. #66561) with `M-x debbugs-gnu' (optionally followed by `M-x
> debbugs-gnu-get-bug-by-id <RET> …')
> 3. Select message and start replying with `S w'.
> 4. X-Hashcash headers are opportunistically generated and displayed,
> in contrast to a plain 'C-x m' (Message mode) where it only starts
> doing so after `C-c C-c'.
>
> It's strange that the value of `message-generate-hashcash' is ignored
> when debbugs is used. This is undesired behavior since it results in
> redundant or unused X-Hashcash headers when I edit the addresses in the
> Cc or To lines.
I'm not sure where debbugs comes into it -- Gnus will generate hashcash
headers for any reply, during message setup. You don't see anything in
"C-x m" because there's nothing in the To or Cc headers yet. But "S w"
in a regular Gnus summary buffer will also generate the headers.
next prev parent reply other threads:[~2023-11-01 15:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-28 14:27 bug#66795: 29.1; debbugs hashcash behavior discrepancy Bruno Victal
2023-11-01 14:34 ` bug#66795: Fwd: " Michael Albinus
2023-11-01 15:37 ` Eric Abrahamsen [this message]
2024-01-17 12:50 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-10 22:01 ` Eric Abrahamsen
2024-02-11 8:03 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87fs1pa3il.fsf_-_@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=66795@debbugs.gnu.org \
--cc=michael.albinus@gmx.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.
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).