From: Dan Christensen <jdc@uwo.ca>
To: ding@gnus.org
Subject: Re: Change default behavior of gnus-summary-pipe-output?
Date: Wed, 18 Oct 2023 11:52:43 -0400 [thread overview]
Message-ID: <87wmvkszas.fsf@uwo.ca> (raw)
In-Reply-To: <87lec1b2xx.fsf@ericabrahamsen.net>
On Oct 17, 2023, Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
> 1. What do you think about changing the default behavior of the output
> to pipe command to use the raw article?
I think it would be better to change the default.
> 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.
I'm aware of them, but have rarely used them.
Dan
prev parent reply other threads:[~2023-10-18 15:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 16:59 Eric Abrahamsen
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 [this message]
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=87wmvkszas.fsf@uwo.ca \
--to=jdc@uwo.ca \
--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).