Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Patrick Palka <patrick@parcs.ath.cx>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Add tab completion for TUI's "focus" command
Date: Tue, 23 Jun 2015 14:54:00 -0000	[thread overview]
Message-ID: <CADPb22Q2ky2qdoMyrrnf7ndSVNoj8ZPUdof=3-HWUNbrRJ5uWw@mail.gmail.com> (raw)
In-Reply-To: <CA+C-WL_qFbrxEHrCH3huQPqSyE6wPOkGam8cfK1Lu0tVjxCpLw@mail.gmail.com>

On Tue, Jun 23, 2015 at 9:37 AM, Patrick Palka <patrick@parcs.ath.cx> wrote:
> On Tue, Jun 23, 2015 at 10:01 AM, Doug Evans <dje@google.com> wrote:
>> On Sun, Jun 21, 2015 at 10:30 PM, Patrick Palka <patrick@parcs.ath.cx> wrote:
>>> The implementation is pretty straightforward, though there's the
>>> question of what the completion list should show when the TUI has not
>>> yet been initalized.
>>
>> Hi.
>> What does "not yet been initialized" mean here?
>
> I mean that the user never switched to the TUI during the session, so
> the windows and stuff have not yet been created.

Thanks.
I tried "focus cmd" and "focus src" at the start of a gdb session and
they worked.
I also tried "focus asm" and got a complaint of an invalid window.
So I'd say sure, add cmd and src to the completion list
even if TUI isn't initialized, since the command will work
as expected. I'd add a comment to the code describing
why they're being unconditionally added.

Adding next and prev when TUI hasn't been initialized
are kinda the odd ones out, conceptually, but they
too "work" (so I'm not suggesting removing them).


  reply	other threads:[~2015-06-23 14:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-22  3:30 Patrick Palka
2015-06-23 14:01 ` Doug Evans
2015-06-23 14:37   ` Patrick Palka
2015-06-23 14:54     ` Doug Evans [this message]
2015-06-23 16:52       ` Pedro Alves
2015-06-23 15:30 ` Patrick Palka
2015-06-24 14:35   ` Doug Evans

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='CADPb22Q2ky2qdoMyrrnf7ndSVNoj8ZPUdof=3-HWUNbrRJ5uWw@mail.gmail.com' \
    --to=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=patrick@parcs.ath.cx \
    /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