A little while ago I updated to the newest version of bash on my macbook (all went smoothly there,) and decided to try out the oh-my-bash framework. I had previously used oh-my-zsh, so I was familiar with the installation; however, I'm running into an annoying problem with oh-my-bash.
When I open the terminal the framework doesn't launch automatically. It only launches if I run exec bash in the command line. I've checked in system preferences and bash is set as default, and running bash --version confirms that I am running the correct version of bash when the terminal starts up.
It's more of an inconvenience than anything else, but I'm learning scripting and my burning curiosity wants to find the solution. I'm out of ideas short of a fresh install of the framework; what do you guys think?
My solution is this:
Run this code in terminal
mv $HOME/.bashrc $HOME/bash_profile
Restart your terminal
In linux, bash run command file is .bashrc, but in MacOS is .bash_profile.
Related
Please Please help. After updating the OS to Catalina, Android Studio would still open, but none of my Flutter apps will work and the emulators do not open (they say 'Loading')
I unistalled Flutter and re-installed it, but in the Terminal when I type in flutter doctor -v, it says "zsh: command not found: flutter"
Is this because I'm no longer using bin (or bash), and now using zsh?
Can someone tell me what I can do to solve this issue? Im not very good at entering Terminal commands, so what exactly would I type to fix this issue? (I'm a beginner)
When I was entering vim bash_profile in the Terminal, I entered the following as the Export Path:
export PATH="$PATH:/Users/raymondfontaine/Developer/flutter/bin"
I had the same problem and it occurred after switching from bash to zsh. A far as I know, you have three different options.
Switch your Terminal back from zsh to bash by typing chsh -s /bin/bash and restart your Terminal. Note: You can always switch back to zsh by typing chsh -s /bin/zsh and restarting your Terminal.
You can tell zsh to use the paths specified in your bash_profile file by typing source ~/.bash_profile into your Terminal. Note: You have to do this every time you open a new Terminal.
The two options above are probably not "Best Practice". The best solution would be to set environment variables for zsh as suggested by the flutter Tutorial: Update your Path.
In your case you have to type nano $HOME/.zshrc into your Terminal enter export PATH="$PATH:/Users/raymondfontaine/Developer/flutter/bin" there, save the file and restart the Terminal. After that flutter doctor -v should run as usual.
Also the emulators in Android Studio should load again. But if you still cannot start them via the Dropdown, try opening them via Tools > AVD Manager. This worked for me while they were not visible in the Dropdown Menu.
I'm on mac, and need to open a new terminal window and run a script/compiled code in it.
Before "open -a Terminal.app Myscript" would work, but now it suddenly no longer runs the script.. only opens the Terminal Window.
If i just run the script, it works. Other scripts that worked before no longer work using open -a either.
I'm running Mojave 10.14.3 Beta. And bash 5.0.0, linked through Homebrew.
If anyone else can reproduce this, please do. I'm not sure if its a bug, or just a issue with me.
console reveals following error:
/usr/bin/open subsystem: com.apple.launchservices
"Unable to load Info.plist exceptions (eGPUOverrides)"
This error is triggered everytime the command is run.
I've also searched and haven't found anyone else experiencing this problem, nor alternatives to open -a.
It works again now. Not sure if it was due to a restart, or because of another program.
I've been using ConEmu x64 on my home computer with Git Bash, and it works well for me.
I recently started a new job and I haven't been able to get them to work together on my new machine.
At first ConEmu would run just fine but wouldn't run git bash, now after a few uninstalls when I try to launch conemu it tries to open and crashes immediately.
Git Bash works on it's own, although it's opening inside MinGW which is different than how it works on my home machine.
I don't know much about the distinction between mingw and git bash but I know mingw comes with git bash on windows.
I'm running Windows 10 on both computers and I've set the corresponding environment variables to be exactly the same using Rapid EE.
How can I launch a bash session within the ConEmu windows, without crash?
Finally fixed my issue - I uninstalled git bash and then the conemu window would stay open. I checked the Settings tab and the terminal was trying to open git bash still, and the path to the file was no longer valid. So after clearing out all the pre-defined tasks, I was able to re-install ConEmu an Git Bash and set the correct path to the git bash .exe. Works just fine now. I definitely appreciate conemu, as a Windows user in a Linux environment it's a super useful tool.
I usually:
unzip https://github.com/git-for-windows/git/releases/download/v2.7.2.windows.1/PortableGit-2.7.2-64-bit.7z.exe anywhere I want,
add the folder to the PATH, and
I am able to call <path\to\git\bin\bash.exe> in a ConEmu session without any issue.
If you do not see "Crash message", than it's improperly to say that ConEmu crashes. If your shell terminates immediately and properly, than ConEmu closes its window by default, and that is normal and expected behavior.
So your question must be rephrased like "Why my bash instance terminates immediately after start". The question does not relate to ConEmu itself.
However, reading ConEmu docs would give you much interesting notes. Especially:
ConEmu -detached
ConEmu -basic
ConEmu -log
ConEmu -? at last!
I tried to upgrade my system Vim from 7.3 to a high version so I used macport to do that. This newer version is located in /opt/local/bin/. Later I decided to uninstall it due to some reason.
Now I can't open my system Vim in the terminal, the error message is -bash: /opt/local/bin/vim: No such file or directory. Somehow the machine still thinks the vim is located in /opt/local/bin/.
Then weird thing happens, when I type which vim, it shows my vim located at /usr/local/bin, and there is indeed a vim folder in that directory, but I can't open it by typing vim in the terminal.
So here is the situation: I have two working versions of Vim in my machine, a 7.3 version in /usr/bin and a 7.4 version in /usr/local/bin(I don't know how I got this one). Both working (I have to type the whole directory /urs/bin/vim or /urs/local/bin/vim), but can't be opened in the terminal by simply typing vim.
Updates:
now I can use vi or vim, but the problem is, the former opens 7.3 whereas the latter opens 7.4
At the current command window, type:
$ hash -r
then try running vim again. Or create a new window and try in that.
Bash remembered where vim was found, and expects to find it there again. When you removed vim, it got upset and complained (rather than try to find it again before complaining). Using hash -r vim forgets all previously hashed commands and then finds vim explicitly. Run hash with no options to see what it knows.
See the Bash manual on hash for more information.
The default Vim is /usr/bin/vim. There is absolutely no reason whatsoever to change it.
If you want a more up-to-date Vim, install MacVim and use the bundled mvim script instead of vim.
I used to install something from github,I stoped it and I can't open iterm-2 too
and I open my Bash ,it appeared
Command not found: /usr/local/bin/bash
[Could not create a new process and open a pseudo-tty.]
I can't input any words.
What should I change?
Google is full of others asking for help with this problem and half-baked solutions, including reboots (re-login should do it if env changed), reinstall (why?) etc.
Looks like a clone of I messed up my terminal environment on Mac OS X and was wondering how to fix it judging by inability to start bash from /usr/local/bin. System default should be in /bin or /usr/bin.
Your terminal (console or iterm2) may have an option to specify shell explicitly, used that.