GNU bug report logs -
#66330
28.2; Gnus wide reply (S W) changes Subject header when used from Debbugs thread
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 66330 in the body.
You can then email your comments to 66330 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
mirai <at> makinata.eu, bug-gnu-emacs <at> gnu.org
:
bug#66330
; Package
emacs
.
(Wed, 04 Oct 2023 00:27:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
mirai <at> makinata.eu, bug-gnu-emacs <at> gnu.org
.
(Wed, 04 Oct 2023 00:27:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hi,
When attempting to reply from an Emacs Debbugs thread specific email,
the Subject line gets set to the subject of the first email in the
thread rather than to that of the specific email I'm replying to, which
looses context.
Example/reproducer:
$ guix shell --container emacs-no-x emacs-debbugs -- emacs
From the launched Emacs:
1. M-x debbugs-gnu-bugs 65479
2. Press 'a' to load the bug despite the lack of SSL certificates.
3. Navigate to the message titled:
[bug#65479] [PATCH core-updates 02/61] gnu: Add docbook-xml-5.
4. Press S W to send a wide reply.
5. Observe that the Subject header in the email response being edited
has been changed to "Re: bug#65479: [PATCH core-updates 00/61] The
Draining of the XML & DocBook Swamp.", that is, the original subject of
the "bug" (its first message).
I haven't been able to explain what causes that, but I've found where it
occurs. Following the original 'gnus-article-wide-reply-with-original'
call, it eventually calls to 'message-setup-1', and the Subject
modification happens by unknown code (hooks?) just before the line 6870
("(run-hooks 'message-setup-hook)") runs:
--8<---------------cut here---------------start------------->8---
(defun message-setup-1 (headers &optional yank-action actions return-action)
(dolist (action actions)
(condition-case nil
;; FIXME: Use functions rather than expressions!
(add-to-list 'message-send-actions
`(apply #',(car action) ',(cdr action)))))
(setq message-return-action return-action)
[...]
(run-hooks 'message-signature-setup-hook)
(message-insert-signature)
(save-restriction
(message-narrow-to-headers)
(run-hooks 'message-header-setup-hook))
(setq buffer-undo-list nil)
(when message-generate-hashcash
;; Generate hashcash headers for recipients already known
(mail-add-payment-async))
===> Subject header changed HERE
;; Gnus posting styles are applied via buffer-local `message-setup-hook'
;; values.
(run-hooks 'message-setup-hook)
;; Do this last to give it precedence over posting styles, etc.
(when (message-mail-p)
(save-restriction
(message-narrow-to-headers)
(if message-alternative-emails
(message-use-alternative-email-as-from))))
(message-position-point)
;; Allow correct handling of `message-checksum' in `message-yank-original':
(set-buffer-modified-p nil)
(undo-boundary)
;; rmail-start-mail expects message-mail to return t (Bug#9392)
t)
--8<---------------cut here---------------end--------------->8---
Would someone be able to explain what is responsible for this? It seems
to me it'd be preferable if the subject of the message I'm replying to
was kept rather than replaced this way, to preserve context.
--
Thanks,
Maxim
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#66330
; Package
emacs
.
(Wed, 04 Oct 2023 07:31:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 66330 <at> debbugs.gnu.org (full text, mbox):
> Cc: Bruno Victal <mirai <at> makinata.eu>
> From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
> Date: Tue, 03 Oct 2023 20:26:26 -0400
>
> When attempting to reply from an Emacs Debbugs thread specific email,
> the Subject line gets set to the subject of the first email in the
> thread rather than to that of the specific email I'm replying to, which
> looses context.
The Subject lines of emails pertaining to a discussion of a bug should
never be changed. So I see no problem here, unless I'm missing
something.
Michael, am I wrong?
> 1. M-x debbugs-gnu-bugs 65479
>
> 2. Press 'a' to load the bug despite the lack of SSL certificates.
>
> 3. Navigate to the message titled:
> [bug#65479] [PATCH core-updates 02/61] gnu: Add docbook-xml-5.
>
> 4. Press S W to send a wide reply.
>
> 5. Observe that the Subject header in the email response being edited
> has been changed to "Re: bug#65479: [PATCH core-updates 00/61] The
> Draining of the XML & DocBook Swamp.", that is, the original subject of
> the "bug" (its first message).
This is a bad Subject line to begin with, from where I stand: it
should not include the patch series numbers, and it should not assume
there will be additional messages with different series numbers.
The Subject lines in a bug/issue discussion should describe the
bug/issue, not the patches sent to fix the issue.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#66330
; Package
emacs
.
(Wed, 04 Oct 2023 07:54:01 GMT)
Full text and
rfc822 format available.
Message #11 received at 66330 <at> debbugs.gnu.org (full text, mbox):
Eli Zaretskii <eliz <at> gnu.org> writes:
Hi Eli,
>> When attempting to reply from an Emacs Debbugs thread specific email,
>> the Subject line gets set to the subject of the first email in the
>> thread rather than to that of the specific email I'm replying to, which
>> looses context.
>
> The Subject lines of emails pertaining to a discussion of a bug should
> never be changed. So I see no problem here, unless I'm missing
> something.
>
> Michael, am I wrong?
Well, we haven't documented such a rule. But based on my experience I
would agree. There's often a message in the bug-gnu-emacs <at> gnu.org ML
with the subject "bug#xxxxx: Patch" or alike, which doesn't help. I'm
too old to remember all the bug numbers and their related topic, and I
read only messages in that ML with topics I'm interested in.
>> 1. M-x debbugs-gnu-bugs 65479
>>
>> 2. Press 'a' to load the bug despite the lack of SSL certificates.
>>
>> 3. Navigate to the message titled:
>> [bug#65479] [PATCH core-updates 02/61] gnu: Add docbook-xml-5.
>>
>> 4. Press S W to send a wide reply.
>>
>> 5. Observe that the Subject header in the email response being edited
>> has been changed to "Re: bug#65479: [PATCH core-updates 00/61] The
>> Draining of the XML & DocBook Swamp.", that is, the original subject of
>> the "bug" (its first message).
>
> This is a bad Subject line to begin with, from where I stand: it
> should not include the patch series numbers, and it should not assume
> there will be additional messages with different series numbers.
>
> The Subject lines in a bug/issue discussion should describe the
> bug/issue, not the patches sent to fix the issue.
D'accord. But I guess the subject line quoted here is created by a tool
of the guix-patches toolchain. So first we shall agree about the rules
of that toolchain (I'm from Emacs, I won't dictate anything!).
If this is an agreed behavior, we could discuss about a debbugs-gnu user
option how to handle the subject line of replies, with a different
default value for guix-patches messages. The global default shouldn't be
changed.
Well, we even have already guix specific code, see debbugs-guix.el. I
would appreciate if somebody from the guix project supports me in
writing such a patch.
Best regards, Michael.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#66330
; Package
emacs
.
(Wed, 04 Oct 2023 08:33:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 66330 <at> debbugs.gnu.org (full text, mbox):
Michael Albinus <michael.albinus <at> gmx.de> writes:
>>> 5. Observe that the Subject header in the email response being edited
>>> has been changed to "Re: bug#65479: [PATCH core-updates 00/61] The
>>> Draining of the XML & DocBook Swamp.", that is, the original subject of
>>> the "bug" (its first message).
>>
>> This is a bad Subject line to begin with, from where I stand: it
>> should not include the patch series numbers, and it should not assume
>> there will be additional messages with different series numbers.
>>
>> The Subject lines in a bug/issue discussion should describe the
>> bug/issue, not the patches sent to fix the issue.
>
> D'accord. But I guess the subject line quoted here is created by a tool
> of the guix-patches toolchain. So first we shall agree about the rules
> of that toolchain (I'm from Emacs, I won't dictate anything!).
The `[PATCH patch-number/patch-count] Subject` subject format is also the
generate format for Git patch-series. The Guix subject format is a
variant of this.
The subject changing could be an issue outside of Gnus. E.g when
responding to a patch in git patch series outside of Guix.
However I think it is a general issue that mail clients append Re: or
some localized variation of it. The issue should also be reported to
Guix.
Other ticket/bugtracking systems might not like changing the subject
either.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#66330
; Package
emacs
.
(Wed, 04 Oct 2023 08:46:01 GMT)
Full text and
rfc822 format available.
Message #17 received at 66330 <at> debbugs.gnu.org (full text, mbox):
> From: Björn Bidar <bjorn.bidar <at> thaodan.de>
> Cc: Eli Zaretskii <eliz <at> gnu.org>, mirai <at> makinata.eu,
> 66330 <at> debbugs.gnu.org, Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
> Date: Wed, 04 Oct 2023 11:31:55 +0300
>
> Michael Albinus <michael.albinus <at> gmx.de> writes:
>
> >> The Subject lines in a bug/issue discussion should describe the
> >> bug/issue, not the patches sent to fix the issue.
> >
> > D'accord. But I guess the subject line quoted here is created by a tool
> > of the guix-patches toolchain. So first we shall agree about the rules
> > of that toolchain (I'm from Emacs, I won't dictate anything!).
>
> The `[PATCH patch-number/patch-count] Subject` subject format is also the
> generate format for Git patch-series. The Guix subject format is a
> variant of this.
>
> The subject changing could be an issue outside of Gnus. E.g when
> responding to a patch in git patch series outside of Guix.
>
> However I think it is a general issue that mail clients append Re: or
> some localized variation of it.
Re: and its localized variants are not a problem: all Emacs MUAs
support that and know how to ignore them for threading purposes.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#66330
; Package
emacs
.
(Wed, 04 Oct 2023 09:12:02 GMT)
Full text and
rfc822 format available.
Message #20 received at 66330 <at> debbugs.gnu.org (full text, mbox):
Eli Zaretskii <eliz <at> gnu.org> writes:
Hi Eli,
>> The subject changing could be an issue outside of Gnus. E.g when
>> responding to a patch in git patch series outside of Guix.
>>
>> However I think it is a general issue that mail clients append Re: or
>> some localized variation of it.
>
> Re: and its localized variants are not a problem: all Emacs MUAs
> support that and know how to ignore them for threading purposes.
This is right in general. They have problems with cascaded localized
prefixes, like "Re: AW: ". But that's another problem, and an edge case
rather. Nothing I worry about.
Best regards, Michael.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#66330
; Package
emacs
.
(Wed, 04 Oct 2023 09:30:02 GMT)
Full text and
rfc822 format available.
Message #23 received at 66330 <at> debbugs.gnu.org (full text, mbox):
Björn Bidar <bjorn.bidar <at> thaodan.de> writes:
Hi Björn,
>> D'accord. But I guess the subject line quoted here is created by a tool
>> of the guix-patches toolchain. So first we shall agree about the rules
>> of that toolchain (I'm from Emacs, I won't dictate anything!).
>
> The `[PATCH patch-number/patch-count] Subject` subject format is also the
> generate format for Git patch-series. The Guix subject format is a
> variant of this.
So perhaps we check the subject of the message we reply to for
--8<---------------cut here---------------start------------->8---
(rx "[PATCH" (? blank (1+ digit) "/" (1+ digit)) "]")
--8<---------------cut here---------------end--------------->8---
If it matches, we use the subject of the message for the reply, rather
than the title of the bug report.
The regexp should be offered as user option, of course.
Best regards, Michael.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#66330
; Package
emacs
.
(Wed, 04 Oct 2023 12:12:02 GMT)
Full text and
rfc822 format available.
Message #26 received at 66330 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Maxim Cournoyer <maxim.cournoyer <at> gmail.com> writes:
> Hi,
Hi Maxim,
> Would someone be able to explain what is responsible for this? It seems
> to me it'd be preferable if the subject of the message I'm replying to
> was kept rather than replaced this way, to preserve context.
FTR, this behavior is due to setting a default subject via
gnus-posting-styles in debbugs-gnu-summary-mode. Could you please check
whether the appended patch helps?
Best regards, Michael.
[Message part 2 (text/x-patch, attachment)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#66330
; Package
emacs
.
(Wed, 04 Oct 2023 14:59:02 GMT)
Full text and
rfc822 format available.
Message #29 received at 66330 <at> debbugs.gnu.org (full text, mbox):
Hello,
Michael Albinus <michael.albinus <at> gmx.de> writes:
> Eli Zaretskii <eliz <at> gnu.org> writes:
>
> Hi Eli,
>
>>> When attempting to reply from an Emacs Debbugs thread specific email,
>>> the Subject line gets set to the subject of the first email in the
>>> thread rather than to that of the specific email I'm replying to, which
>>> looses context.
>>
>> The Subject lines of emails pertaining to a discussion of a bug should
>> never be changed. So I see no problem here, unless I'm missing
>> something.
>>
>> Michael, am I wrong?
>
> Well, we haven't documented such a rule. But based on my experience I
> would agree. There's often a message in the bug-gnu-emacs <at> gnu.org ML
> with the subject "bug#xxxxx: Patch" or alike, which doesn't help. I'm
> too old to remember all the bug numbers and their related topic, and I
> read only messages in that ML with topics I'm interested in.
>
>>> 1. M-x debbugs-gnu-bugs 65479
>>>
>>> 2. Press 'a' to load the bug despite the lack of SSL certificates.
>>>
>>> 3. Navigate to the message titled:
>>> [bug#65479] [PATCH core-updates 02/61] gnu: Add docbook-xml-5.
>>>
>>> 4. Press S W to send a wide reply.
>>>
>>> 5. Observe that the Subject header in the email response being edited
>>> has been changed to "Re: bug#65479: [PATCH core-updates 00/61] The
>>> Draining of the XML & DocBook Swamp.", that is, the original subject of
>>> the "bug" (its first message).
>>
>> This is a bad Subject line to begin with, from where I stand: it
>> should not include the patch series numbers, and it should not assume
>> there will be additional messages with different series numbers.
>>
>> The Subject lines in a bug/issue discussion should describe the
>> bug/issue, not the patches sent to fix the issue.
When working on bugs, I agree this behavior makes sense, where the
original bug title should be kept around. I'm fine with that behavior
for the 'bug-guix' tracker, which tracks bugs. Where I'd like to be
able to customize/change that behavior is when working with *patches*
posted to guix-patches, which is also hosted on Debbugs.
These patches typically get sent via 'git send-email' and include in
their subject the patch number, e.g. [PATCH v2 12/62]. I want this
preserved when reviewing the patch, so that participant knows what was
reviewed.
> D'accord. But I guess the subject line quoted here is created by a tool
> of the guix-patches toolchain. So first we shall agree about the rules
> of that toolchain (I'm from Emacs, I won't dictate anything!).
>
> If this is an agreed behavior, we could discuss about a debbugs-gnu user
> option how to handle the subject line of replies, with a different
> default value for guix-patches messages. The global default shouldn't be
> changed.
That sounds good to me.
> Well, we even have already guix specific code, see debbugs-guix.el. I
> would appreciate if somebody from the guix project supports me in
> writing such a patch.
I'm willing to work on it. It seems you draft a plan in another reply,
which I'll look at now.
--
Thanks,
Maxim
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#66330
; Package
emacs
.
(Wed, 04 Oct 2023 16:35:02 GMT)
Full text and
rfc822 format available.
Message #32 received at 66330 <at> debbugs.gnu.org (full text, mbox):
> From: Michael Albinus <michael.albinus <at> gmx.de>
> Cc: Björn Bidar <bjorn.bidar <at> thaodan.de>,
> mirai <at> makinata.eu,
> 66330 <at> debbugs.gnu.org, maxim.cournoyer <at> gmail.com
> Date: Wed, 04 Oct 2023 11:11:23 +0200
>
> Eli Zaretskii <eliz <at> gnu.org> writes:
>
> > Re: and its localized variants are not a problem: all Emacs MUAs
> > support that and know how to ignore them for threading purposes.
>
> This is right in general. They have problems with cascaded localized
> prefixes, like "Re: AW: ".
Maybe some of them do, but not all.
> But that's another problem, and an edge case rather. Nothing I worry
> about.
Right.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#66330
; Package
emacs
.
(Wed, 04 Oct 2023 20:13:02 GMT)
Full text and
rfc822 format available.
Message #35 received at 66330 <at> debbugs.gnu.org (full text, mbox):
Hi Michael,
Michael Albinus <michael.albinus <at> gmx.de> writes:
> Maxim Cournoyer <maxim.cournoyer <at> gmail.com> writes:
>
>> Hi,
>
> Hi Maxim,
>
>> Would someone be able to explain what is responsible for this? It seems
>> to me it'd be preferable if the subject of the message I'm replying to
>> was kept rather than replaced this way, to preserve context.
>
> FTR, this behavior is due to setting a default subject via
> gnus-posting-styles in debbugs-gnu-summary-mode. Could you please check
> whether the appended patch helps?
I've applied the patch and retried my original reproducer; it passes the
test! So it seems useful to me already in the current form, thank you!
Another thing that could be nice for the future would be some way for
the user to customize the gnus-posting-styles used by Debbugs. That way
I believe you could modify its behavior only for some particular
"group", e.g. when sending to 'guix-patches'; but that seems trickier
to implement.
So I think the solution you propose is satisfactory!
--
Thanks,
Maxim
Reply sent
to
Michael Albinus <michael.albinus <at> gmx.de>
:
You have taken responsibility.
(Thu, 05 Oct 2023 07:54:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
:
bug acknowledged by developer.
(Thu, 05 Oct 2023 07:54:02 GMT)
Full text and
rfc822 format available.
Message #40 received at 66330-done <at> debbugs.gnu.org (full text, mbox):
Maxim Cournoyer <maxim.cournoyer <at> gmail.com> writes:
> Hi Michael,
Hi Maxim,
>> FTR, this behavior is due to setting a default subject via
>> gnus-posting-styles in debbugs-gnu-summary-mode. Could you please check
>> whether the appended patch helps?
>
> I've applied the patch and retried my original reproducer; it passes the
> test! So it seems useful to me already in the current form, thank you!
>
> Another thing that could be nice for the future would be some way for
> the user to customize the gnus-posting-styles used by Debbugs. That way
> I believe you could modify its behavior only for some particular
> "group", e.g. when sending to 'guix-patches'; but that seems trickier
> to implement.
>
> So I think the solution you propose is satisfactory!
Thanks for the feedback. I've applied the patch to the GNU ELPA
repository, and released debbugs 0.37. Shall be visible in a couple of
hours.
Further changes might be possible. But as you've said it is more
complex, because some of the settings in gnus-posting-styles must be
preserved. So we'll better wait for further requests if any.
Closing the bug.
Best regards, Michael.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#66330
; Package
emacs
.
(Thu, 05 Oct 2023 13:01:02 GMT)
Full text and
rfc822 format available.
Message #43 received at 66330-done <at> debbugs.gnu.org (full text, mbox):
Hi Michael,
Michael Albinus <michael.albinus <at> gmx.de> writes:
[...]
> Thanks for the feedback. I've applied the patch to the GNU ELPA
> repository, and released debbugs 0.37. Shall be visible in a couple of
> hours.
>
> Further changes might be possible. But as you've said it is more
> complex, because some of the settings in gnus-posting-styles must be
> preserved. So we'll better wait for further requests if any.
>
> Closing the bug.
Excellent, thanks for the prompt resolution :-).
--
Thanks,
Maxim
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#66330
; Package
emacs
.
(Fri, 06 Oct 2023 06:49:01 GMT)
Full text and
rfc822 format available.
Message #46 received at 66330 <at> debbugs.gnu.org (full text, mbox):
Michael Albinus <michael.albinus <at> gmx.de> writes:
> Eli Zaretskii <eliz <at> gnu.org> writes:
>
> Hi Eli,
>
>>> The subject changing could be an issue outside of Gnus. E.g when
>>> responding to a patch in git patch series outside of Guix.
>>>
>>> However I think it is a general issue that mail clients append Re: or
>>> some localized variation of it.
>>
>> Re: and its localized variants are not a problem: all Emacs MUAs
>> support that and know how to ignore them for threading purposes.
>
> This is right in general. They have problems with cascaded localized
> prefixes, like "Re: AW: ". But that's another problem, and an edge case
> rather. Nothing I worry about.
It depends on how far much you interact with people that don't speak
English as their native language.
But then it's a minor issue even it's not an edge case.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Fri, 03 Nov 2023 11:24:08 GMT)
Full text and
rfc822 format available.
This bug report was last modified 1 year and 230 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.