Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
[self-remedied] exiting commands help needed
I need a little help with command-line exiting in a couple of cases.
First, I accidentally typed/ran cd `, which output bquote> and I can’t seem to exit this no matter what exit command I can think of to try.
Second, I was trying to unpack a tar file and got this error
tar: Failed to set default locale
Then it put me on a new blank line and, again, no matter what I type I can’t exit the blank line, or whatever it is.
In this last case I just want to exit before I bother trying to fix the locale problem.
Anyone set me straight on these issues?
Just curious, in macOS, when a boob like me runs into this kind of thing, can you just close the Terminal tab to kill the process or whatever and get back to ~/? That seems a little too easy to be true so I’ve not dared to try it out of fear of leaving the processes(?) hanging.
Last edited by Destry (2020-11-07 12:38:11)
Offline
Re: [self-remedied] exiting commands help needed
Destry wrote #326694:
Second, I was trying to unpack a tar file and got this error
tar: Failed to set default locale
Then it put me on a new blank line and, again, no matter what I type I can’t exit the blank line, or whatever it is.
Okay. Solved this one by killing all tar processes in a new command-line tab:
pkill tarThough that does not solve the initial error that tripped me up.
Last edited by Destry (2020-11-07 12:27:58)
Offline
Re: [self-remedied] exiting commands help needed
Destry wrote #326694:
First, I accidentally typed/ran
cd `, which outputbquote>and I can’t seem to exit this no matter what exit command I can think of to try.
And dealing with that one just requires using ctrl + c. Huh. Easy.
Seems using the right keywords is smart internet searching. ;)
Offline
Re: [self-remedied] exiting commands help needed
Destry wrote #326696:
And dealing with that one just requires using ctrl + c. Huh. Easy.
The standard OS command to stop a process: Command + . (Command + period) should work as well.
Seems using the right keywords is smart internet searching. ;)
In those situations where the command line does something my demented silly head ordered wrongly, I always need an eternity, the keywords seem to be stuck as well :-(
PS – to your OP, quoting the Terminal will always kill the running process(es) without collateral damages. The output of a running script might be damaged though.
Where is that emoji for a solar powered submarine when you need it ?
Sand space – admin theme for Textpattern
Offline
Re: [self-remedied] exiting commands help needed
Thanks for the info.
Offline