Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb@sourceware.org
Subject: Re: / (slash) command : fast way to temporarily change setting(s) to run a command
Date: Tue, 16 Apr 2019 21:22:00 -0000	[thread overview]
Message-ID: <1555449719.6208.1.camel@skynet.be> (raw)
In-Reply-To: <33981fb59a1202b4e00dc7d4b5a77089@polymtl.ca>

On Tue, 2019-04-16 at 08:20 -0400, Simon Marchi wrote:
> 
> 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?
The previous command can be run by just typing Return,
so I think we can keep slash command checking that at least one
setting was given.

I thought that implementing a command that would re-run the
previous saved_command_line would mean to just look/use 
saved_command_line.
But when a command runs, saved_command_line already contains
the line of the currently running command.
Slightly unexpected but not a big deal:
it is very easy to add previous_saved_command_line.

Philippe



  reply	other threads:[~2019-04-16 21:22 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
2019-04-16 21:22       ` Philippe Waroquiers [this message]
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=1555449719.6208.1.camel@skynet.be \
    --to=philippe.waroquiers@skynet.be \
    --cc=gdb@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    /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