Re: shell-init: error retrieving current directory: getcwd: cannot access parent directories: Permission denied

2014-02-28 Thread zeazas
On Wednesday, December 4, 2013 7:03:40 AM UTC-8, allan...@gmail.com wrote: > On Thursday, July 17, 2008 11:42:57 PM UTC-4, Chet Ramey wrote: > > > LynnOS wrote: > > > > Thanks ,but after I export PWD,the problem doesn't go > > > > > > As I explained previously, this is not a bash problem. Thi

Latest fix for DEBUG causes pipes to fail when used with trap and an interactive shell

2014-02-28 Thread Moe Tunes
From: pnewm To: bug-bash@gnu.org Subject: Latest fix for DEBUG makes pipes not work when trap is used Configuration Information [Automatically generated, do not change]: Machine: i686 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='linux-gn

error message when rmail isn't installed

2014-02-28 Thread Moe Tunes
When rmail isn't installed, bashbug makes a dead.bashbug file and prints an error message saying rmail isn't installed. That error message could include this mailing list address to make error reporting easier instead of the end user having to search for somewhere to post it.

Re: Latest fix for DEBUG causes pipes to fail when used with trap and an interactive shell

2014-02-28 Thread Chet Ramey
On 2/28/14 2:48 AM, Moe Tunes wrote: > Machine Type: i686-pc-linux-gnu > > Bash Version: 4.3 > Patch Level: 0 > Release Status: release > > Description: > Pipes stop working in this version when DEBUG is used with trap in an > interactive shell > > Repeat-By: > pgas | # bash -c 'trap :

Re: error message when rmail isn't installed

2014-02-28 Thread Chet Ramey
On 2/28/14 7:36 AM, Moe Tunes wrote: > When rmail isn't installed, bashbug makes a dead.bashbug file and prints an > error message saying rmail isn't installed. That error message could > include this mailing list address to make error reporting easier instead of > the end user having to search for

Re: Latest fix for DEBUG causes pipes to fail when used with trap and an interactive shell

2014-02-28 Thread Chet Ramey
On 2/28/14 2:48 AM, Moe Tunes wrote: > Machine Type: i686-pc-linux-gnu > > Bash Version: 4.3 > Patch Level: 0 > Release Status: release > > Description: > Pipes stop working in this version when DEBUG is used with trap in an > interactive shell It turns out that this is Linux-specific only

Parent shell gets stopped when a child shell is created with job control but not interactive (bash -mc)

2014-02-28 Thread Eduardo A . Bustamante López
This works fine: dualbus@debian:~$ ~/local/bin/bash -s <<< 'for i in . .; do (~/local/bin/bash -mic ": & wait") ; done' [1] 1629 [1]+ Done: [1] 1631 [1]+ Done: - This does not: dualbus@debian:~$ ~/local/bin/bash -s <<< 'for i in . .; do (~/local/bin

`test -R' not working

2014-02-28 Thread NBaH
Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Rompilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-unknown-linux-gnu' -DCONF_VENDOR='unknown' -DLOCALEDIR='/home/nbah/shar

Re: `test -R' not working

2014-02-28 Thread Chet Ramey
On 2/28/14, 4:50 PM, NBaH wrote: > Bash Version: 4.3 > Patch Level: 0 > Release Status: release > > Description: > > $ var="foo bar" > $ declare -n nameref=var > $ echo "${!nameref} = $nameref" > var = foo bar > $ test -R nameref && echo ok || echo ko > bash: test: -R: unary operator expected >