Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: Pedro Alves <palves@redhat.com>, Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2.1] Introduce the "with" command
Date: Sat, 22 Jun 2019 10:30:00 -0000	[thread overview]
Message-ID: <1561199437.1556.1.camel@skynet.be> (raw)
In-Reply-To: <918fb7a7-4c62-68cd-006a-8d213b26d571@redhat.com>

On Wed, 2019-06-19 at 18:20 +0100, Pedro Alves wrote:
> Here's the updated full patch that incorporates the changes addressing
> both Eli's and Philippe's comments.
I quickly re-read the patch and did some trials.

Two small remarks:
* The tests related to "maint with" are failing.
  It looks like this patch misses the change
  "maint test-settings" to "maint set|show test-settings".
* Maybe it would be worth expanding slightly the on-line help?
What about:

(gdb) help with
Temporarily set SETTING to VALUE, run COMMAND, and restore SETTING.
Usage: with SETTING [VALUE] [-- COMMAND]
Usage: w SETTING [VALUE] [-- COMMAND]
With no COMMAND, repeats the last executed command.

SETTING is any setting you can change with the "set" subcommands.
Examples:
  with language pascal -- print obj
  with print elements unlimited -- print obj
  
Multiple settings can be changed using nested with, and abbreviations
can be used for commands and/or values.
Example:
  w la p -- w p el u -- p obj
(gdb) 


Thanks

Philippe


  reply	other threads:[~2019-06-22 10:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-18  0:39 [PATCH v2 0/4] " Pedro Alves
2019-06-18  0:39 ` [PATCH v2 1/4] Fix defaults of some "maint test-settings" subcommands Pedro Alves
2019-06-18  0:39 ` [PATCH v2 3/4] "maint test-settings set/show" -> "maint set/show test-settings" Pedro Alves
2019-06-18 16:35   ` Eli Zaretskii
2019-06-18  0:39 ` [PATCH v2 2/4] Fix a few comments in maint-test-settings.c Pedro Alves
2019-06-18  0:39 ` [PATCH v2 4/4] Introduce the "with" command Pedro Alves
2019-06-18 16:42   ` Eli Zaretskii
2019-06-19 15:46     ` Pedro Alves
2019-06-19 16:53       ` Eli Zaretskii
2019-06-19 17:20         ` [PATCH v2.1] " Pedro Alves
2019-06-22 10:30           ` Philippe Waroquiers [this message]
2019-06-22 11:48             ` Pedro Alves
2019-06-22 12:09               ` Philippe Waroquiers
2019-06-19  0:34 ` [PATCH v2 0/4] " Philippe Waroquiers
2019-06-19 13:05   ` Pedro Alves
2019-06-19 13:40     ` Philippe Waroquiers
2019-07-03 12:49 ` Pedro Alves
2019-08-02 23:24   ` New FAIL on gdb.base/with.exp on native-extended-gdbserver (was: Re: [PATCH v2 0/4] Introduce the "with" command) Sergio Durigan Junior
2020-05-11 14:54     ` [PATCH] gdb/testsuite: fix gdb.base/with.exp failure with, native-extended-gdbserver (was: New FAIL on gdb.base/with.exp on native-extended-gdbserver) Simon Marchi

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=1561199437.1556.1.camel@skynet.be \
    --to=philippe.waroquiers@skynet.be \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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