Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > gnu.bash.bug > #11232

Re: Tab completion misbehaves with newlines

Show key headers only | View raw

On 7/17/15 9:47 AM, Greg Wooledge wrote:
> On Fri, Jul 17, 2015 at 09:41:04AM -0400, Chet Ramey wrote:
>> On 7/15/15 11:25 AM, Greg Wooledge wrote:
>>> I type:
>>>
>>> $ cat bad
>>>
>>> and press Tab twice.
> [...]
>>> So, quoting the filename works around the bug, but readline isn't quite
>>> clever enough to do that on its own yet.
> 
>> Readline understands quoted strings using single and double quotes, and
>> will allow you to quote the newline with a backslash.  But when you
>> present readline with unquoted word separators, it will use them to
>> separate words.
> 
> "Bug" may not have been the right word, and maybe the cleverness should
> be in bash rather than readline, but the point is that given the first
> few characters of a filename, and multiple matches, one of which contains
> a newline character, it would have been nice if something had quoted the
> filename for me.  It's not an urgently needed feature, though.

Readline does quote the filename for you when it adds the filename to the
line buffer.  An unquoted newline is still going to act as a completion
word break character, though.

-- 
``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/

Back to gnu.bash.bug | Previous | Next | Find similar

Thread

Re: Tab completion misbehaves with newlines Chet Ramey <chet.ramey@case.edu> - 2015-07-17 10:01 -0400

csiph-web