Do you know how to exit of the command not found: uname? - oh-my-zsh

I am a beginer and I was trying to connect postgres to a database ig and this happen and can't exist nor clear
Users/kouadiondah/.oh-my-zsh/oh-my-zsh.sh:56: command not found: mkdir
/Users/kouadiondah/.oh-my-zsh/oh-my-zsh.sh:117: command not found: rm
compdump:136: command not found: mv
detect-clipboard:33: command not found: uname
I can't exit of this
Any help??

same problem here. I think it has to do with the FPATH-Variable but I do not get a solution.
My errors are:
/home/weidner.f/ohmyzsh/oh-my-zsh.sh:56: command not found: mkdir
/home/weidner.f/ohmyzsh/oh-my-zsh.sh:56: command not found: mkdir
/home/weidner.f/ohmyzsh/oh-my-zsh.sh:117: command not found: rm
parse_git_dirty:18: command not found: tail
This messages occur in the terminal when I am opening my IDE (IntelliJ)

Related

zsh: command not found: duarouter to create a rou.xml file

I'm using sumo in macOS. I'm trying to create a duarouter by calling the following command after creating a random trips for a given network:
duarouter -n ~/SUMOTutorials/sumotest.net.xml --route-files ~/SUMOTutorials/sumotest.trips.xml -o ~/SUMOTutorials/sumotest.rou.xml --ignore-errors
However I just get the error:
zsh: command not found: duarouter
I see in sumo directory there is duarouter of kind Unix executable file in sumo/bin and sumo/tests and in I run the above command when I'm in each of those directory but I just get an error.
I found the answer. Because the type is Unix executable file, we have to write the following in the directory where it is:
./duarouter -n ~/SUMOTutorials/sumotest.net.xml --route-files ~/SUMOTutorials/sumotest.trips.xml -o ~/SUMOTutorials/sumotest.rou.xml --ignore-errors.

zsh: command not found: mysql answered

Kept getting this error every time I tried to start SQL on Mac
zsh: command not found: mysql
➜ u-develop-it git:(main) ✗
For zsh: command not found: mysql
GO TO DIRECTORY OF PROJECT
Try:
export PATH="${PATH}:/usr/local/mysql/bin/"
Then enter
mysql -u root -p
you will then be prompted for SQL password
Or All toegther
/usr/local/mysql/bin/mysql -uroot -p

REDIS Error: ERR unknown command `CONFIG when trying to set dir

I'm trying to run the following
redis-cli --raw -a '<password censored>' 'CONFIG SET dir /var/www/html'
However I keep getting:
ERR unknown command `CONFIG SET dir /var/www/html`, with args beginning with:
Any advice?

zsh: command not found: "ams_cds"

I am trying to get my Cadence Environment set up for designing my circuit. This is my first encounter with .zshrc files. I am working from my school server. I was instructed to run the command zsh first and then basically run this command:
ams_cds -tech h35b4 -mode fb`
(specific to Cadence design kit). On running this, I get the following error:
zsh: command not found : ams_cds
I have been trying to resolve this "command not found" issue but have not succeded in doing so. Any help/guidance will be appreciated.
Thanks a lot in advance.

Handling DCL ON ERROR actions after first error?

The OpenVMS DCL command HELP ON EXAMPLE displays:
ON
Examples
1.$ ON SEVERE_ERROR THEN CONTINUE
A command procedure that contains this statement continues
to execute normally when a warning or error occurs during
execution. When a severe error occurs, the ON statement signals
the procedure to execute the next statement anyway. Once
the statement has been executed as a result of the severe
error condition, the default action (ON ERROR THEN EXIT) is
reinstated.
According to the help if neither [-]x.for nor [-]y.for exist then the last two lines will not be executed:
$ on error then $ continue
$ rename [-]x.for []
$ rename [-]y.for []
$ type *.for
Is there a way to set the ON ERROR handling as in the first line w/o placing an ON ERROR statement between each line of the script?
If the ON ERROR fires, you have to re-establish it. It looks like you
don't know whether any of the files exists. So the ON ERROR needs to be
re-established after the first failing command.
You can do this in a subroutine, like in:
$ on error then $ gosub on_error
$ rename [-]x.for []
$ rename [-]y.for []
$ on error then $ exit
$ type *.for
$ exit
$
$ on_error:
$ on error then $ gosub on_error
$ return
Also, you can handle this differently, with disabling error checking (SET
NOON):
$ set noon
$ rename [-]x.for []
$ rename [-]y.for []
$ set on
$ type *.for
or establishing error handling only for sever errors (ON SEVERE_ERROR):
$ on severe_error then $ exit
$ rename [-]x.for []
$ rename [-]y.for []
$ on error then $ exit
$ type *.for