From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 66795@debbugs.gnu.org, mirai@makinata.eu
Subject: bug#66795: 29.1; debbugs hashcash behavior discrepancy
Date: Sat, 10 Feb 2024 14:01:18 -0800 [thread overview]
Message-ID: <87jzncvv0x.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87mst486ow.fsf@gmx.de> (Michael Albinus's message of "Wed, 17 Jan 2024 13:50:39 +0100")
Michael Albinus <michael.albinus@gmx.de> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
> Hi,
>
>>> 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.
>
> I don't know where we are now. Is it an error? Is it an error triggered
> only in debbugs? Or isn't it an error at all?
I don't know! I installed hashcash and turned it on, and couldn't see
any difference in behavior between replies from debbugs summary buffers
and regular Gnus summary buffers.
next prev parent reply other threads:[~2024-02-10 22:01 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87jzncvv0x.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=66795@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=mirai@makinata.eu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.