bash inserts semicolon into history when using here-document

2010-10-04 Thread Robert Citek
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

Re: nocaseglob doesn't always work as expected.

2010-10-04 Thread Bob Proulx
Alexey Vinogradov wrote: > ale...@ubuntu64:/tmp$ shopt -u nocaseglob; shopt -s nullglob; for a in > [B-C]* ; do echo $a; done Since you do not mention your locale setting I assume that you are not aware of how it affects ranges. Here if your locale setting uses dictionary sort ordering then [B-C]

Re: nocaseglob doesn't always work as expected.

2010-10-04 Thread Greg Wooledge
On Mon, Oct 04, 2010 at 08:14:32PM +0700, Alexey Vinogradov wrote: > ale...@ubuntu64:/tmp$ shopt -u nocaseglob; shopt -s nullglob; for a in > [B-C]* ; do echo $a; done > > But the range search here is thow out only non-capital "bigstore" from the > listing, and still included both-cased files begi

nocaseglob doesn't always work as expected.

2010-10-04 Thread Alexey Vinogradov
It seems that ranged filename substitution sometimes doesn't work as expected. A couple of illustrations. Source dir: ale...@ubuntu64:/tmp$ ls -la ... -rw-r--r-- 1 root root 66 2010-09-21 08:54 ahello.txt drwxr-xr-x 2 root root6 2010-09-18 13:09 bigstore -rw---