Error for large input files >2GB

Configuration Information [Automatically generated, do not change]: Machine: i486 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash

set -e, bad substitutions, and trap EXIT

Hi, Is this a bug? In the script below, I'm using a variable to control whether the script uses set -e or not, because the behavior is dependent on whether set -e is set. When the script hits the bad substitution, it runs the exit handler and then exits as expected. However, with set -e, the

Fix for #107950, Debian BTS #516152, #343673 and Ubuntu LP: #589496

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' -D$ uname output: Linux desktop 2.6.35-32-generic #64-Ubunt

Enhancement Request: Provide something like Emacs comint-get-next-from-history in Bash

Hi. To re-do previous command sequences from the history Bash provides operate-and-get-next (bound to C-o). So to re-do a sequence A B C of commands I need to navigate to A in the history and then enter A C-o (=> B) C-o (=> C) RET However, that requires the decision to re-do a sequence (and