Just a simple thought:
Could it be something like HISTIGNORE or 'ignorespace' in HISTCONTROL?
After I had one too many lines disappear to "ignorespace", I decided
it wasn't too worth it.
If I type history at this point, I'll see most of my command history
... with an empty line in place of the
Hi Chet,
for unrelated reasons I'm currently building identically configured bash
binaries on Linux and Solaris. Interestingly enough I can now reproduce
the problem only on the Solaris build, and even there the problem goes
away when I run bash as 'env - ./bash --rcfile /dev/null' so it looks
lik
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
Configuration Information [Automatically generated, do not change]:
Machine: i386
OS: freebsd5.3
Compiler: cc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386'
-DCONF_OSTYPE='freebsd5.3' -DCONF_MACHTYPE='i386-portbld-freebsd5.3'
-DCONF_VENDOR='portbld' -DLOCALEDIR='/usr/local/share/loc
Terry Raitt wrote:
> The =~ operator does not appear to function.
Unfortunately that is not enough information to recreate the problem.
The =~ operator appears to work for others. Can you say what you were
trying to do?
Bob
