Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: RFA: >, >>, and "tee" operators
Date: Tue, 30 Jul 2002 13:00:00 -0000	[thread overview]
Message-ID: <20020730191825.GA17620@nevyn.them.org> (raw)
In-Reply-To: <3D40371D.6070603@ges.redhat.com>

On Thu, Jul 25, 2002 at 01:36:29PM -0400, Andrew Cagney wrote:
> >I think this was raised before (fernando and I discussed it somewhere on 
> >>gdb@).  GDB is used on systems that are not even UNIX like (namely 
> >>DJGPP), trying to tie the syntax to UNIX is such a good idea.  GDB needs 
> >>a syntax spec, the current piece meal aproach is regrettable :-(
> >>
> >>If the command was called ``log'' rather than ``tee'' then I don't think 
> >>we would have problems with ``log -a''.  (I'm not saying that log is the 
> >>right name mind.)
> >
> >
> >Well, I find the DOS-ish '/' separator much nastier than '-' options. 
> 
> The `/' would most likely have come from VMS or a precursor.  VMS has 
> [had?] a remarkably well structured (too well structured?) CLI interface 
> (I show my heritage :-).

Before my day :)

> >A question of personal taste.  ``log'' unfortunately is more like
> >``tee'' than it is like redirection; how about a simple ``redirect''
> >command?
> >
> >  redirect [-a[ppend]] FILE [COMMAND]
> >  log [-a[ppend]] FILE [COMMAND]
> 
> Or `log/a FILE [COMMAND]'  or, hmm, something like:
> 
> 	set log write FILE
> 	set log redirect FILE
> 	set log append FILE
> 	show log
> 
> and
> 
> 	log[/a] FILE command-that-isn't-optional
> 
> Same for redirect.

I don't know about that... write/redirect/append aren't really mutually
exclusive (it's overwrite/append and redirect/tee), and that doesn't
mesh with the feeling of a set command.

> Are you proposing that ``print/FMT'' gets replaced by ``print -FMT''. 
> There shouldn't be two conflicting syntaxes.

Well, I don't have a problem with reserving / for FMT sequences
(anything that modifies how output is printed) and - for options
(anything that modifies what gets done).  I think '/' is only used for
format sequences right now; at least I don't see anything otherwise in
the manual besides display, print, and x.  Heck, I actually think
separating format specifiers and options this way is intuitive.


So in other words, I'd like to stick with 
> >  redirect [-a[ppend]] FILE [COMMAND]
> >  log [-a[ppend]] FILE [COMMAND]

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-07-30 19:18 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
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 [this message]
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=20020730191825.GA17620@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@ges.redhat.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