unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Tomas Volf <~@wolfsden.cz>
To: 68510@debbugs.gnu.org
Subject: bug#68510: Bug in debbugs' C-u S v
Date: Tue, 16 Jan 2024 16:28:39 +0100	[thread overview]
Message-ID: <Zaagp0pVfmGRSSza@ws> (raw)

[-- Attachment #1: Type: text/plain, Size: 2156 bytes --]

Hello,

I think I found a bug in debbugs, however I am not sure if the bug is in
documentation or in the code.  Steps to reproduce (in emacs -Q):

In *scratch* buffer:
   (require 'debbugs-gnu)
   (debbugs-gnu-bugs 66531)

In the new buffer open the message and navigate cursor to last message from Mike
Gran (47: ).  Now, when I want to reply, I press S v and it opens a buffer with
(addresses are censored):

    To: Mike Gran <xxx>
    Cc: Tomas Volf <xxx>,  "xxx@debbugs-gnu-org" <xxx>
    Subject: Re: bug#66531: [PATCH] ftw: Fix getuid-or-false, getgid-or-false macros.
    From: me@hostname.mail-host-address-is-not-set
    --text follows this line--

So far that is expected.  However when I want to quote the original message, I can, based on the reading of the manual, use C-u S v:

> If prefix argument YANK is non-nil, the original article(s) will be yanked
> automatically.

However while that does work, additional undocumented (and unwanted) changes are
done as well,producing a following message:

    To: Mike Gran <xxx>
    Cc: Tomas Volf <xxx>,  Tomas Volf <xxx>,  control@debbugs-gnu-org,  xxx@debbugs-gnu-org
    Subject: Re: bug#66531: [PATCH] ftw: Fix getuid-or-false, getgid-or-false macros., bug#66531: [PATCH] ftw: Fix getuid-or-false, getgid-or-false macros., bug#66531: [PATCH] ftw: Fix getuid-or-false, getgid-or-false macros., bug#66531: [PATCH] ftw: Fix getuid-or-false, getgid-or-false macros., control message for bug #66531, control message for bug #66531
    From: me@hostname.mail-host-address-is-not-set
    --text follows this line--
    Mike Gran <xxx> writes:
    
    [..]

Notice that the subject is pretty weird, and for some reason there is a control
server in the CC list.  I do not know if this is expected (well, at least I did
not expect it), but it at the very least does not seem to be documented.  Based
on my reading of the C-h k S v I would have expected just the "Mike Gran
<xxx> writes:" change.

Thank you and have a nice day,
Tomas Volf

-- 
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2024-01-16 15:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-16 15:28 Tomas Volf [this message]
2024-01-19 11:55 ` bug#68510: Bug in gnus' C-u S v Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-19 16:10   ` Eric Abrahamsen
2024-01-19 17:05     ` Tomas Volf
2024-01-19 22:03       ` Eric Abrahamsen
2024-01-19 22:29       ` Eric Abrahamsen
2024-01-19 22:50         ` Tomas Volf

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=Zaagp0pVfmGRSSza@ws \
    --to=~@wolfsden.cz \
    --cc=68510@debbugs.gnu.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).