From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15466 invoked by alias); 25 Jul 2002 03:10:22 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 15458 invoked from network); 25 Jul 2002 03:10:21 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 25 Jul 2002 03:10:21 -0000 Received: from dsl254-114-118.nyc1.dsl.speakeasy.net ([216.254.114.118] helo=nevyn.them.org ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 17XZ19-0004ke-00; Wed, 24 Jul 2002 22:10:19 -0500 Received: from drow by nevyn.them.org with local (Exim 3.35 #1 (Debian)) id 17XZ1G-0005Id-00; Wed, 24 Jul 2002 23:10:26 -0400 Date: Wed, 24 Jul 2002 20:14:00 -0000 From: Daniel Jacobowitz To: Andrew Cagney Cc: Tom Tromey , gdb-patches@sources.redhat.com Subject: Re: RFA: >, >>, and "tee" operators Message-ID: <20020725031026.GA20117@nevyn.them.org> Mail-Followup-To: Andrew Cagney , Tom Tromey , gdb-patches@sources.redhat.com References: <20020723183956.GA28558@nevyn.them.org> <871y9ub6fj.fsf@fleche.redhat.com> <20020723192325.GA30738@nevyn.them.org> <87d6te8a6o.fsf@fleche.redhat.com> <20020723202051.GA5427@nevyn.them.org> <3D3F5BDF.2050209@ges.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D3F5BDF.2050209@ges.redhat.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2002-07/txt/msg00501.txt.bz2 On Wed, Jul 24, 2002 at 10:01:03PM -0400, Andrew Cagney wrote: > >On Tue, Jul 23, 2002 at 02:24:15PM -0600, Tom Tromey wrote: > > > >>>>>>> "Daniel" == Daniel Jacobowitz 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? > > Does the `transcript FILE' command send both the user input (prompts?) > and output to the file (output also to the console)? Like unix script? [Speaking for my patch] Nope. Prompts and user input are not logged. Output goes only to a file. Something like `script' might be useful but that's a patch for another day. > I guess the corresponding ``tee FILE'' command just writes output? Output goes to the file and to the normal output channel. Still no prompts or input. > I think there is also a need for a tempoary redirection. So I guess > either the obscure: > >FILE ... > maybe? > log FILE ..... How about "transcript FILE "? There's some quoting badness but for the moment I'm willing to just disallow spaces in the filename. Much more straightforward that way. That doesn't allow for: transcript | command args but that's also an OK restriction, I think... > GDB's option identifier is ``/'' and not ``-''. See the print/ > commands. ``-'' has the problem of being a valid expression operator. > I should note that the current parser is pretty broken. It can't > differentiate between: > transcript/f > transcript /f > (sigh) but that is a fixable problem. GDB's option identifier varies, actually; symbol-file -readnow, add-symbol-file -s
are the only two I see offhand. We only use / for print format characters. Mostly we just drop them all on one line. I'd rather stick with '-' as it's more familiar to most of our audience, particularly with 'tee -a'. -- Daniel Jacobowitz Carnegie Mellon University MontaVista Software Debian GNU/Linux Developer