On Fri, 17 Feb 2006, [EMAIL PROTECTED] wrote:
hi everybody
this is my first post, and i'm not sure whether it even belongs here...
is it the shell which handles the command history? if so, here my
feature request: it would be very convenient, to be able and narrow down
the search in the comman
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Greg Schafer on 2/21/2006 8:20 PM:
>
> status=`echo '-'| { ${GREP} -E -e 'a\' >/dev/null 2>&1 ; echo $?; }`
Even shorter - from the command line:
bash-3.1.9 $ echo `echo 'a\'`
a\
bash-3.1.10 $ echo `echo 'a\'`
># Oops, bash is stil
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to [EMAIL PROTECTED] on 1/23/2006 6:52 AM:
>
> Description:
> There is a behavior difference between bash 3.0 and 3.1. This results
> in trouble installing oracle database software. in 3.0 `cmd` can
> span over lines, i
On Wed, 22 Feb 2006, Greg Schafer wrote:
status=`echo '-'| { ${GREP} -E -e 'a\' >/dev/null 2>&1 ; echo $?; }`
You're having one additional "\" ... change that to ...
status=`echo '-'| { ${GREP} -E -e 'a' >/dev/null 2>&1 ; echo $?; }`
or split to the next line ...
status=`echo '-'| {
hi
i made a bug repport few days ago but i'm not sure it reached the list,
anyway my concern is quite simple, i got a pattern which doesn't match
what he should do : +([[:alpha:].]) which doesn't match strings composed
of letters and/or dots, it just match letters-only-composed string
whereas
Configuration Information [Automatically generated, do not change]:
Machine: hppa2.0w
OS: hpux11.11
Compiler: cc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='hppa2.0w'
-DCONF_OSTYPE='hpux11.11' -DCONF_MACHTYPE='hppa2.0w-hp-hpux11.11'
-DCONF_VENDOR='hp' -DLOCALEDIR='/usr/local/gnu/share/
Chet Ramey wrote:
> There is a difference in behavior between bash-3.0 and bash-3.1 involving
> parsing of single- and double-quoted strings occurring in old-style
> command substitution. The difference has to do with how backslashes are
> processed. This patch restores a measure of backwards
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash
Configuration Information [Automatically generated, do not change]:
Machine: i586
OS: linux
Compiler: gcc -I/usr/src/packages/BUILD/bash-2.05b
-L/usr/src/packages/BUILD/bash-2.05b/../readline-4.3
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i586'
-DCONF_OSTYPE='linux' -DCONF_MACHTYPE='
Running program many times I noticed that
ps -p $$ -o pid,args > waiting.$$;
lockfile -1 setting
if ! cat waiting.$$ | egrep -q '[0-9]'
then
ps -p $$ -o pid,args > check.$$
echo "What's going on!!!"
exit 1;
fi
sometimes it prints "What is going on". File
waiting.1234
hi everybody
this is my first post, and i'm not sure whether it even belongs here...
is it the shell which handles the command history? if so, here my
feature request: it would be very convenient, to be able and narrow down
the search in the command history by typing a few characters, instead o
> "Chet" == Chet Ramey <[EMAIL PROTECTED]> writes:
> If you run with convert-meta disabled, take the output and convert the
> key sequences that begin with \M- to begin with \e. (That is, make ESC
> the meta-prefix explicitly.)
> Chet
> --
> ``The lyf so short, the
> "Chet" == Chet Ramey <[EMAIL PROTECTED]> writes:
> It does, actually. Bash-3.1 key bindings interpret the "\M-" prefix the
> same way that the dispatch code does: if the convert-meta flag has been
> set, the sequence is converted into an escape-prefixed sequence and
> boun
Hi,
the bash-3.1.5 has a problem with quoting which leads to
a different output of
echo $(set -- $'a b'; echo $#)
and
echo "$(set -- $'a b'; echo $#)"
The patch below fix this problem.
Werner
*
14 matches
Mail list logo
