From: nicolas.pouillard@gmail.com (Nicolas Pouillard)
Subject: [sup-talk] Piping multiple messages
Date: Wed, 25 Mar 2009 13:20:56 +0100 [thread overview]
Message-ID: <1237983576-sup-4691@ausone.local> (raw)
In-Reply-To: <1237979385-sup-6382@lenin>
Excerpts from vasudeva's message of Wed Mar 25 12:11:51 +0100 2009:
> Excerpts from Nicolas Pouillard's message of Wed Mar 25 04:58:48 -0400 2009:
> > Excerpts from William Morgan's message of Tue Mar 24 22:01:44 +0100 2009:
> > > How many people actually use "|" to modify a search?
> >
> > That's fine to keep '|' for piping, but we need another key for modify a
> > search.
>
> To be honest, I didn't even know that keystroke existed, and I've been
> using sup every day as my primary client for probably a year+. I don't
> see it documented anywhere now that I look. Is there a way to have found
> out about this (and other items) without reading each patch?
After searching something '\something<enter>', if you type '?' you will
see the description of '|'.
--
Nicolas Pouillard
prev parent reply other threads:[~2009-03-25 12:20 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
2009-03-25 8:58 ` Nicolas Pouillard
2009-03-25 11:11 ` vasudeva
2009-03-25 12:20 ` Nicolas Pouillard [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=1237983576-sup-4691@ausone.local \
--to=nicolas.pouillard@gmail.com \
/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