From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Doug Evans <dje@google.com>, teawater@gmail.com, gdb@sourceware.org
Subject: Re: What about add a interface to output the assembly codes follow inferior execution
Date: Wed, 04 Mar 2009 19:26:00 -0000 [thread overview]
Message-ID: <20090304192647.GA21091@caradoc.them.org> (raw)
In-Reply-To: <uy6vlm7ga.fsf@gnu.org>
On Wed, Mar 04, 2009 at 09:08:53PM +0200, Eli Zaretskii wrote:
> > Plus to a new user the intent of the option is a bit vague.
> > "disassemble-next-line" ? [that has a lot to type to become
> > unambiguous
>
> Right, I thought about something that begins with "disassemble", but
> didn't want to shoot our completion habits in the foot, since
> currently typing just "disas TAB" is all I need to get disassembly.
I agree we don't want to change that binding (I use it all the time).
But is it a problem? This would be under set, if I understand right.
(Another thing that would be useful, perhaps, is a modifier to 'x/i' to
say "a line's worth of instructions". But I think we'd have a lot of
trouble finding a non-ambiguous command for that.)
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-03-04 19:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 3:11 teawater
2009-03-03 16:42 ` Doug Evans
2009-03-03 17:04 ` Daniel Jacobowitz
2009-03-04 2:29 ` teawater
2009-03-04 4:09 ` Eli Zaretskii
2009-03-04 5:30 ` teawater
2009-03-04 17:15 ` Doug Evans
2009-03-04 19:09 ` Eli Zaretskii
2009-03-04 19:20 ` Pedro Alves
2009-03-04 22:10 ` Eli Zaretskii
2009-03-04 19:24 ` Doug Evans
2009-03-04 19:26 ` Daniel Jacobowitz [this message]
2009-03-04 19:32 ` Pedro Alves
2009-03-04 21:25 ` Doug Evans
2009-03-04 22:14 ` Eli Zaretskii
2009-03-04 22:20 ` Pedro Alves
2009-03-04 22:31 ` Doug Evans
2009-03-04 23:41 ` Tom Tromey
2009-03-05 2:42 ` teawater
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=20090304192647.GA21091@caradoc.them.org \
--to=drow@false.org \
--cc=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=teawater@gmail.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