Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA 4/4] NEWS and documentation for | (pipe) command.
Date: Sun, 21 Apr 2019 05:22:00 -0000	[thread overview]
Message-ID: <83pnpg9bkv.fsf@gnu.org> (raw)
In-Reply-To: <20190420212153.30934-5-philippe.waroquiers@skynet.be> (message	from Philippe Waroquiers on Sat, 20 Apr 2019 23:21:53 +0200)

> From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
> Cc: Philippe Waroquiers <philippe.waroquiers@skynet.be>
> Date: Sat, 20 Apr 2019 23:21:53 +0200
> 
> diff --git a/gdb/NEWS b/gdb/NEWS
> index 5309a8f923..8744659e7b 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -27,6 +27,14 @@
>       'array_indexes', 'symbols', 'unions', 'deref_refs', 'actual_objects',
>       'static_members', 'max_elements', 'repeat_threshold', and 'format'.
>  
> +* New commands
> +
> +pipe [COMMAND] | SHELL_COMMAND
> +| [COMMAND] | SHELL_COMMAND
> +  Executes COMMAND and sends its output to SHELL_COMMAND.
> +  With no COMMAND, repeat the last executed command
> +  and send its output to SHELL_COMMAND.
> +

This is OK.

> +You can also redirect the output of a @value{GDBN} command to a
> +shell command.  See @ref{pipe}.
                   ^^^^^^^^^^^^^^
This isn't incorrect, bur @xref{pipe} is better.

Otherwise, the documentation part is OK, thanks.


  reply	other threads:[~2019-04-21  5:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-20 21:22 [RFA 0/4] Implement " Philippe Waroquiers
2019-04-20 21:22 ` [RFA 4/4] NEWS and documentation for " Philippe Waroquiers
2019-04-21  5:22   ` Eli Zaretskii [this message]
2019-04-20 21:22 ` [RFA 2/4] Implement " Philippe Waroquiers
2019-04-21  5:19   ` Eli Zaretskii
2019-04-21  9:40     ` Philippe Waroquiers
2019-04-21 10:18       ` Eli Zaretskii
2019-04-22 10:30         ` Philippe Waroquiers
2019-04-22 11:08           ` Eli Zaretskii
2019-04-22 13:15             ` Philippe Waroquiers
2019-04-22 13:21               ` Eli Zaretskii
2019-04-24 20:50   ` Tom Tromey
2019-04-25  5:58     ` Eli Zaretskii
2019-04-20 21:22 ` [RFA 3/4] Test the " Philippe Waroquiers
2019-04-24 20:52   ` Tom Tromey
2019-04-20 21:22 ` [RFA 1/4] Add previous_saved_command_line to allow a command to repeat a previous command Philippe Waroquiers
2019-04-24 20:51   ` Tom Tromey
2019-04-22 20:45 ` [RFA 0/4] Implement | (pipe) command Abhijit Halder
2019-04-22 21:14   ` Philippe Waroquiers
2019-04-24 20:53   ` Tom Tromey

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=83pnpg9bkv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=philippe.waroquiers@skynet.be \
    /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