On Wed, 2008-07-30 at 18:53 +0200, Michael Haubenwallner wrote:
> Now I can see (stripped the unimportant):
> open("GetWMCMapW.loT", O_WRONLY|O_CREAT|O_APPEND|O_LARGEFILE) = 4
> kfcntl(4, 14, 0x0001) = 1
> close(4)= 0
> open("/tmp//sh-thd-
christophe malvasio wrote:
cbz (){ echo "why 'cbz' not a valid function name ?";}
bash: syntax error near unexpected token `('
It works for me. What does "alias cbz" say for you?
alias work
He wants to know if you probably have an alias named "cbz" defined, not
if your alias engine works.
Chet Ramey wrote:
> Toralf Förster wrote:
> >I'm wondering why in the example (see below) the right side is
> >prefixed with a '\' wheras the left side is unchanged.
> >...
> >[EMAIL PROTECTED] ~ $ echo "1 2 3 4" | while read a b c d; do [[
> > "$a" =
> >"$b" || "
Bob Proulx wrote:
Chet Ramey wrote:
Toralf Förster wrote:
I'm wondering why in the example (see below) the right side is
prefixed with a '\' wheras the left side is unchanged.
...
[EMAIL PROTECTED] ~ $ echo "1 2 3 4" | while read a b c d; do [[ "$a" =
"$b" || "$a"
Jan Schampera wrote:
= and == should make have difference in behaviour.
"should not show differences" *suh*
Sorry
J.
Jan Schampera wrote:
> Bob Proulx wrote:
>> Chet Ramey wrote:
...
>>> Because the ==/!=/= operators are defined to match the rhs as a pattern
>>> unless it's quoted. You quoted the original string, and the `set -x'
>>> output is supposed to be re-usable as input, so the trace output is
>>> quoted
Hello
I've tried to insert a single quote into a variable content.
With something like this :
bash-3.2$ foo=bar
bash-3.2$ echo "${foo/%/'}"
>
If you look at that, you understand that > is the $PS2, so it means that
bash is interpreting the single quote a special char.
So, naturally, I
