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 20:51:00 -0000	[thread overview]
Message-ID: <20020731033617.GA11554@nevyn.them.org> (raw)
In-Reply-To: <3D4758A5.8050605@ges.redhat.com>

On Tue, Jul 30, 2002 at 11:25:25PM -0400, Andrew Cagney wrote:
> >So in other words, I'd like to stick with 
> >
> >>>  redirect [-a[ppend]] FILE [COMMAND]
> >>>  log [-a[ppend]] FILE [COMMAND]
> 
> Don't forget that prefix `-' and `--' are valid C operators.  You can't 
> tell the difference between the above and a valid C expressions.  I 
> think that rules `-...' out.

Actually, I still disagree - I think that it remains unambiguous where
to expect an expression and where to expect command-line syntax. 
However, I am interested in finishing this patch, not in continuing a
debate about the command-line syntax, which I don't have time to do at
the moment.  So...

> I also think it should be part of the ``set'' family.  I think it is 
> entirely reasonable for a user to type:
> 	``show logfile''
> set/show can be used in ways that avoid the need for parameters.

Perhaps
  set logging redirect append FILE
  set logging log overwrite FILE
  log log overwrite FILE COMMAND
but "log log" is very unintuitive.

The problem is that now the syntax is very verbose, and I believe much
more complicated than it needs to be.  I really like the one above,
which I keep suggesting, which is not incompatible with "show logging".

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


  reply	other threads:[~2002-07-31  3: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
2002-07-30 13:00                   ` Daniel Jacobowitz
2002-07-30 20:36                     ` Andrew Cagney
2002-07-30 20:51                       ` Daniel Jacobowitz [this message]
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=20020731033617.GA11554@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