Path: csiph.com!aioe.org!news.glorb.com!usenet.stanford.edu!not-for-mail From: Chet Ramey Newsgroups: gnu.bash.bug Subject: Re: Tab completion misbehaves with newlines Date: Fri, 17 Jul 2015 09:41:04 -0400 Lines: 50 Approved: bug-bash@gnu.org Message-ID: References: <20150715152557.GM4309@eeg.ccf.org> Reply-To: chet.ramey@case.edu NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Trace: usenet.stanford.edu 1437140501 29391 208.118.235.17 (17 Jul 2015 13:41:41 GMT) X-Complaints-To: action@cs.stanford.edu Cc: bug-bash@gnu.org, bash@packages.debian.org, chet.ramey@case.edu To: Greg Wooledge , Rickard Norlander Envelope-to: bug-bash@gnu.org User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 In-Reply-To: <20150715152557.GM4309@eeg.ccf.org> X-Junkmail-Status: score=10/50, host=mpv5.cwru.edu X-Junkmail-Whitelist: YES (by domain whitelist at mpv2.tis.cwru.edu) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 129.22.105.37 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:11229 On 7/15/15 11:25 AM, Greg Wooledge wrote: > OK, after a bit more testing, there is certainly something interesting > here that I don't quite understand, but which Chet probably will. > > I have two files: 'bad' and $'bad\nfile' > > I type: > > $ cat bad > > and press Tab twice. (The first does nothing visible.) This gives me > two completion choices: > > bad bad^Jfile > > If I press Ctrl-V Ctrl-J, the cursor moves to the next line. At this > point, further Tabbing (with or without characters) acts like a new > completion rather than a continuation of the previous completion, as > this bug report indicated. I answered this in another message; it's not a bug. > > But if instead I type: > > $ cat 'bad > > and then press Tab twice, I get the same completion choices: > > bad bad^Jfile > > Then if I press Ctrl-V Ctrl-J Tab, I end up with: > > $ cat 'bad > file' > > 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. -- ``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/