Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Change default behavior of gnus-summary-pipe-output?
Date: Tue, 17 Oct 2023 09:59:06 -0700	[thread overview]
Message-ID: <87lec1b2xx.fsf@ericabrahamsen.net> (raw)

Hi all,

There was a bug report recently about the behavior of the output-to-pipe
article command in Gnus (bound to "|"), which by default sends the
treated article to the pipe/process, not the raw article. This was
breaking the direct application of some git patches, because the
treatment was inserting newlines where they didn't belong.

The solution[0] was to use the symbolic prefix "M-i r" before running
the "|" command. That switches to sending the raw article instead. This
is the only article output command that allows the user to toggle
raw/treated.

It seems like piping the raw article should be the default, instead.
That ought to reduce the likelihood that users would run into the
symbolic prefix, too, which I have to assume many people don't know
about and don't use.

So my survey is two part:

1. What do you think about changing the default behavior of the output
to pipe command to use the raw article?
2. How many of you are aware of Gnus' symbolic prefixes, and make use of
them? Looks like only 11 commands use it, mostly around sorting groups,
and a couple of scoring commands.

Thanks!
Eric


[0] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=66450#8



             reply	other threads:[~2023-10-17 16:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-17 16:59 Eric Abrahamsen [this message]
2023-10-17 17:15 ` Eric S Fraga
2023-10-17 18:32   ` Stephen Berman
2023-10-17 21:07   ` Eric Abrahamsen
2023-10-18 10:33     ` Eric S Fraga
2023-10-18 15:52 ` Dan Christensen

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=87lec1b2xx.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=ding@gnus.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.
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).