From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFC: Syntax for logging
Date: Sun, 22 Jun 2003 18:07:00 -0000 [thread overview]
Message-ID: <20030622180719.GA7389@nevyn.them.org> (raw)
In-Reply-To: <3EF5EFAD.6010401@redhat.com>
On Sun, Jun 22, 2003 at 02:04:29PM -0400, Andrew Cagney wrote:
> >Folks may remember the thread from a year ago:
> > RFA: >, >>, and "tee" operators
> > http://sources.redhat.com/ml/gdb-patches/2002-07/msg00458.html
> >
> >I eventually decided that my prefered syntax was:
> > redirect [-a] [FILE [COMMAND]]
> > log [-a] [FILE [COMMAND]]
> >But people didn't care for the use of "-a". I still like this syntax; it's
> >symmetric, and it allows clearly "transcript [-a]". But it's pretty clear
> >to me that we won't reach a consensus on that. I believe Fernando liked it
> >and Andrew didn't.
> >
> >I believe the best alternative at this point is:
> > set logging [redirect|log] [append|overwrite] FILE
>
> > show logging
> >The defaults would be log,overwrite; they could be explicitly specified in
> >order to overwrite a log file named append, if one wanted to do that.
> >
> >Comments, anyone? Shall I repost the patch with that change? I'd really
> >like to see this feature added.
>
> Set show are consistent with the command line syntax. How does one turn
> it off?
Hmm, two options:
set logging
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.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-06-22 18:07 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 [this message]
2003-06-22 18:32 ` Andrew Cagney
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=20030622180719.GA7389@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.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