From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: jimb@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: add macro commands
Date: Fri, 10 May 2002 09:33:00 -0000 [thread overview]
Message-ID: <5137-Fri10May2002193224+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <npznz86lq6.fsf@zwingli.cygnus.com> (message from Jim Blandy on 10 May 2002 10:55:45 -0500)
> From: Jim Blandy <jimb@redhat.com>
> Date: 10 May 2002 10:55:45 -0500
>
> I think a better change would be to simply include macro names in the
> completion process.
Yes, if you can make make_symbol_completion_list complete on macros as
well as on other symbols, it would be great.
next prev parent reply other threads:[~2002-05-10 16:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-09 16:58 Jim Blandy
2002-05-09 17:13 ` Daniel Jacobowitz
2002-05-09 20:43 ` Jim Blandy
2002-05-09 17:54 ` Andrew Cagney
2002-05-09 20:43 ` Jim Blandy
2002-05-10 0:16 ` Eli Zaretskii
2002-05-10 8:55 ` Jim Blandy
2002-05-10 9:33 ` Eli Zaretskii [this message]
2002-05-10 16:07 ` Neil Booth
2002-05-11 0:16 ` Eli Zaretskii
2002-05-11 3:45 ` Neil Booth
2002-05-11 13:06 ` Jim Blandy
2002-05-16 14:17 ` Jim Blandy
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=5137-Fri10May2002193224+0300-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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