Gnus development mailing list
 help / color / mirror / Atom feed
From: Michael Albinus <>
To: Eric Abrahamsen <>
Subject: Re: Replies, (very) wide replies, yanking, and the prefix argument
Date: Sat, 20 Jan 2024 09:28:44 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Eric Abrahamsen's message of "Fri, 19 Jan 2024 14:47:49 -0800")

Eric Abrahamsen <> writes:

Hi Eric,

> I'm surprised that no one hit this bug before, and I'm not sure what to
> do with it. We have "S V" (gnus-summary-very-wide-reply-with-original)
> that uses the prefix argument correctly *and* yanks message content
> correctly, so I'm not sure there's a need for "S v" to handle the prefix
> argument both ways. I suppose I could make it handle the prefix argument
> both ways, though.
> Let me know if anyone has any thoughts on this.

I don't know anything about the implementation in Gnus. But as a data
point, we have also the 'S w' and 'S W' key bindings in the Summary
buffer. And 'C-u S w' seems to behave correctly. Perhaps you could
compare how those commands are implemented?

Best regards, Michael.

  reply	other threads:[~2024-01-20 20:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-19 22:47 Eric Abrahamsen
2024-01-20  8:28 ` Michael Albinus [this message]
2024-01-21  3:28   ` Eric Abrahamsen

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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.
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 NNTP newsgroup(s).