From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/tui: Add command completion to winheight command.
Date: Sun, 12 Jul 2015 21:34:00 -0000 [thread overview]
Message-ID: <20150712213449.GA3915@embecosm.com> (raw)
In-Reply-To: <55A280B3.9050503@redhat.com>
* Pedro Alves <palves@redhat.com> [2015-07-12 15:58:59 +0100]:
> On 07/12/2015 09:51 AM, Andrew Burgess wrote:
>
> > gdb/ChangeLog:
> >
> > * tui/tui-win.c (window_name_completer): New function.
> > (focus_completer): Call window_name_completer. All old content
> > moved into window_name_completer.
> > (winheight_completer): New function.
> > (_initialize_tui_win): Rename variable. Add completer to
> > winheight command. Update doc string on winheight.
> >
>
> This is OK.
>
> > -/* Complete possible window names to focus on. TEXT is the complete text
> > - entered so far, WORD is the word currently being completed. */
> > +/* Generic window name completion function. Complete window name pointed
> > + to by TEXT and WORD. If INCLUDE_NEXT_PREV_P is true then the special
> > + window names 'next' and 'prev' are also included in the list of possible
> > + completions (if appropriate). */
> >
>
> I don't really understand what "if appropriate" is referring to, though.
I originally wrote "... are also included in the list of possible
completions." however, this is not true, if a window name has been
partially typed then clearly 'prev' or 'next' might not be included in
the list of possible completions (if say the partial window name
started with a 'c').
How about this wording:
"If INCLUDE_NEXT_PREV_P is true then the special window names 'next'
and 'prev' will also be considered as possible completions of the
window name."
Or feel free to suggest something simpler.
Thanks,
Andrew
next prev parent reply other threads:[~2015-07-12 21:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 13:13 Andrew Burgess
2015-07-10 16:24 ` Pedro Alves
2015-07-12 8:51 ` Andrew Burgess
2015-07-12 14:59 ` Pedro Alves
2015-07-12 21:34 ` Andrew Burgess [this message]
2015-07-13 9:42 ` Pedro Alves
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=20150712213449.GA3915@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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