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

Groups > gnu.bash.bug > #11231

Re: Tab completion misbehaves with newlines

Show key headers only | View raw

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.

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

Thread

Re: Tab completion misbehaves with newlines Greg Wooledge <wooledg@eeg.ccf.org> - 2015-07-17 09:47 -0400

csiph-web