From: david carlton <carlton@math.Stanford.EDU>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: david carlton <carlton@math.Stanford.EDU>,
Andrew Cagney <ac131313@ges.redhat.com>,
gdb-patches@sources.redhat.com
Cc: carlton@math.Stanford.EDU
Subject: Re: RFA: >, >>, and "tee" operators
Date: Thu, 01 Aug 2002 12:16:00 -0000 [thread overview]
Message-ID: <15689.35085.998410.672452@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <20020801190348.GA4426@nevyn.them.org>
On Thu, 1 Aug 2002 15:03:48 -0400, Daniel Jacobowitz <drow@mvista.com> said:
> +@table @code
> +@kindex redirect
> +@item redirect [-a] [@var{file} [@var{command}]]
> +Redirect all output to @var{file}.
> +@kindex log
> +@item log [-a] [@var{file} [@var{command}]]
> +Copy output to both the screen and @var{file}.
> +@end table
> +
> +Both @code{redirect} and @code{log} default to overwriting the log file,
> +unless @code{-a} is specified.
Personally, I'd say
Both @code{redirect} and @code{log} default to overwriting
$var{file} unless @code{-a} is specified, in which case they append
to $var{file}.
So two changes: replace "the log file" with "$var{file}" (after all,
is it really a log file if you're using redirect instead of log?), and
make it a bit more explicit what the alternate behaviour is, just in
case the person reading the documentation hasn't gotten much sleep
recently. (And I guess I deleted a comma as well, for better or for
worse: I like the comma in your version but don't like once the bit
about appending is added.)
Incidentally, I hope I'm not being out-of-place in making comments
like this or my earlier ones about syntax; I realize that I'm new to
this list and have comparatively little experience with GDB. I
certainly wouldn't comment on matters internal to GDB without more
experience than I have now.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2002-08-01 19:16 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
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 [this message]
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=15689.35085.998410.672452@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=ac131313@ges.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