From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: drow@mvista.com
Cc: fnasser@redhat.com, gdb@sources.redhat.com, vinschen@cygnus.com
Subject: Re: [rfc] Completion tests failing
Date: Thu, 27 Sep 2001 08:36:00 -0000 [thread overview]
Message-ID: <1858-Thu27Sep2001173710+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <20010927103401.B19151@nevyn.them.org>
> Date: Thu, 27 Sep 2001 10:34:01 -0400
> From: Daniel Jacobowitz <drow@mvista.com>
>
> I wanted to get a name that I knew would complete unambiguously, so I
> tried using '"break.', which ought to complete to '"break.c"'. It
> completes instead to '"break.c ' - trailing space, no trailing quote.
Try this twice, one after the other, and you will see that only the
first time fails. The second and all the successive times will
complete to `"break.c"'.
This is a known limitation of the current completion machinery: GDB
needs to set the correct word-delimiting characters, but Readline
doesn't give us a chance to do that before it breaks the user input
into words. Thus, the first time our completion function is called,
the input is broken into words according to wrong delimiters.
We cannot fix this without some additional hooks provided by Readline.
next prev parent reply other threads:[~2001-09-27 8:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-26 18:13 Daniel Jacobowitz
2001-09-26 18:26 ` Elena Zannoni
2001-09-26 18:42 ` Daniel Jacobowitz
2001-09-27 1:39 ` Eli Zaretskii
2001-09-27 5:05 ` Fernando Nasser
2001-09-27 7:29 ` Daniel Jacobowitz
2001-09-27 7:33 ` Daniel Jacobowitz
2001-09-27 8:34 ` Fernando Nasser
2001-09-27 10:01 ` Eli Zaretskii
2001-09-27 10:22 ` Daniel Jacobowitz
2001-09-27 12:08 ` Eli Zaretskii
2001-09-27 13:48 ` Fernando Nasser
2001-09-27 15:22 ` Daniel Jacobowitz
2001-09-27 8:36 ` Eli Zaretskii [this message]
2001-09-27 10:00 ` Daniel Jacobowitz
2001-09-27 12:07 ` Eli Zaretskii
2001-09-27 12:19 ` Daniel Jacobowitz
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=1858-Thu27Sep2001173710+0300-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=drow@mvista.com \
--cc=fnasser@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=vinschen@cygnus.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