Re: [patch] fix building when readline is disabled

2012-04-23 Thread Mike Frysinger
On Monday 23 April 2012 20:08:26 Chet Ramey wrote: > On 4/23/12 7:40 PM, Mike Frysinger wrote: > > On Monday 23 April 2012 18:57:05 Chet Ramey wrote: > >> On 4/23/12 12:22 AM, Mike Frysinger wrote: > >>> if you disable readline, the complete.def code fails to build. simple > >>> patch below (not s

Re: [patch] fix building when readline is disabled

2012-04-23 Thread Chet Ramey
On 4/23/12 7:40 PM, Mike Frysinger wrote: > On Monday 23 April 2012 18:57:05 Chet Ramey wrote: >> On 4/23/12 12:22 AM, Mike Frysinger wrote: >>> if you disable readline, the complete.def code fails to build. simple >>> patch below (not sure if it's correct, but at least gets the >>> conversation g

Re: [patch] fix building when readline is disabled

2012-04-23 Thread Mike Frysinger
On Monday 23 April 2012 18:57:05 Chet Ramey wrote: > On 4/23/12 12:22 AM, Mike Frysinger wrote: > > if you disable readline, the complete.def code fails to build. simple > > patch below (not sure if it's correct, but at least gets the > > conversation going). > > How did you disable readline? Ru

Re: [patch] fix building when readline is disabled

2012-04-23 Thread Chet Ramey
On 4/23/12 12:22 AM, Mike Frysinger wrote: > if you disable readline, the complete.def code fails to build. simple patch > below (not sure if it's correct, but at least gets the conversation going). How did you disable readline? Running configure --disable-readline and building as usual works f

Re: Internal 'echo' command doesn't handle I/O errors on close file

2012-04-23 Thread Greg Wooledge
On Mon, Apr 23, 2012 at 06:50:31PM +0200, Andreas Schwab wrote: > The redirection itself won't fail, unless the device is out of inodes. Ah... OK, I can see how that might be the case. Or depending on the file system implementation, it might fail if an additional block of disk space would need to

Re: Internal 'echo' command doesn't handle I/O errors on close file

2012-04-23 Thread Andreas Schwab
Greg Wooledge writes: > On Mon, Apr 23, 2012 at 02:38:47PM +0400, Andrey Zaitsev wrote: >> Strace show that errors from /bin/bash were ignored: >> >> [user@host ~]# strace echo "bla-bla-bla" > /mnt/fs/out.txt >> execve("/bin/echo", ["echo", "bla-bla-bla"], [/* 22 vars */]) = 0 > > If you want an

Re: Internal 'echo' command doesn't handle I/O errors on close file

2012-04-23 Thread Greg Wooledge
On Mon, Apr 23, 2012 at 02:38:47PM +0400, Andrey Zaitsev wrote: > Strace show that errors from /bin/bash were ignored: > > [user@host ~]# strace echo "bla-bla-bla" > /mnt/fs/out.txt > execve("/bin/echo", ["echo", "bla-bla-bla"], [/* 22 vars */]) = 0 If you want an strace of the internal echo, you

Internal 'echo' command doesn't handle I/O errors on close file

2012-04-23 Thread Andrey Zaitsev
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-unknown-linux-gnu' -DCONF_VENDOR='unknown' -DLOCALEDIR='/usr/share/locale'

Re: Passing variables by reference conflicts with local

2012-04-23 Thread Clark Wang
On Wed, May 5, 2010 at 01:57, Freddy Vulto wrote: > It appears that `unset' is capable of traversing down the call-stack and > unsetting variables repeatedly: > >a=0 b=0 c=0 d=0 e=0 >_unset() { unset -v b c c d d d e; } >t1() { >local a=1 b=1 c=1 d=1 >t2 >} >t2

Re: Directory completion problems

2012-04-23 Thread Artur Rataj
To be exact, symlink is in the directory ~/a, and it points to ~/test and there is also a directory ~/.java. So, after cd ~/a/symlink, there are two ../.java files -- one in the physical parent, and one in the logical parent. The former is a directory, the latter is a plain file. ~/a/symlink$ cd .