From: Daniel Jacobowitz <drow@mvista.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: >, >>, and "tee" operators
Date: Tue, 23 Jul 2002 13:58:00 -0000 [thread overview]
Message-ID: <20020723202051.GA5427@nevyn.them.org> (raw)
In-Reply-To: <87d6te8a6o.fsf@fleche.redhat.com>
On Tue, Jul 23, 2002 at 02:24:15PM -0600, Tom Tromey wrote:
> >>>>> "Daniel" == Daniel Jacobowitz <drow@mvista.com> writes:
>
> >> transcript > FILE
> >> transcript >> FILE
> >> transcript | COMMAND
>
> Daniel> I don't like this syntax very much. It looks too much like
> Daniel> dumping the output of a command ("transcript") to the file,
> Daniel> not like a redirection for the future output.
>
> Good point.
>
> Daniel> Also - is piping to a command actually useful?
>
> I don't know. I haven't even been running with this patch in place,
> since the feature in general is only occasionally useful to me. I
> thought I saw a request for this (piping to a command)?
>
> Daniel> Hmm... How do you feel about:
> Daniel> transcript [-append] FILE
> Daniel> tee [-append] FILE
> Daniel> Where transcript replaces ">" and ">>"?
>
> That looks good to me. Or even `transcript [-tee] [-append] FILE'.
> Or maybe `[-notee]', with tee as the default.
I'd rather have tee as the default, also. But -notee doesn't look
right, so I left it as two commands. Anyone else out on the list have
a suggestion?
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-07-23 20:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 11:51 Daniel Jacobowitz
2002-07-23 12:23 ` Tom Tromey
2002-07-23 13:18 ` Daniel Jacobowitz
2002-07-23 13:20 ` Tom Tromey
2002-07-23 13:58 ` Daniel Jacobowitz [this message]
2002-07-24 20:10 ` Andrew Cagney
2002-07-24 20:14 ` Daniel Jacobowitz
2002-07-25 9:17 ` Andrew Cagney
2002-07-25 10:36 ` Daniel Jacobowitz
2002-07-25 10:46 ` Andrew Cagney
2002-07-30 13:00 ` Daniel Jacobowitz
2002-07-30 20:36 ` Andrew Cagney
2002-07-30 20:51 ` Daniel Jacobowitz
2002-07-30 20:58 ` Andrew Cagney
2002-07-30 22:45 ` Daniel Jacobowitz
2002-07-31 9:36 ` david carlton
2002-07-31 9:39 ` Daniel Jacobowitz
2002-08-01 8:05 ` Andrew Cagney
2002-08-01 10:24 ` david carlton
2002-08-01 12:03 ` Daniel Jacobowitz
2002-08-01 12:16 ` david carlton
2002-08-13 15:20 ` Fernando Nasser
2002-07-23 14:23 ` Grant Edwards
2002-07-24 1:59 ` Eli Zaretskii
2002-07-24 19:01 ` Andrew Cagney
2002-07-24 22:15 ` Daniel Jacobowitz
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=20020723202051.GA5427@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=tromey@redhat.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