From: Simon Marchi <simon.marchi@polymtl.ca>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Cc: gdb@sourceware.org
Subject: Re: / (slash) command : fast way to temporarily change setting(s) to run a command
Date: Tue, 16 Apr 2019 12:20:00 -0000 [thread overview]
Message-ID: <33981fb59a1202b4e00dc7d4b5a77089@polymtl.ca> (raw)
In-Reply-To: <1555397322.1473.10.camel@skynet.be>
On 2019-04-16 02:48, Philippe Waroquiers wrote:
> On Mon, 2019-04-15 at 23:06 -0400, Simon Marchi wrote:
>> Hi Philippe,
>>
>> I like the idea, I would probably use it most with /e (for long
>> strings) and /p.
>> I just tried it a little bit, and I appreciate the fact that it's easy
>> to apply
>> to your previous command. Just type up and add the prefix to the
>> beginning of the
>> line.
> Interesting, that was not the primary use case I was thinking to.
>
> We could make this even easier by making COMMAND optional in:
> Usage: /SETTING... [COMMAND]
> and giving no command means to repeat the previous command with the
> additional
> given settings e.g. :
> (gdb) some command
> .... some command output
> (gdb) /e
> => executes /e some command
>
> (gdb) /e some command
> ... some command output
> (gdb) /p
> => executes /ep some command
>
> I guess we probably call dont_repeat () in / command
> when no COMMAND is given.
Ah yeah, that sounds good too, I would be consistent with the fact that
just like you can do:
(gdb) p 10
$4 = 10
(gdb) p/x
$5 = 0xa
Does it mean that as a side-effect, "/" alone would repeat the previos
command unaltered?
Simon
next prev parent reply other threads:[~2019-04-16 12:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1555313564.1473.2.camel@skynet.be>
2019-04-16 3:06 ` Simon Marchi
2019-04-16 6:48 ` Philippe Waroquiers
2019-04-16 12:20 ` Simon Marchi [this message]
2019-04-16 21:22 ` Philippe Waroquiers
2019-04-17 8:14 ` Kevin Buettner
2019-04-17 20:59 ` Philippe Waroquiers
2019-04-19 16:52 ` John Baldwin
2019-05-03 3:10 ` Kevin Buettner
2019-05-03 8:23 ` Pedro Alves
2019-05-03 9:10 ` 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=33981fb59a1202b4e00dc7d4b5a77089@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb@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