From: Mike Frysinger <vapier@gentoo.org>
To: Tom Tromey <tromey@redhat.com>
Cc: toolchain-devel@blackfin.uclinux.org, gdb-patches@sourceware.org
Subject: Re: [toolchain-devel] [PATCH] gdb: sim: add command line completion
Date: Fri, 15 Apr 2011 03:44:00 -0000 [thread overview]
Message-ID: <BANLkTinzvQ6+UX5fOk5=1uddTwxm9uaW=A@mail.gmail.com> (raw)
In-Reply-To: <m3d3kofvpt.fsf@fleche.redhat.com>
On Thu, Apr 14, 2011 at 16:01, Tom Tromey wrote:
> Mike Frysinger writes:
>> +char **sim_command_completer (struct cmd_list_element *ignore,
>> + char *text, char *word)
>
> I think this could be static.
> And, newline after the initial "char **".
np, updated patch should fix that and one or two other style things.
ive committed that.
> I don't really know anything about sim, but I didn't see anything
> obviously bad in there. So, ok with the above change.
well, it works for me :)
side note that i meant to ask about earlier, i noticed that i cant
complete things that have a dash in its name. seems because of
readline having this marked as a word break char (which is
understandable as it is usually used in math expressions). any way
around this ?
e.g. if i do:
(gdb) sim h<tab>
i get back:
help hw-board-file hw-device hw-file hw-info hw-list hw-trace
and so if i do:
(gdb) sim hw<tab>
it goes to "hw-", but now if i hit <tab>, i get nothing back. in the
completer, the word is set to "" and the text is "hw-" ...
-mike
next prev parent reply other threads:[~2011-04-15 3:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 23:32 Mike Frysinger
2011-04-14 20:02 ` Tom Tromey
2011-04-15 3:44 ` Mike Frysinger [this message]
2011-04-19 17:13 ` [toolchain-devel] " Tom Tromey
2011-04-15 3:20 ` [PATCH v2] " Mike Frysinger
2011-04-16 11:40 ` Richard Earnshaw
2011-04-16 18:33 ` Mike Frysinger
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='BANLkTinzvQ6+UX5fOk5=1uddTwxm9uaW=A@mail.gmail.com' \
--to=vapier@gentoo.org \
--cc=gdb-patches@sourceware.org \
--cc=toolchain-devel@blackfin.uclinux.org \
--cc=tromey@redhat.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