Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFC: Syntax for logging
Date: Sun, 22 Jun 2003 18:32:00 -0000	[thread overview]
Message-ID: <3EF5F649.6050809@redhat.com> (raw)
In-Reply-To: <20030622180719.GA7389@nevyn.them.org>

> 
> Hmm, two options:
>   set logging

Not this.  It should behave like:

(gdb) set architecture
"set architecture" must be followed by "auto" or an architecture name.

>   unset logging
> 
> I like "unset logging"; how about you?  The only thing we use unset for
> at the moment is "unset environment" but I think it extends naturally.

so (slightly wierd) yes this.  Be sure to mention it in the help 
message.  Perhaphs, also accept ``set logging off'', and ``set logging 
on'' as those are the first things I'd try :-)

Hmm, just noticed, the options are optional, I was thinking that they 
were required.

	set logging [redirect|log] [append|overwrite] FILE

The syntax will lead to confusion with things like:

	set logging l
or
	set logging redirect a

suggest instead:

set logging on [FILE]
	default gdb.log, log, append?
set logging off
set logging file FILE
set logging append {true,false}
set logging redirect {true,false}

so that the [FILE] isn't context dependent.  Realisticly, I think people 
will only use:

	set logging on
	set logging off

Andrew



  reply	other threads:[~2003-06-22 18:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-21 17:24 Daniel Jacobowitz
2003-06-21 18:01 ` Doug Evans
2003-06-22 18:04 ` Andrew Cagney
2003-06-22 18:07   ` Daniel Jacobowitz
2003-06-22 18:32     ` Andrew Cagney [this message]
2003-06-22 18:41       ` Daniel Jacobowitz
2003-06-22 19:19         ` 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=3EF5F649.6050809@redhat.com \
    --to=ac131313@redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.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