Hey guys,

Im currently going through a bash-script tutorial.

Unfortunately its from a magazine, so its difficult to show you the exact tutorial.

However a line in the code say i=0; CLEAR; CIVIS;NULL=/dev/null

and when I try to execute the file I get the notion "CLEAR: command not found".

I checked for typos or anything, but I cant find any. Also Im not sure, where to find the correct syntax for the clear-command. Web searches simply show problems with the terminal command.

The code example also is something above my actual horizon and the tutorial also says so Id still like to know, what went wrong there.

I hope I could make my problem "clear" .

Thanks in advance.

K

Linux is case sensitive. CLEAR is not the same command as clear. CAPS are typically used for variables, rarely for commands.

1 members found this post helpful.

Nice, thank you ! In the tutorial it is in all caps but I tried it without and it worked.

After debugging a few other line I came to the following

while [[ "$0" |= " " ]];do case $i in

and in the terminal it says
line 47: unexpected token `|', conditional binary operator expected␌⎺└└▒┼␍ ┼⎺├ °⎺┤┼␍
./bashselection.sh: line 47: syntax error near `|='
./bashselection.sh: line 47: ` while [[ "$0" |= " " ]];do case $i in'

Problem is: The part where I wrote "|=" is written so small in the magazine, that I cant recognize, which symbol it shows.
Is there maybe a common one that would fit here?

Post #3 shows many non-alphanumeric characters (mostly high-ASCII box-drawing and "|") here that make it impossible to understand whatever your are trying to script.

1 members found this post helpful.

The correct operator is != (not equal)

1 members found this post helpful.

The code example is for an graphical bash selection menu.
Like I said, its way above my skills and I dont really understand the code, but now that I started to copy it, I want to make it work.
In the lines I marked with >>> on the left, each red"|" is a symbol I cant recognize, because it is printed so small



REFRESH(){ after=$((i+1)); before=$((i-1))
if [[ $before -lt 0 ]];then before=$LM;fi
if [[ $after -gt $LM ]];then after=0;fi
if [[ $j -lt $i ]];then UNMARK;M$before;else UNMARK;M$after;fi
>>> if [[ $after -eq 0 ]] || [ $before -ew $LM ];then
UNMARK; M$before; M$after;fi;j=$i;UNMARK;M$before;M$after;}
INIT(){ R;HEAD;FOOT;MENU;}
SC(){ REFRESH;MARK;$S;$b;cur='ARROW' ;}
ES(){ MARK;$e "ENTER = main menu ";$b;read;INIT;};INIT
>>> while [[ "$0" |= " " ]];do case $i in
0) S=M0;SC;if [[ $cur == "" ]];then R;$e "\n$(w )\n";ES;fi;;
1) S=M1;SC;if [[ $cur == "" ]];then R;$e "\n$(ifconfig )\n";ES;fi;;
2) S=M1;SC;if [[ $cur == "" ]];then R;$e "\n$(df -h )\n";ES;fi;;
3) S=M1;SC;if [[ $cur == "" ]];then R;$e "\n$(route -n )\n";ES;fi;;
4) S=M1;SC;if [[ $cur == "" ]];then R;$e "\n$(date )\n";ES;fi;;
5) S=M1;SC;if [[ $cur == "" ]];then R;$e "\n$($e by oto )\n";ES;fi;;
6) S=M1;SC;if [[ $cur == "" ]];then R;exit 0;fi;;
esac;POS;done

thanks, I had that before the "=" at first but changed it because of the other line. Could you think of the right symbol, where I wrote "||"?
Simply putting in "!!" results in:

./bashselection.sh: line 42: syntax error near unexpected token `!!'
./bashselection.sh: line 42: ` if [[ $after -eq 0 ]] !! [ $before -ew $LM ];then'

The || (double pipe, logical OR) is correct.
But there is no -ew operator; perhaps it should be -eq (equal, comparing numbers).

1 members found this post helpful.

that makes the print even worse, but at least now I got it. I didn't even notice the "ew"-mistake. Thank you both very much
I really wouldn't have figured it out without you.

Typing in code found in magazines?

That brings back some memories.

The code not running, ambiguous, poor font choices, or just plain wrong?

That brings back some memories.

Glad they got you sorted out, but man this thread bring back some old memories.

Early 80th, Commodore, Sinclair?

Then either the tutorial is very, very bad, or it's not a bash tutorial. Maybe it's a batch scripting tutorial (or similar) which I believe is a DOS/Windows thing?

In any case, there's no point pursuing this on a bash shell.

There's plenty of good bash tutorials out there.

Among others, like Byte.