From: Chet Ramey <chet@caleb.ins.cwru.edu>
To: eliz@elta.co.il
Cc: drow@mvista.com, bug-readline@gnu.org, gdb@sources.redhat.com,
chet@po.cwru.edu
Subject: Re: Difficulty with the readline completion interface in GDB
Date: Wed, 28 Jan 2004 20:09:00 -0000 [thread overview]
Message-ID: <040128200429.AA22556.SM@caleb.ins.cwru.edu> (raw)
In-Reply-To: Message from eliz@elta.co.il of Mon, 19 Jan 2004 08:15:24 +0200 (id <uad4kea6b.fsf@elta.co.il>)
> > There's a lot of possible solutions. There could be a hook called before
> > rl_complete generates the matches list, which could fudge the complete
> > characters - most direct solution, not very elegant. A function could be
> > called to get the list of complete characters, which would then be sensitive
> > to rl_point - not sure what other issues this could cause. The filename
> > completion code could search backwards according to the list of filename
> > wordbreak characters; this would solve the specific problem but not the
> > more general one. Probably there are others.
>
> I think the first solution is the easiest one and will do the job.
I added the hook: char *(*rl_completion_word_break_hook)(void)
The completion code sets the word break characters from this function's
return value, defaulting to rl_completer_word_break_characters if it is
unset or returns NULL.
This will be in bash-3.0/readline-5.0.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet )
Live...Laugh...Love
Chet Ramey, ITS, CWRU chet@po.cwru.edu http://tiswww.tis.cwru.edu/~chet/
next prev parent reply other threads:[~2004-01-28 20:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 22:49 Daniel Jacobowitz
2004-01-19 6:14 ` Eli Zaretskii
2004-01-28 20:09 ` Chet Ramey [this message]
2004-01-28 20:17 ` Daniel Jacobowitz
2004-01-29 23:33 ` Elena Zannoni
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=040128200429.AA22556.SM@caleb.ins.cwru.edu \
--to=chet@caleb.ins.cwru.edu \
--cc=bug-readline@gnu.org \
--cc=chet@po.cwru.edu \
--cc=drow@mvista.com \
--cc=eliz@elta.co.il \
--cc=gdb@sources.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