VI mode "r" (single char replace) behaviour change

2006-05-10 Thread Bill Duncan 
Configuration Information [Automatically generated, do not change]:
Machine: i586
OS: linux
Compiler: gcc -I/usr/src/packages/BUILD/bash-3.0 
-L/usr/src/packages/BUILD/bash-3.0/../readline-5.0
Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='i586' 
-DCONF_OSTYPE='linux' -DCONF_MACHTYPE='i586-suse-linux' -DCONF_VENDOR='suse' 
-DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H  -I.  
-I. -I./include -I./lib   -O2 -march=i586 -mcpu=i686 -fmessage-length=0 -Wall 
-g -D_GNU_SOURCE -Wall -pipe -g -fbranch-probabilities
uname output: Linux marion 2.6.11.4-21.9-default #1 Fri Aug 19 11:58:59 UTC 
2005 i686 i686 i386 GNU/Linux
Machine Type: i586-suse-linux

Bash Version: 3.0
Patch Level: 16
Release Status: release

Description:
VI mode, "r"  (single character replace) now moves cursor
one character to right.  vi doesn't do this, ksh doesn't,
and bash didn't used to do this.  What happened?  Can I
turn this off?




___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash

Re: VI mode "r" (single char replace) behaviour change

2006-05-10 Thread Chet Ramey 
Bill Duncan wrote:

> Bash Version: 3.0
> Patch Level: 16
> Release Status: release
> 
> Description:
>   VI mode, "r"  (single character replace) now moves cursor
> one character to right.  vi doesn't do this, ksh doesn't,
> and bash didn't used to do this.  What happened?  Can I
> turn this off?

This was fixed in bash-3.1.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
   Live Strong.  No day but today.
Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://cnswww.cns.cwru.edu/~chet/


___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash

trap documentation does not match trap behavior

2006-05-10 Thread John Gatewood Ham 

Configuration Information [Automatically generated, do not change]:
Machine: i586
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='i586' 
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i586-pc-linux-gnu' 
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL 
-DHAVE_CONFIG_H   -I.  -I. -I./include -I./lib   -g -O2
uname output: Linux www.buraphalinux.org 2.6.16.15 #1 Wed May 10 16:48:09 ICT 
2006 i686 pentium4 i386 GNU/Linux
Machine Type: i586-pc-linux-gnu

Bash Version: 3.1
Patch Level: 17
Release Status: release

Description:
The info file says "Trapped signals are reset to their original
values in a child process when it is created." but this is not
true for me with crond and smartd for the SIGTERM signal.

Repeat-By:
crond is Dillon's cron with many patches; I get the same
problem with smartmontools' smartd daemon.  Source for
our crond package if you need to see the source code
is in:

http://www.buraphalinux.org/download/bls1.0/sourcecd/source/1/base/dcron

#!/sbin/bash
# this launches a crond that will NOT get the SIGTERM
# from killall crond and does not shutdown
trap '' TERM
/usr/sbin/crond -l8
exit 0

#!/sbin/bash
# this launches a crond that will get the SIGTERM
# from killall crond and shutdown
doit() {
  trap - TERM
  /usr/sbin/crond -l8
  trap '' TERM
}
trap '' TERM
doit
exit 0

Fix:
Remove that sentence from the documentation?  Maybe
add a description in the same place in the info file
of what 'set -o ???' needed to control whether signals
get inherited or not?


___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash