On 04.09.2012 13:13, Roman Rakus wrote:
Hi,
Petr, adding to cc: list, found behaviour not documented, neither in man
page nor bash ref manual:
${par-word} will do expansion of par, and if the par is unset it is
substituted by word. It is different from ${par:-word}, where word is
used when par
On 02.07.2012 15:57, Eric Blake wrote:
Look for FUNCNEST variable. In recent release it is available.
I more meant the shell interpreter, less the code I can write.
It would be possible to link bash with libsigsegv to install a graceful
stack overflow handler that allows a nicer exit
On 02.07.2012 20:57, Chet Ramey wrote:
On 7/2/12 2:36 PM, Jan Schampera wrote:
The origin of this all was a bugreport to me about the manual lying about
no limits on recursion
That's funny.
Aye. A bit of confusion.
--
Be conservative in what you do, be liberal in what you accept from
Hi folks,
a suggestion about recursive function calls (and not only that, of course).
Do you see a way for Bash to pull the emergency break before it runs out
of stack here (to provide an error to the user, rather than a crash):
f1() {
f1
}
f1
On 01.07.2012 14:37, Roman Rakus wrote:
Look for FUNCNEST variable. In recent release it is available.
I more meant the shell interpreter, less the code I can write.
--
Be conservative in what you do, be liberal in what you accept from others.
- jbp, master of the net, in RFC793
Hi,
I agree this is not a bug. %c works as described.
However, Mr. Wang may want to read one of Greg's brilliant FAQ entries [1].
In general it's a bit of a pity that printf can do character-number
conversion, but not (directly) back. But it is like it is and the
workarounds are not really
Yunfeng Wang wrote:
Perhaps bash should clarify this issue in its documents such that users like me
would not be misguided again.
Since the reference to printf(3) is misleading sometimes, I made some
document [1] for Bash's printf only. It's far from perfect, but at least
it mentions %s
John Williams wrote:
I find that I cannot execute world-executable scripts when they are in
a directory which is mounted on a drive on an HBA (host bus adapter
Can you show the mount options of the filesystem?
--
Be conservative in what you do, be liberal in what you accept from others.
-
Andreas Schwab wrote:
Steven W. Orr ste...@syslang.net writes:
As a work around, I can use eval or the builtin test, but my question is
this: Is this a bug or is there a reason that it should work for
arithmetic but not for the test [[ operator?
[[ is a reserved word like if, which triggers
Hi,
just as side note, not meant to touch the maintainer discussion.
This is not only a Bash problem. The programmer/user mistake to use
[A-Z] for only capital letters, capital A to capital Z is a very
common one.
But I'm not sure if every official application-level documentation
should
Bradley M. Kuhn wrote:
I humbly suggest that http://git.savannah.gnu.org/cgit/bash.git be
replaced with this repository above that I've created. The new
repository contains everything that the current Savannah one does, but I
put much more effort into making commits fine-grained, rather than
Roman Rakus wrote:
It is noted in Here Documents (and Here Strings is a variant of here
documents). And there is:
No parameter expansion, command substitution, arithmetic expansion, or
pathname expansion is performed on word.
This is not true for here strings (infact, it wouldn't make sense
Hello world,
I recently answered a question about using the asterisk mixed with
redirection and other words. This also lead me to the documentation that
states (REDIRECTION section):
---
The word following the redirection operator in the following
descriptions, unless otherwise noted,
Dennis Williamson wrote:
I think this distinction from the man page is what's missing in the help:
[...]
Exactly. Thanks for pointing it out, I thought it was clear :)
--
Be conservative in what you do, be liberal in what you accept from others.
- jbp, master of the net, in RFC793
Marc Herbert wrote:
seq is not exactly Linux-only but GNU-only.
GNU-specific versus bash-specific, which is worse? I'd say it
depends... on which mailing-list you post :-)
I'd say a script interpreted by the GNU shell must not rely blindly on
GNU tools being installed or on running on a GNU
Hello,
the help output for the set builtin command misses '--'.
The manpage is ok.
(recognized by 'yitz' on irc://irc.freenode.net/#bash)
--
Be conservative in what you do, be liberal in what you accept from others.
- jbp, master of the net, in RFC793
Chet Ramey wrote:
I can't imagine this is just some debugging code still active (it's a beta).
Imagine. Anything that doesn't have a version tag of `release' has DEBUG
enabled for the preprocessor, which enables MALLOC_DEBUG. If you're using
the bash malloc, MALLOC_DEBUG turns on extensive
Hello list,
the read builtin command, when trying to assign to a readonly variable
after reading the data, spits an error message. This is fine.
But the return status is 0. It always (down to 2.04 was tested) has
been like that, and it's like that in upcoming 4.2.
For me, this doesn't
jens.schmid...@arcor.de wrote:
For an empty $@ this does not throw an unbound error, which seems to be
an inconsistent behaviour to me.
-u Treat unset variables as an error when substituting.
I think the behaviour is consistent with the documentation.
--
Be conservative in what you do,
jida...@jidanni.org wrote:
$ cat 201012contract
#!/bin/sh -eux
set a b c d e f
: ''$@''
: ' '$@' '
: ''$*''
: '' $* ''
: $*
$ ./201012contract
+ set a b c d e f
+ : a b c d e f
+ : ' a' b c d e 'f '
+ : 'a' b c d e 'f'
+ : '' a b c d e f ''
+ : ' a' b c d
Joerg Boehmer wrote:
The value of variable ar[1] is expanded to 0 although it was not set.
The full syntax produces the expected behavior:
The value of y is 0, since you operate in arithmetic context. This is
fine. But I definitely agree it should bail out here.
--
Be conservative in what
Roger wrote:
If you want the PID of the current shell process, use $$ instead.
Yes I do. It's only me on this computer, unless you're speculating on
prioritizing a snooper. :-O
This is (in this context) not related to the number pf bash processes
running. Not at all.
--
Be conservative
Krzysztof Zelechowski wrote:
Description:
The text of pwd and the value of $PWD return a cached value, regardless
of the actual current path.
Repeat-By:
mkdir '-p' 'a' cd 'a' mv '../a' '../b' enable '-n' 'pwd' builtin
'pwd' pwd
Fix:
cd '-P' '.'
I think it's
I'm sorry to not answer a message directly, but I didn't get the mails
of this list during the last day - no idea why. Quoting text from the
pipermail archive.
After initialÄy introducing =~, Chet made it consistent with =/==
in a second version, means: =/== doesn't do pattern matching for
Mike Frysinger wrote:
the difference here being the value in variable a after function f
finishes executing. i was expecting the behavior of `bash`, not of `sh`. i
cant seem to find anything covering this in the man page except for perhaps
interpreting the meaning of some sections to mean
Hello,
don't ask about the detail how I originally invented this code, but I
stepped over something I really can't explain:
1) Why doesn't this print anything
while read -d'' -n1 ch; do
echo $ch
done $'hello\nworld'
2) Why does this print something, but only up to the hyphen?
while
Jan Schampera wrote:
1) Why doesn't this print anything
while read -d'' -n1 ch; do
echo $ch
done $'hello\nworld'
2) Why does this print something, but only up to the hyphen?
while read -d'' -n1 ch; do
echo $ch
done $'hello\nwor-ld'
Please ignore this question. 2 minutes after
Linda Walsh wrote:
On 8/2/2010 1:13 PM, Chet Ramey wrote:
There are several versions of `autoload' in examples/functions.
Chet
===
I've been using 'man bash' as my reference. I don't see a reference
to examples or autoload, and finding 'functions' doesn't show me any examples.
Is
Linda Walsh wrote:
The curly brackets are suposed to be optional.
They are line 2 of the Compound commands list below...
Don't ask me why, but it works when you don't use the function
keyword, but () instead:
foo() [[ 1 ]]
Might be a parsing bug, though you shouldn't use function at all.
Hello,
Tested versions:
- 4.1.2(1)-release
- 3.2.39(1)-release
Reproduce by:
string=1/2 3=
echo ${string//[= /]}
Expected result:
123
Actual result:
1/2 3=
Workaround: Escape the inner slash with a backslash.
Within a bracket expression, the slash should lose its special meaning.
Linda Walsh wrote:
I suppose I'm presuming these features are not already implemented in
some fashion -- did I overlook them, or would they be 'new'?
I know it's not applicable for all cases, but I usually use read to
split strings into variables/an array.
J.
Clark J. Wang wrote:
Running a cmd in background (by ) would not create subshell. Simple
testing:
#!/bin/bash
function foo()
{
echo $$
}
echo $$
foo
### END OF SCRIPT ###
The 2 $$s output the same.
This doesn't mean that it doesn't create a subshell. It creates one,
since it can't
Britton Kerin wrote:
How so? It seems that read always reads from the terminal even when its in a
shell pipeline.
This isn't correct. Read reads from STDIN by default.
Regards,
Jan
Dr. Werner Fink wrote:
The question rises: Why does the bash require a sub peocess/shell
for the final command of a pipe sequence.
I'd think this is more or less a design choice at first (with one or the
other issue, maybe for both solutions - though I can't construct a
failing case for the
RESEND FOR THE MAILINGLIST
Britton Kerin schrieb:
Which in a pipeline is supposed to be the output of the previous command, right?
Its not at all obvious to me why it behaves as it does.
The other subthread of this thread is about it: In Bash, all parts of a
pipeline are executed in an own
Marc Herbert schrieb:
From section 2.12 and from messages posted here in the past I
understand that POSIX allows either one. This ambiguity reinforces the
need for documentation IMHO.
I agree with Greg here, it's a well known don't. What should be
documented is (maybe it is?) how pipelines
Chet Ramey wrote:
How about a stack traceback?
I'm so sorry, I thought this was clear and easy to reproduce/verify.
I'm using this to generate the script. The number of commands varies
between shell versions (and likely other platform stuff), so you might
need to play around with the
Oh, and to be complete:
uname -rms yields:
* Linux 2.6.26-2-amd64 x86_64
The C library is a:
* GNU libc 2.16.6-3
The crashed Bash is a:
* ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically
linked (uses shared libs), for GNU/Linux 2.6.8, not stripped
Jan TheBonsai
Hello list,
somebody in chat just asked about the maximum input line length, I know
(and told him) that this might be very platform dependent, but I did
some tests.
The result of these tests was a SEGV (after some 78K line length).
Shouldn't this be sanely catched somehow by the parser? I
Bernd Eggink wrote:
Select lists are sometimes displayed with incorrect vertical alignment
if an item contains one or more German umlauts. Examples:
select x in äöü blah{1..20}; do :; done# wrong
select x in amöbe blah{1..20}; do :; done# wrong
select x in amöb
Hello Chet,
hello list,
during some discussion in the IRC #bash channel on freenode we found a
weird behaviour of the 'hash' builtin command.
The command exits true if the operand in question contains a /, no
matter if that makes sense or not:
---
$ hash
Clark J. Wang schrieb:
I saw a printf usage from a Linux forum's post:
# printf %d\n 'a
97
#
It's really cool but I found no info in bash's manual. Are there any other
undocumented interesting features? :)
I documented it, though I don't remember where I first heard about it.
Maybe I
Clark J. Wang schrieb:
In C code I can use lockf(), flock(), semaphore and mutex for locking /
unlocking. Can bash provide some similar mechanisms?
For simple things, which don't need to be 1000% rocksolid, you can use
atomic operations like mkdir or noclobbered redirection for mutex
Clark J. Wang schrieb:
And if the script crashes the dir will be left unlocked.
System crashes and kill -9 are the problem. The rest is none.
If the area isn't too complex, noclobbered redirection serves well. But
if you have other options, they should be used, of course.
(doing this on a
Vadym Chepkov schrieb:
I would expect never see Continue printed
The 'exit' command exits the subshell you just created.
http://bash-hackers.org/wiki/doku.php/scripting/processtree
There's also a FAQ about it, E4.
Jan
Hello list,
hello Chet.
Bug reported on freenode's IRC #bash by: Satgi
There is a crash somewhere in completion (the last commandline is
completed using TAB):
echo $BASH_VERSION
4.1.2(1)-release
mkdir -p the/?/directory
./the/\?/Segmentation fault (core dumped)
These completions DO NOT
Mike Frysinger schrieb:
When using the bash shell in an xterm or rxvt terminals at least,
commands executed which start with a space, eg ls are not added to
the command line history and so are not accessible by ctrl-p.
this is by design
-mike
This is controlled by the HISTCONTROL and
Evan Driscoll schrieb:
Then, many programs don't handle them per se, but *not* handling them
doesn't cause much problem. grep, cat, and echo probably fall in this
category.
Bash doesn't handle it. It's a character like 'A' or 'B'. It causes
problems :)
J.
Andreas Schwab schrieb:
It's a character like 'A' or 'B'.
'A' and 'B' are letters, $'\r' is whitespace.
Yes... :)
drisc...@cs.wisc.edu schrieb:
Some of the time, using CRLF line endings cause syntax errors
in Bash scripts (unexpected end of file).
This problem shows up on Bash 4.1 on Linux, Bash 3.2 on Linux,
and Bash 3.2 on Cygwin (where I first noticed it).
Normal. Though I
Jon_R schrieb:
http://old.nabble.com/file/p27316649/newsh2.sh newsh2.sh
You have a misunderstanding about select here, I guess.
Select is supposed to display a list of given words and take user input
(index to these words). It more or less is the same as a for loop, it
just doesn't iterate
Leonid Evdokimov schrieb:
This problem may be fixed if bash does not optimise number of getcwd() calls,
but I'm not sure if the bug is really a _bug_, but not a sort of strange
feature.
Depends what 'bar' is above, assuming it's a (sym-)link or a bind here:
IMHO this is not a bug. There
Leonid Evdokimov schrieb:
This problem may be fixed if bash does not optimise number of getcwd() calls,
but I'm not sure if the bug is really a _bug_, but not a sort of strange
feature.
Sorry, I didn't read carefully enough :)
J.
Ken Irving schrieb:
This patch is not sufficient, as it leaves the error message, but it
does call the hook function in the problem cases:
I'm just not sure if it makes sense. I mean, if the user requests the
execution of a *specific file*, what should the hook function do if it
fails?
Ken Irving schrieb:
That's up to that function to determine, since bash passes control over
to it. It should be able to handle whatever it gets. My use case is
to take things that look like 'object.method' -- which are not likely
to collide with normal executables -- and run them under a
Ken Irving schrieb:
Description:
I'm not sure this is a bug, but I notice that the
command_not_found_handle function is not called if the command has a
slash in it. I can't find anywhere in the bash source producing the
No such file ... error message, so I guess this is
Mun schrieb:
nounset on
Something sets -u in your startup scripts (or in the script or whatever)
jida...@jidanni.org schrieb:
OK, never mind. Market demand too low to add...
I rather think you could just define a stop()
Lhunath (Maarten B.) schrieb:
My bad. I was under the impression `read` was a Bourne shell-only
thing and not standardized under POSIX.
(not personal for you only, I see that very often)
It would be nice if people actually read POSIX before they talk about it.
Jan
Antonio Macchi schrieb:
$ hd (echo -en \\0{0..3}{0..7}{0..7})
it breaks the console.
It doesn't break the console, it crashes the shell (here with a
subshell to get the text):
bon...@core:~$ bash
bon...@core:~$ hd (echo -en \\0{0..3}{0..7}{0..7})
malloc: ../bash/subst.c:4198:
Just for completeness: Same with 3.2.39, 4.1 alpha and beta.
Jan
Chet Ramey schrieb:
That's how I prefer it. I don't do public development on savannah, and
I do controlled test releases.
The official patches should be there as individual commits. Though, I
admit it's not a small amount of work to do all that for the past
releases. Such a GIT or SVN
Antonio Macchi schrieb:
what's the rasonable limit in using this compact contruct, after which
the for (( i=0; i1000...; i++ )) became better?
Hardware/OS limits.
J.
Ciprian Dorin, Craciun schrieb:
Thus if I say: `set -e ; { false ; true ; }` it works, but when I
put the `||`, it doesn't...
I think it's because { ...; } isn't a simple command (however, its
components are).
J.
Good morning,
http://www.gnu.org/software/bash/manual/bashref.html#Brace-Expansion
The brace expansion increment syntax is shown wrong.
OLD:
A sequence expression takes the form {x..y[incr]}, where x and y are
either integers or single characters, and incr, an optional increment,
is an
Jo King schrieb:
Fix:
[ bash/the read code could
detect there's no stdin and sleep for 1-2 seconds]
If you consider this as a bug, the bug is not in Bash (but in the
application).
In short you request that read should wait a second, once it got a
end-of-file signalled, I don't think
Marc Herbert schrieb:
Repeat-By:
$ unset PWD
Fix = readonly PWD ?
This is not a fix, this is a workaround.
Anyways, I can't reproduce it.
J.
Hey Chet,
I can reproduce it. What can I do to help tracking it down?
bon...@core:~/devel/bash-4.0$ ./bash -c 'echo $(echo \|)'
./bash: command substitution: line 1: syntax error near unexpected token `)'
./bash: command substitution: line 1: `echo \|)'
bon...@core:~/devel/bash-4.0$ ./bash -c
Jan Schampera schrieb:
It was a fresh install. Unpacking source + applying pathces, then
build *scratches beard*.
And it was done without bison - my bad. Works now.
Jan
Mitch Frazier wrote:
The close appears to be a special case of (from the man page):
Similarly, the redirection operator
[n]digit-
moves the file descriptor digit to file descriptor n,
or the standard output (file descriptor 1) if n is not
specified.
Not sure if that's a bug or
Christian Krause wrote:
Given all of these facts I still tend to say that the bash shouldn't
filter them...
There's always the following argument:
Other characters may be permitted by an implementation; applications
shall tolerate the presence of such names.
I agree with Christian here. As
Hello Chet,
hello Raph,
I was involved in the discussion on IRC (Freenode / #bash) yesterday,
maybe I can give one or the other comment.
It took a while for us to find out why it happens. When we knew it, and
after some discussion, we agreed that the easiest way would be to make
Bash able to
Ray Parrish wrote:
bash: printf: 08: invalid number
0
bash: printf: 09: invalid number
Arithmetic expression/base specifications:
http://bash-hackers.org/wiki/doku.php/syntax/arith_expr#different_bases
Seems to apply for all numerical formats for printf, too.
J.
Mike Coleman wrote:
[Oops--I sent that incomplete.]
It would be nice if there was some really brief syntax for
$(type -p somecommand)
I find myself using this all day long with 'ls', 'file', 'ldd',
'strings', 'nm', etc., and the current incantation is just long enough
to be
Lennart Schultz wrote:
In the construct
cat file|while read line
do
done
the content of any arry assignments in the loop dissapears leaving the loop:
This is logic, since every part of the pipe runs in an own subshell (the
first one runs in the current shell). This behaviour is also *not*
Dr. Werner Fink wrote:
This is not a bug, this is a consequence of Bash's design.
Yep ... nevertheless a side mark: ksh can do ;)
Which is: A consequence of Korn's design ;-)
*waves the 80km to Nuremberg*
Jan
Cam Cope wrote:
Combine tab completion with history: when you put ! at the beginning of a
command and use tab completion, it displays history results
IMHO yet a new history expansion/editing/searching mechanism (there
already are a few) would bloat it even more.
But that's just my opinion.
J.
OnTheEdge wrote:
I'm trying to check for a directory and create it if it doesn't exist as
follows:
CommonDir=../common
if [ -d ${CommonDir} ]; then
mkdir ${CommonDir}
fi
It works from the command line, but my script doesn't seem to like it and I
can't figure it out.
Thanks for
lehe wrote:
Hi,
I am trying to debug my shell script by bashdb. My script take as argument
--gdb, so I wrote
bashdb myscript.sh --gdb
However, this way it will produce error that bashdb:
unrecognized option '--gdb'
If I quote --gdb as
bashdb myscript.sh '--gdb'
then I will
Mike Frysinger wrote:
$ true
$ echo 'enter
ctrl+d
$ echo $?
258
$ true
$ echo 'enter
ctrl+d
$ echo 'enter
ctrl+c
$ echo $?
386
that doesnt seem right to me :)
the first test seems fine, and older versions of bash would set 258 for the
second test (not sure if it's correct
Mike Frysinger wrote:
$ true
$ echo 'enter
ctrl+d
$ echo $?
258
$ true
$ echo 'enter
ctrl+d
$ echo 'enter
ctrl+c
$ echo $?
386
Just tested it, hopefully it's as easy as changing every
itos (last_command_exit_value)
to
itos (last_command_exit_value 0xFF)
in subst.c (seems 2
Tim Hatch wrote:
Pilot:~/tmp/bash-4.0 tim$ coproc NAME ls
[1] 18474
Pilot:~/tmp/bash-4.0 tim$ ./bash: line 32: NAME: command not found
[1]+ Exit 127coproc COPROC NAME ls
For some reason it expects a compound command on named coprocesses,
Antonio Macchi wrote:
commands like ls --color does not use terminfo capabilities...
...use instead fixed strings (without regards about TERMinal)
is this a good (and safe) choice too?
IMHO not. Too many assumptions. GNU ls seems to always assume an ANSI
terminal, regardless which TERM is
tal396 wrote:
there is any way to echo aaa or any msg in colors?
Start at
http://bash-hackers.org/wiki/doku.php/scripting/terminalcodes
and continue at whatever Google spits out for:
- bash colors
- terminal colors
- ANSI colors
- VT100 colors
J.
Mike Frysinger wrote:
Without looking there: It can't be documented, because there's no
general way to retrieve the creation time of a file.
the op wasnt asking for the time, they were asking for the last created file.
and the ls man page talks how to sort by ctime.
Yes, that's the
coubeatczech wrote:
c...@notas:~$ if [ -z $variable ]; then echo true; fi
true
c...@notas:~$
Can anybody explain to me this behaviour? I would expect not any output in
the last command...? The variable is set to zero and there is the condition
is still true...?
Hi.
In comp.unix.shell [1] somebody wondered about
IFS=: read a b a:b; echo '$a' '$b'
ending up in
'a b' ''
Korn and Z seem to behave different. I see that across all my available
Bash versions. I remember the colon to be special in some way (was it
hostnames in a file path?), but I don't
Jan Schampera wrote:
Hello list!
Just a few thoughts, awaiting comments.
Heh. I wanted to raise a discussion about that issue, but it seems I
failed (or I'm the only one who cares) ;)
Jan
Linda Walsh wrote:
Am running an older bash version and this may be fixed (assuming it
is a bug and I'm not confused...:-))
bash version = 3.2.39(20)
This works:
1)if [ -n -a 2 -gt 1 ] ; then echo one;fi
This does not:
2)if [[ -n -a 2 -gt 1 ]] ; then echo one;fi
Hello list!
Just a few thoughts, awaiting comments.
Currently, Bash 4 calls a fixed named function
command_not_found_handle() when a command is not found. The basic
approach (to have such a possibility) is great, but:
I can imagine that there may be more internal events to react on in
future.
Chet Ramey wrote:
The case modification operators (for parameter expansion) seem to be
puzzled.
Two things I don't understand:
- it seems to work word-wise (might be due to my misinterpretion of the
default pattern)
It does work word-by-word, like the emacs-mode editing commands. I
grendelos wrote:
So this is really bugging me. Why is [a-z] not case sensitive, but [A-Z] is?
For example:
# ls -l
total 0
-rw-r--r-- 1 root root 0 Nov 20 12:22 xa
-rw-r--r-- 1 root root 0 Nov 20 12:22 xA
# ls -l x[a-z]
-rw-r--r-- 1 root root 0 Nov 20 12:22 xa
-rw-r--r-- 1 root root
Hello,
is there something like a development snapshot for Bash 4 or is the code
hidden during development phase and I need to wait for the first release?
Thanks in advance,
Jan
--
This is my life - this is my net!
- Jan
Mike Coleman wrote:
Here's a bash feature I'd love to see, but don't have time to
implement myself: a --free-slot flag to 'wait' that will wait until
there is at least one free slot available, where a slot is basically
a CPU core.
Example usage:
$ for ((n=0; n100; n++)); do
my_experiment
Juergen Gohlke wrote:
Description:
If a command in $(...) contains a case-esac construction, the
bash prints a syntax error instead
of executing the code:
bash: syntax error near unexpected token `;;'
In case you have trouble with code you need, use this workaround:
lexton wrote:
From what I read it is not good to use ls -la in the manner I use below.
Could I run this by just using the find command with additional arguments?
I still need to be able to print everything that the ls -la command gives me
GNU find has an -ls option IIRC, which produces
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.
J.
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 = $c ||
Jan Schampera wrote:
= and == should make have difference in behaviour.
should not show differences *suh*
Sorry
J.
Richard Neill wrote:
$ echo ${stringZ:2: -1} #Wish: start at 2, read till
ERROR #1 before the end. i.e.
# cde
$ echo ${stringZ: -3: -1} #Wish: start 3 back, read till
ERROR #1 before the end.
1 - 100 of 128 matches
Mail list logo
