Question:
➜ ~ mvn
zsh: command not found: mvn
Answer:
step 1:
vim ~/.zshrc
step 2:(Add at the end of the file)
source ~/.bash_profile;
step 3:(Execution shell)
> source ~/.bash_profile
You can use mvn :
➜ / mvn
[INFO] Scanning for projects...
.......
Answer from sunmeilinbbs on Stack Overflowmacos - Command not found - Oh-My-Zsh - Stack Overflow
"ZSH: Killed" Error immediately after every command on M1 MacBook
zsh killed when trying to access git on m1 mac
macos - Maven commands resuting in Killed: 9 on MAC OS - Stack Overflow
Videos
Question:
➜ ~ mvn
zsh: command not found: mvn
Answer:
step 1:
vim ~/.zshrc
step 2:(Add at the end of the file)
source ~/.bash_profile;
step 3:(Execution shell)
> source ~/.bash_profile
You can use mvn :
➜ / mvn
[INFO] Scanning for projects...
.......
Just add:
source ~/.bash_profile
to .zshrc
Hi, I'm pretty new to homebrew and the whole command line thing on the Mac, so please be kind ;) Every time I try to use YouTube-DL this happens:
youtube-dl --verbose "https://www.youtube.com/watch?v=lKeUCkBO8QA" zsh: killed youtube-dl --verbose "https://www.youtube.com/watch?v=lKeUCkBO8QA"
I spend hours googling for help, but I couldn't find anything. Can someone please explain to me what's going on there and wtf is killing that process?
Btw I got Vidl installed also.
Here I put the final solution. I tried many methods on my mac M1, the best method is re-install homebrew.
Step1:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/uninstall.sh)"
Step2: Install homebrew
cd /opt
mkdir homebrew # if not exist, just create one.
curl -L https://github.com/Homebrew/brew/tarball/master | tar xz --strip 1 -C homebrew
Then, the problem solved.
I used the below commands:
brew uninstall git
brew update
brew reinstall pcre2 gettext
brew install git
Git worked after.
Open a new terminal window/tab
If you replace a signed macOS binary by using cp instead of mv then macOS caches the signature, doesn't like the look of it because the file changed and kills your process when you try and start the new binary. Clearly, this is a bug in macOS. We had to update our install scripts to copy the file a different way.