zsh | Mirror of the Z shell source code repository | Command Line Interface library
kandi X-RAY | zsh Summary
kandi X-RAY | zsh Summary
Mirror of the Z shell source code repository.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of zsh
zsh Key Features
zsh Examples and Code Snippets
Community Discussions
Trending Discussions on zsh
QUESTION
Since I got Monterey 12.3 update (not sure it's related though), I have been getting this error when I try to run my python code in the terminal:
I am using python 3.10.3, Atom IDE, and run the code in terminal via atom-python-run package (which used to work perfectly fine). The settings for the package go like this:
The which
command in terminal returns the following (which is odd because earlier it would return something to just which python
):
I gather the error occurs because the terminal calls for python
instead of python3
, but I am super new to any coding and have no idea why it started now and how to fix it. Nothing of these has worked for me:
- I deleted and then reinstalled python from python.org.
- I tried
alias python='python3'
(which I saw in one of the threads here). - I tried
export PATH="/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin"
(which I found here). - To reset zsh and paths, I deleted all associated hidden files in
/local/users/
and ran the terminal once again. - I deleted evetyrhing and reinstalled macos and python only to get the same error.
ANSWER
Answered 2022-Mar-25 at 17:46OK, after a couple of days trying, this is what has worked for me:
- I reinstalled Monterey (not sure it was essential, but I just figured I had messed with terminal and
$PATH
too much). - I installed
python
viabrew
rather than from the official website. It would still returncommand not found
error. - I ran
echo "alias python=/usr/bin/python3" >> ~/.zshrc
in terminal to aliaspython
withpython3
.
Problem solved.
As far as I get it, there is no more pre-installed python 2.x in macOS as of 12.3 hence the error. I still find it odd though that atom-python-run
would call for python
instead of python3
despite the settings.
QUESTION
I have just made some pulls from my library's from GitHub, I was using my windows computer to do the coding in VSCode. The code has no problem, although when I attempt to run npm install or yarn install to get the node_modules and the yarn.lock I get a weird error and the packages don't work. I'm using ZSH as the terminal for my Mac.
This is the error output:
ANSWER
Answered 2021-Oct-27 at 17:48After facing similar issues on some of our workstations, I would say that it definitely looks like a bug in Node 14.18.x on m1 Macs and/or Big Sur (even though node
itself is compiled for x86_64
). I suspect a linking issue with the zlib library, but this is a discussion for Node's issue tracker...
So here's my suggestion: uninstall Node 14.18.x and try using Node 14.17.x instead.
As a side note, you may find it useful to first install nvm. nvm
allows to quickly install several versions of Node, and switch from one to the other. For example, you might do:
QUESTION
Description
How to fix this error. I have created simple project with latest version and when try to build the project via Xcode
it generate error?
Version
0.67.3
Output of
npx react-native info
ANSWER
Answered 2022-Feb-27 at 07:55You could create that into the library source or you could avoid it and use the same UIColor option just above it.
I removed: ( [RCTConvert UIColor:options.cancelButtonTintColor() ? @( options.cancelButtonTintColor()) : nil];* ) and replace it with: ( *[RCTConvert UIColor:options.tintColor() ? @(options.tintColor()) : nil]; )
my line now looks like:
QUESTION
Please note, I'm looking for /Applications/Xcode.app/Contents/Developer/usr/bin/instruments
util (lower-case), not the Instruments
app which can be found in Xcode.app/Contents/Applications
.
I have both Xcode12
and Xcode13-beta-5
on my computer.
When run xcrun instruments -w
, Xcode13 says xcrun: error: Failed to locate 'instruments'
.
Locating the "instruments" in Xcode12:
...ANSWER
Answered 2021-Aug-23 at 14:02There's no "instruments" util because it was deprecated in Xcode12
, and in Xcode13
it seems to be removed.
Apple recommends using xcrun xctrace
instead of xcrun instruments
in Xcode12.
But as command xcrun instruments -w
is for pre-launching Simulator, xctrace
doesn't apply there.
We can run smth like
QUESTION
I triyed to execute pipenv shell in a new environtment and I got the following error:
...ANSWER
Answered 2022-Feb-12 at 13:54By github issue, the solution that works was the following:
QUESTION
I updated my macOS from Catalina to Monterey 12.2 a few days ago, and am no longer able to access Heroku from the command line (using zsh). Normally, running heroku login
from the terminal will open Heroku in a web browser, and after logging in, I am able to run subsequent Heroku commands from the CLI.
Here's the input and error message I get:
...ANSWER
Answered 2022-Feb-02 at 16:25I solved the issue, though I'm still unclear on why that particular error message was showing up. Here's what I did:
I thought I might find answers in Heroku error logs on my computer. I couldn't use the heroku logs
command, but I could search manually. Heroku's website says that these are located here ~/Library/Caches/heroku/error.log
on macOS. But this directory didn't exist. There was no heroku
folder in ~/Library/Caches/
. I still had Heroku - which heroku
correctly returned the path /usr/local/bin/heroku
.
At this point I wondered whether the CleanMyMac X
software I had used to clear storage space before updating my OS might have deleted the Heroku folder along with old error logs, and this might have prevented the program from opening?
Solution: I uninstalled the Heroku CLI based on instructions from Heroku's website:
QUESTION
I have been using php with mamp on mac for a year even with old versions of MacOS, since I installed MacOS Monterrey if I type php
on the terminal I get a message:zsh: command not found: php
Using older versions of MacOS I have never had this problem.
How can I solve the problem?
...ANSWER
Answered 2021-Oct-31 at 12:03You probably need to fix it in the .bashrc
file.
Do this:
Open the terminal and run this command:
QUESTION
I have installed nvm using brew. After that, I installed node version of 16 through nvm and check the current version using node -v to see whether the node is working properly. However, when I install version 14 or any other previous versions and runs node -v, it gives this "zsh: bad CPU type in executable: node" message and I have no idea what to do about this, though, installing node v17 and running node -v works as expected. Below are the snippet of the said commands.
...ANSWER
Answered 2022-Feb-15 at 21:39This is CPU related issue. It seems that your MacBook Air's CPU is Apple Silicon (M1).
You need update node version architecture on NVM.
QUESTION
I try to run my React Native project on MacBook Pro M1 but when I run adb it's gives error : zsh: segmentation fault adb.
I tried run adb from both ~/Library/Android/sdk/platform-tools
& ~/usr/local/bin/adb
.
Tried reinstall platform-tools in android studio.
Tried install and reinstall platform-tools from brew.
Tried reinstall android studio itself.
Device: MacBook Pro M1 2020, SSD: 512, RAM: 8
OS: macOS Monterey
Android Studio: android-studio-2021.1.1.21-mac_arm
...ANSWER
Answered 2022-Feb-07 at 17:44This looks similar to your problem. Setting up android emulators on mac m1 pros requires extra installation steps.
QUESTION
I have installed and reinstalled npm to try to run ganache and it has not been successful..really need help here!
(base) user bin % npm install -g ganache-cli
changed 6 packages, and audited 102 packages in 4s
2 packages are looking for funding
run npm fund
for details
8 vulnerabilities (7 moderate, 1 high)
To address issues that do not require attention, run: npm audit fix
To address all issues (including breaking changes), run: npm audit fix --force
Run npm audit
for details.
(base) user bin % ganache-cli
zsh: command not found: ganache-cli
ANSWER
Answered 2021-Nov-11 at 00:39The most likely cause is that the global modules installation directory is not in your path. As a quick workaround, you can run it like this:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install zsh
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page