From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Piping multiple messages
Date: Tue, 24 Mar 2009 14:01:44 -0700 [thread overview]
Message-ID: <1237927869-sup-4016@entry> (raw)
In-Reply-To: <a412e2a70903241245s20144fd2uec3ccfc84a6b8da5@mail.gmail.com>
Reformatted excerpts from Mark Alexander's message of 2009-03-24:
> Sup has been stable enough that I've pretty much abandoned mutt,
Awesome to hear.
> A simpler way for the user, but perhaps harder to implement, would be
> to tag the threads as before, and then use a new "pipe all tagged
> threads" command. Unfortunately, the '|' command at the thread-index
> level already means "modify search".
This is the way to go. No need to play around with the thread structure.
We already individual message piping in thread-view-mode, so adding it
to thread-index-mode shouldn't be hard.
The keyboard command is a bit unfortunate though.
How many people actually use "|" to modify a search?
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2009-03-24 21:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 19:45 Mark Alexander
2009-03-24 21:01 ` William Morgan [this message]
2009-03-25 8:58 ` Nicolas Pouillard
2009-03-25 11:11 ` vasudeva
2009-03-25 12:20 ` Nicolas Pouillard
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=1237927869-sup-4016@entry \
--to=wmorgan-sup@masanjin.net \
/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