From: Andrew Cagney <ac131313@ges.redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: RFA: >, >>, and "tee" operators
Date: Thu, 25 Jul 2002 10:46:00 -0000 [thread overview]
Message-ID: <3D40371D.6070603@ges.redhat.com> (raw)
In-Reply-To: <20020725161749.GA10862@nevyn.them.org>
> 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 :-).
> 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.
Are you proposing that ``print/FMT'' gets replaced by ``print -FMT''.
There shouldn't be two conflicting syntaxes.
Andrew
next prev parent reply other threads:[~2002-07-25 17:36 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 [this message]
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=3D40371D.6070603@ges.redhat.com \
--to=ac131313@ges.redhat.com \
--cc=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