From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Chris Moller <cmoller@redhat.com>,
"gdb-patches\@sourceware.org"
<gdb-patches@sourceware.org>
Subject: Re: pr 11543 using-directive does not autocomplete
Date: Tue, 27 Apr 2010 21:10:00 -0000 [thread overview]
Message-ID: <m3ljc8fvpq.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100427203207.GA12825@host0.dyn.jankratochvil.net> (Jan Kratochvil's message of "Tue, 27 Apr 2010 22:32:08 +0200")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> The completion patch must follow the existing / non-existing "using
Jan> namespace" directives. The patch must be integrated with `struct
Jan> using_direct' lists tracked by Sami Wagiaalla's using_directive
Jan> infrastructure.
Also, I think this should probably be done via la_make_symbol_completion_list.
Tom
prev parent reply other threads:[~2010-04-27 21:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 17:58 Chris Moller
2010-04-27 20:32 ` Jan Kratochvil
2010-04-27 20:42 ` Chris Moller
2010-04-27 21:10 ` Tom Tromey [this message]
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=m3ljc8fvpq.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=cmoller@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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