Re: TIMEOUT

On Sat, Apr 04, 2009 at 08:37:32AM -0300, Sergio Charpinel Jr. wrote: > So, first of all, I'm trying to find a way to combine TMOUT variable with > vlock. What's vlock? > I just found a way to do this in zhs. And if it is not possible, I > need to set TIMEOUT just for root, and it can't logout wh

Re: Brace expansion

> So... what gives??? I tried looking at info coreutils 'printf > invocation', and it does not even explicitly spell out what the %d > argument means, instead it just tells me "it's like the C printf, except > for these differences". I have never used C, and have no idea where to > look it up,

Re: checkwinsize doesn't work on Solaris due to missing #include for TIOCGWINSZ

Dan Price wrote: > [resubmitting, this doesn't seem to have gotten to bug-bash on my first > try a few weeks ago] > > Configuration Information [Automatically generated, do not change]: > Machine: i386 > OS: solaris2.11 > Compiler: gcc > Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386'

Re: using mapfile is extreamly slow compared to oldfashinod ways to read files

Chet Ramey wrote: I'm sure there are efficiency improvements possible in the bash indexed array implementation, but sequentially accessing a data structure optimized for space and sparse arrays is never going to be as fast as a read-process loop, and that difference becomes more and more apparent

Re: feature-request: brief syntax for $(type -p somecommand)

Mike Coleman wrote: It would be nice if there was some really brief syntax for $(type -p somecommand) p() { local what=$(type -p $1) shift 1 "$@" "$what" } p foobar ls -l p foobar strings ...etc also, 'complete -c p' -- Matthew Please do not quote my e-mail address unobfuscated in mes

Re: using mapfile is extreamly slow compared to oldfashinod ways to read files

Matthew Woehlke wrote: > Chet Ramey wrote: >> I'm sure there are efficiency improvements possible in the bash indexed >> array implementation, but sequentially accessing a data structure >> optimized for space and sparse arrays is never going to be as fast as >> a read-process loop, and that differ

set -x prejudiced; won't smell UTF-8 coffee

Gentlemen, -x's reporting should just pass the Chinese right back. $ set -x; export LC_ALL=$LANG; echo 中文 + export LC_ALL=zh_TW.UTF-8 + LC_ALL=zh_TW.UTF-8 + echo $'\344\270\255\346\226\207' 中文 Or OK, to be fair, even the ASCII should come back as octal escapes.

Re: dir*/** behavior

m...@ice.filescope.com wrote: Configuration Information [Automatically generated, do not change]: Machine: i686 OS: linux-gnu Compiler: i686-pc-linux-gnu-gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu' -DCONF_VENDOR=

Re: set -x prejudiced; won't smell UTF-8 coffee

On Monday 06 April 2009 21:24:35 jida...@jidanni.org wrote: > Gentlemen, -x's reporting should just pass the Chinese right back. > $ set -x; export LC_ALL=$LANG; echo 中文 > + export LC_ALL=zh_TW.UTF-8 > + LC_ALL=zh_TW.UTF-8 > + echo $'\344\270\255\346\226\207' > 中文 i dont think that's UTF-8. unico

Re: set -x prejudiced; won't smell UTF-8 coffee

Mike Frysinger writes: > exactly do you suggest differentiating... I don't know. It's all truly over my head. All I know is "how are you going to 'market' this stuff in Asia?". I mean the US kids get to see all their -x feedback pretty, but Asians must see it garbled. I don't know. Some kind of s