[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: in completion, $COMP_WORDBREAKS should be ignored, unless there are
|
From: |
Chet Ramey |
|
Subject: |
Re: in completion, $COMP_WORDBREAKS should be ignored, unless there are no matches |
|
Date: |
Thu, 24 May 2012 15:16:40 -0400 |
|
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 |
On 5/23/12 7:11 AM, Vincent Lefevre wrote:
> It seems that $COMP_WORDBREAKS annoys users when filenames contain
> one of its characters:
> http://lists.gnu.org/archive/html/bug-bash/2005-07/msg00034.html
> http://lists.gnu.org/archive/html/bug-bash/2006-09/msg00019.html
> http://lists.gnu.org/archive/html/bug-bash/2011-02/msg00163.html
> and my bug report:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674084
>
> Unsetting $COMP_WORDBREAKS is not a solution, as completion would no
> longer work in contexts where such characters are word separators.
>
> How about the following behavior when the user types [TAB]?
>
> 1. Try to complete the whole word, ignoring $COMP_WORDBREAKS.
"The whole word" implies some default hidden value for COMP_WORDBREAKS
that the user can't touch or modify. The whole raison d'etre for having
it in the first place is to allow the user to specify these things. It's
easy enough to have COMP_WORDBREAKS only contain whitespace and shell
metacharacters. Maybe there should be a shell option to set that.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/