When I first start a terminal session, and I use the man command, the result is delayed for a while. Yesterday, I noticed in the terminal bar that this xcodebuild was running. I do not remember seeing this in the past.
I deleted xcode and it no longer happened, but then I could not use clang or gcc in the terminal, so I reinstalled Xcode.
I still get the process as in the near past, but it does not take so long to get done.
Can anyone tell me what is going on here?
Thank you
trav
Update git by brew, it will fix.
https://github.com/robbyrussell/oh-my-zsh/issues/2189
Related
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.
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 recently upgraded to OSX 10.9 (Mavericks) and upgrade everything on Homebrew and even reinstalling vim making sure I have the latest stable version that works with Mavericks. (Vim 7.4)
But I start having this annoying warning every time I tried to editing anything with vim:
"~/.vimrc" 497L, 12210C^[[>0;95;c
Command terminated
Press ENTER or type command to continue
I know my vimrc might not be correct, but is there a way to debug this? I think it's some system command that I called on vimrc that mess it up, but is there a way to get more debugging info on which commands fail ?
Thanks,
Alright, I think I find the answer.
You can always start vim with some debugging info output to a log file:
vim -V9vim.log ~/.zshrc
That helped me!
I've got a big problem, I can't launch anything from the terminal, not python, not emacs (or aquamacs), not even 'which'.
I was using homebrew to try to install ffmpeg and was having difficulties so I decided to pay attention to the warning that always come up advising me to uninstall fink. I removed the sw directory from my root directory, which is what the fink website told me to do and was confirmed on many blogs and message boards after a quick google search.
And since then nothing has worked, I'm almost certain that this was the cause of the problem because after removing sw I immediately tried home brew again and it said 'brew: command not found'. I get the same warning with any and every program I try to launch.
I use Mac OS Lion on a 6 year old MacBook.
Any ideas?
You probably busted your PATH. You can use absolute paths to commands until you get it fixed. For example:
/bin/mv ~/.profile ~/.profile.bak
/bin/mv ~/.bash_profile ~/.bash_profile.bak
Then open a new Terminal window, where standard things should now work. and repair your profile script.
I am at a place where I don't have the installation CD or the bandwidth to do a full Xcode install (It would take well over a day) to get gcc. However I did install xcode and I notice in Developer/Xcodefiles/usr/bin/ that there is gcc. When I click on it, a terminal opens up and exits complaining no input file. Is there any way I can salvage this? man gcc says no manual entry for gcc.Thanks in advance for the help.
If you want only gcc on OS X go here: https://github.com/kennethreitz/osx-gcc-installer