While using my macOs I would love to start the Atom from the terminal and I did the install shell commands from Atom, the problem is that every time I restart the machine I have to redo that to make it working again.
Do anyone knows why this happens?
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.
My macOS terminal is showing Process completed when I type any thing. I am not able to type or do anything on terminal (This effect my Android Studio and VsCode terminal also they just open close in an second) So all issue are causing with this terminal I try every thing restore profile etc nothing is working for me.
But one thing is strange here when I restart my Mac terminal works fine but after I work on android studio or vscode with Mac terminal (Not there default terminal because they are not working) After 1 hour same happen as I say before and as in screenshot.
On different questions solutions was to type /bin/bash -x on terminal but I can't even type single character on this.
I am finding solution for this from 1 week and not able to find any thing I need to restart me laptop every 1 hour to work.
I am using BigSur with M1 processor.
Also it was working fine before but I work on Flutter so I have set path and run commands like
Run: nano ~/.zshrc
Add: export PATH=[PATH_TO_FLUTTER_GIT_DIRECTORY]/flutter/bin:$PATH
Run: source ~/.zshrc
And some bash commands to set path.
I get the following message when opening the terminal on mac
Last login: Tue Mar 11 14:33:24 on console
login(291,0x7fff78af9310) malloc: * error for object 0x7f974be006f0: pointer being freed was not allocated
* set a breakpoint in malloc_error_break to debug
[Process completed]
... and I don't seem to be able to escape it. I've been having some weird permissions problems with Adobe CC - could the two be symptoms of a single problem?
It looks like you don't have the right permissions on the /usr/bin directory.
Solution for OS X 10.11 (El Capitan) and later:
Install Onyx 3.1.3 app (Free analog of Disk Utility)
Choose 'Maintenance' -> 'Permissions' -> 'Execute'.
Solution for older versions of OS X:
Open 'Disk Utility' app -> Press 'Repair Disk Permissions'.
It will set default permissions for the /usr/bin directory.
If this step doesn't help try this:
Delete com.apple.terminal.plist from the ~/Library/Preferences folder;
Running on Mac OS X Mavericks just
Open "Disk Utility" app -> Press "Repair Disk Permissions"
Solved the problem
I couldn't find any com.apple.terminal.plist in the ~/Library/Preference folder
I had a similar issue while running OSX 10.11.6. I got a similar error when I ran certain commands, but it did not force bash to exit. It just aborted the command.
I tried running Onyx and repairing disk permissions via command line with no results (along with about another 100 or so desperate "fixes").
Eventually, I tried upgrading to a newer version of bash, which fixed the problem. To do this:
brew install bash
sudo -s
echo /usr/local/bin/bash >> /etc/shells
chsh -s /usr/local/bin/bash
Restart the computer.
I write this in the hopes that if someone else has this error they have one more fix to try!
I tried running the Disk Utility and it kept crashing. I had to run it from OSX Recovery Mode.
You can enter OSX Recovery Mode during system boot by holding down CMD ⌘+R as your mac is booting up. Choose Disk Utility when it reaches the Recovery Options screen.
I had the same problem with my dev machine. After several hours of trying anything other than a reinstall I finally realized that was the only choice. It should have been the FIRST choice. SO EASY!
Back up the critical data (just in case)
Enter the recovery mode by pressing cmd+r at start up
Choose "Reinstall Mac OS X"
That's it. When my computer restarted I was prompted for my Apple ID credentials and then my user loaded like normal, with a working Terminal, even. I didn't need to reinstall / restore anything. The whole process (including the user folder backup) took about 45 min.
Final step, remove all of the sketchy utilities installed trying to fix this without a reinstall.
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.
Every time I open my Terminal application at work it starts from a clean slate (e.g. it opens from the ~/ directory). But at home on my laptop my Terminal always remembers the last directory I was in (and all the commands on the screen) and displays them to me.
I'm trying to get this to happen when I'm at work but I can't find any information on it (I've no idea why or how my laptop managed to set itself to work that way?).
The only thing I've found out is that I can change the preferences so the Terminal executes a particular command when the app is started up, but that's not quite what I want (simply because I'm not sure what command I would run to get the Terminal to go to the directory I was looking at when I had the Terminal open last).
Any ideas?
Thanks!
Since you're using Lion, it should do that automatically.
You might have disabled the Resume functionality systemwide or in Terminal.
Make sure it's enabled systemwide. You can also try to manually enable it for Terminal:
defaults write com.apple.Terminal NSQuitAlwaysKeepsWindows -bool true