From: Kevin Buettner <kevinb@redhat.com>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA 1/3] / command : fast way to change setting(s), run a command, reset settings(s).
Date: Sun, 14 Apr 2019 18:20:00 -0000 [thread overview]
Message-ID: <20190414112035.64913f42@f29-4.lan> (raw)
In-Reply-To: <20190413190016.11970-2-philippe.waroquiers@skynet.be>
On Sat, 13 Apr 2019 21:00:14 +0200
Philippe Waroquiers <philippe.waroquiers@skynet.be> wrote:
> GDB has a lot of settings related to how commands behaves and/or print things.
>
> There is however currently no easy way to temporarily change a setting
> for a command.
> This patch implements a new command called /, that allows to temporarily
> change the settings in order to execute another command.
> The objective for this / command is to be fast to type, so it uses
> 1 or 2 letters codes to identify which settings(s) to temporarily set.
Hi Philippe,
I'd like to see some discussion regarding your proposed changes to
the command line interface first. (Though it is indeed useful to have
a patch to try out your proposed changes.)
I think it might be useful to post your examples along with a pointer
to this patch set to gdb@sourceware.org.
If this discussion has already occurred and I've somehow missed it,
I'd appreciate a link...
Kevin
next prev parent reply other threads:[~2019-04-14 18:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-13 19:00 [RFA 0/3] / command : fast way to change setting(s) to run a command Philippe Waroquiers
2019-04-13 19:00 ` [RFA 1/3] / command : fast way to change setting(s), run a command, reset settings(s) Philippe Waroquiers
2019-04-14 18:20 ` Kevin Buettner [this message]
2019-04-15 7:34 ` Philippe Waroquiers
2019-04-13 19:00 ` [RFA 3/3] NEWS and documentation for / (slash) command Philippe Waroquiers
2019-04-13 19:10 ` Eli Zaretskii
2019-04-13 19:22 ` Philippe Waroquiers
2019-04-13 19:00 ` [RFA 2/3] Test for slash_command Philippe Waroquiers
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=20190414112035.64913f42@f29-4.lan \
--to=kevinb@redhat.com \
--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