Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: FYI: fix PR gdb/8869
Date: Mon, 10 Aug 2009 19:38:00 -0000	[thread overview]
Message-ID: <831vnjlcnj.fsf@gnu.org> (raw)
In-Reply-To: <m3k51b8ssi.fsf@fleche.redhat.com>

> Cc: gdb-patches@sourceware.org
> From: Tom Tromey <tromey@redhat.com>
> Date: Mon, 10 Aug 2009 11:47:41 -0600
> 
> >>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
> 
> Tom> I reasoned that only "set" commands could accept completers
> 
> Eli> I hope this doesn't mean that "show" commands will not complete
> Eli> anymore, does it?
> 
> The completer in question is used for the arguments to a command.
> "show" commands don't take arguments, AFAIK.  So, there is no problem here.

How do you mean ``don't take arguments''? Every word after `show' is
an argument to `show', and some "show" commands have more than one
word there, like "show history", "show mem", etc.

> Perhaps I am misunderstanding you, though.  What do you think would stop
> working?

Completion of the words after `show'.  I didn't say it would stop
working, I just expressed the hope that it won't.


  reply	other threads:[~2009-08-10 18:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-07 20:48 Tom Tromey
2009-08-07 22:05 ` Tom Tromey
2009-08-07 22:16 ` Pedro Alves
2009-08-07 22:29   ` Tom Tromey
2009-08-08  1:55     ` Tom Tromey
2009-08-08 16:17       ` Pedro Alves
2009-08-08 16:39         ` Pedro Alves
2009-08-08 18:08           ` Pedro Alves
2009-08-12 23:00             ` Tom Tromey
2009-08-13 17:06               ` Pedro Alves
2009-08-13 17:34                 ` Eli Zaretskii
2009-08-13 18:30                   ` Pedro Alves
2009-08-08  8:37 ` Eli Zaretskii
2009-08-10 17:59   ` Tom Tromey
2009-08-10 19:38     ` Eli Zaretskii [this message]
2009-08-10 19:59       ` Tom Tromey
2009-08-10 20:10         ` Eli Zaretskii

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=831vnjlcnj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.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