Re: problem with HISTCONTROL

2015-07-17 Thread Chet Ramey
On 7/11/15 12:43 PM, isabella parakiss wrote: > When the value of HISTCONTROL is ignoredups or ignoreboth, if you enter > a command and then open the editor and add lines to it without changing > the first line, only the first line will be stored in the history. > > I'm terrible at explaining, but

Re: Tab completion misbehaves with newlines

2015-07-17 Thread Chet Ramey
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 >>> clev

Re: Tab completion misbehaves with newlines

2015-07-17 Thread Greg Wooledge
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. > Read

Re: Tab completion misbehaves with newlines

2015-07-17 Thread Chet Ramey
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 doe

Re: Tab completion misbehaves with newlines

2015-07-17 Thread Chet Ramey
On 7/17/15 5:08 AM, Andreas Schwab wrote: > Chet Ramey writes: > >> enough to know that even though it follows a newline, the current word is >> not in a command position, > > Is it not? When executed the second line is treated as a command on its > own. In this case, it is. -- ``The lyf so

Re: time builtin does not work with set -e when a command fails

2015-07-17 Thread Chet Ramey
On 7/16/15 11:48 PM, Sam Watkins wrote: > Bash Version: 4.2 > Patch Level: 37 > Release Status: release > > Description: > The time builtin does not work with set -e when a command fails. > The "time" builtin should give timing for a command regardless of exit > status. Thanks for t

time builtin does not work with set -e when a command fails

2015-07-17 Thread Sam Watkins
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKA

Re: Tab completion misbehaves with newlines

2015-07-17 Thread Andreas Schwab
Chet Ramey writes: > enough to know that even though it follows a newline, the current word is > not in a command position, Is it not? When executed the second line is treated as a command on its own. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B