From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <dje@google.com>
Cc: teawater@gmail.com, drow@false.org, gdb@sourceware.org
Subject: Re: What about add a interface to output the assembly codes follow inferior execution
Date: Wed, 04 Mar 2009 19:09:00 -0000 [thread overview]
Message-ID: <uy6vlm7ga.fsf@gnu.org> (raw)
In-Reply-To: <e394668d0903040915l7496aa5fpbe734464de56b16c@mail.gmail.com>
> Date: Wed, 4 Mar 2009 09:15:30 -0800
> From: Doug Evans <dje@google.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, drow@false.org, gdb@sourceware.org
>
> Having another word for "disassembly" seems clumsy though. ["apropos
> opcodes" doesn't print anything today]
"apropos" searches the first lines of the doc strings, not only the
command names. So if we document the new commands like this:
show-opcodes -- display disassembly of next line with each prompt
"apropos disassembly" will find that as well. Does that solve your
problem with the name I suggested?
> 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.
next prev parent reply other threads:[~2009-03-04 19:09 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 [this message]
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
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=uy6vlm7ga.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dje@google.com \
--cc=drow@false.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