Re: Difficulty with the readline completion interface in GDB

[Elena Zannoni <ezannoni@redhat.com>]

Daniel Jacobowitz writes:
 > On Wed, Jan 28, 2004 at 03:04:29PM -0500, Chet Ramey wrote:
 > > > > 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.
 > 
 > Great, thank you!  Would you mind posting the patch for this feature,
 > so that I can merge it into the version of readline we are currently
 > using?

Can this be made part of the official set of readline-4.3 patches? It
would be easier to keep track of.

thanks
elena


 > 
 > -- 
 > Daniel Jacobowitz
 > MontaVista Software                         Debian GNU/Linux Developer