Path: csiph.com!aioe.org!news.glorb.com!usenet.stanford.edu!not-for-mail From: Greg Wooledge Newsgroups: gnu.bash.bug Subject: Re: Tab completion misbehaves with newlines Date: Fri, 17 Jul 2015 09:47:11 -0400 Lines: 22 Approved: bug-bash@gnu.org Message-ID: References: <20150715152557.GM4309@eeg.ccf.org> <55A905F0.7070506@case.edu> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: usenet.stanford.edu 1437140839 30008 208.118.235.17 (17 Jul 2015 13:47:19 GMT) X-Complaints-To: action@cs.stanford.edu To: bug-bash@gnu.org, bash@packages.debian.org Envelope-to: bug-bash@gnu.org Content-Disposition: inline In-Reply-To: <55A905F0.7070506@case.edu> User-Agent: Mutt/1.4.2.3i X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 139.137.100.1 X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Xref: aioe.org gnu.bash.bug:11231 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.