Bash terminal stuck in process ([Process Completed])
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
My Bash Terminal is stuck after a bad command.
Even opening new shell instances (cmd T) starts the same hangup ending with a [Process completed] message.
It's rendering bash terminal unusable (cannot type or run any other process). How can I kill the hangup process?
Note: ^C, ^D, ^Z do not work.
bash terminal
asked Sep 26 '17 at 19:55
Growler
1165
add a comment |Â
up vote
0
down vote
favorite
My Bash Terminal is stuck after a bad command.
Even opening new shell instances (cmd T) starts the same hangup ending with a [Process completed] message.
It's rendering bash terminal unusable (cannot type or run any other process). How can I kill the hangup process?
Note: ^C, ^D, ^Z do not work.
bash terminal
asked Sep 26 '17 at 19:55
Growler
1165
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
My Bash Terminal is stuck after a bad command.
Even opening new shell instances (cmd T) starts the same hangup ending with a [Process completed] message.
It's rendering bash terminal unusable (cannot type or run any other process). How can I kill the hangup process?
Note: ^C, ^D, ^Z do not work.
bash terminal
asked Sep 26 '17 at 19:55
Growler
1165
My Bash Terminal is stuck after a bad command.
Even opening new shell instances (cmd T) starts the same hangup ending with a [Process completed] message.
It's rendering bash terminal unusable (cannot type or run any other process). How can I kill the hangup process?
Note: ^C, ^D, ^Z do not work.
bash terminal
bash terminal
asked Sep 26 '17 at 19:55
Growler
1165
asked Sep 26 '17 at 19:55
Growler
1165
asked Sep 26 '17 at 19:55
Growler
1165
asked Sep 26 '17 at 19:55
Growler
1165
asked Sep 26 '17 at 19:55
Growler
1165
1165
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
This is on macOS, right?
As it's difficult to edit the file from a terminal (owing to the fact that the shell will immediately exit), open the file you previously modified (probably ~/.bashrc, ~/.bash_profile, or ~/.profile), from the Finder, in a text editor, and correct the error.
You should be able to toggle the listing of hidden files in any "Open File" dialog box, or in the Finder itself, by pressing ⌘ CMD+⇧ SHIFT+..
Another option is simply to rename the file that you think is causing the issue. Again, do this from the Finder.
Speculating on the cause:
You may have inadvertently executed exit, possibly unconditionally, or through following some logic branching. Or you may have used set -e or set -o errexit and then had a utility exit with a non-zero exit status (i.e. failing).
answered Sep 26 '17 at 20:03
Kusalananda
106k14209327
Might be easier to simply rename the potentially offending file(s) rather than trying to shoehorn them into TextEdit without accidentally making them non-plaintext files.
– DopeGhoti
Sep 26 '17 at 20:18
@DopeGhoti That's another good option.
– Kusalananda
Sep 26 '17 at 20:23
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
This is on macOS, right?
As it's difficult to edit the file from a terminal (owing to the fact that the shell will immediately exit), open the file you previously modified (probably ~/.bashrc, ~/.bash_profile, or ~/.profile), from the Finder, in a text editor, and correct the error.
You should be able to toggle the listing of hidden files in any "Open File" dialog box, or in the Finder itself, by pressing ⌘ CMD+⇧ SHIFT+..
Another option is simply to rename the file that you think is causing the issue. Again, do this from the Finder.
Speculating on the cause:
You may have inadvertently executed exit, possibly unconditionally, or through following some logic branching. Or you may have used set -e or set -o errexit and then had a utility exit with a non-zero exit status (i.e. failing).
answered Sep 26 '17 at 20:03
Kusalananda
106k14209327
Might be easier to simply rename the potentially offending file(s) rather than trying to shoehorn them into TextEdit without accidentally making them non-plaintext files.
– DopeGhoti
Sep 26 '17 at 20:18
@DopeGhoti That's another good option.
– Kusalananda
Sep 26 '17 at 20:23
add a comment |Â
up vote
2
down vote
accepted
This is on macOS, right?
As it's difficult to edit the file from a terminal (owing to the fact that the shell will immediately exit), open the file you previously modified (probably ~/.bashrc, ~/.bash_profile, or ~/.profile), from the Finder, in a text editor, and correct the error.
You should be able to toggle the listing of hidden files in any "Open File" dialog box, or in the Finder itself, by pressing ⌘ CMD+⇧ SHIFT+..
Another option is simply to rename the file that you think is causing the issue. Again, do this from the Finder.
Speculating on the cause:
You may have inadvertently executed exit, possibly unconditionally, or through following some logic branching. Or you may have used set -e or set -o errexit and then had a utility exit with a non-zero exit status (i.e. failing).
answered Sep 26 '17 at 20:03
Kusalananda
106k14209327
Might be easier to simply rename the potentially offending file(s) rather than trying to shoehorn them into TextEdit without accidentally making them non-plaintext files.
– DopeGhoti
Sep 26 '17 at 20:18
@DopeGhoti That's another good option.
– Kusalananda
Sep 26 '17 at 20:23
add a comment |Â
up vote
2
down vote
accepted
up vote
2
down vote
accepted
This is on macOS, right?
As it's difficult to edit the file from a terminal (owing to the fact that the shell will immediately exit), open the file you previously modified (probably ~/.bashrc, ~/.bash_profile, or ~/.profile), from the Finder, in a text editor, and correct the error.
You should be able to toggle the listing of hidden files in any "Open File" dialog box, or in the Finder itself, by pressing ⌘ CMD+⇧ SHIFT+..
Another option is simply to rename the file that you think is causing the issue. Again, do this from the Finder.
Speculating on the cause:
You may have inadvertently executed exit, possibly unconditionally, or through following some logic branching. Or you may have used set -e or set -o errexit and then had a utility exit with a non-zero exit status (i.e. failing).
answered Sep 26 '17 at 20:03
Kusalananda
106k14209327
This is on macOS, right?
As it's difficult to edit the file from a terminal (owing to the fact that the shell will immediately exit), open the file you previously modified (probably ~/.bashrc, ~/.bash_profile, or ~/.profile), from the Finder, in a text editor, and correct the error.
You should be able to toggle the listing of hidden files in any "Open File" dialog box, or in the Finder itself, by pressing ⌘ CMD+⇧ SHIFT+..
Another option is simply to rename the file that you think is causing the issue. Again, do this from the Finder.
Speculating on the cause:
You may have inadvertently executed exit, possibly unconditionally, or through following some logic branching. Or you may have used set -e or set -o errexit and then had a utility exit with a non-zero exit status (i.e. failing).
answered Sep 26 '17 at 20:03
Kusalananda
106k14209327
edited Sep 26 '17 at 20:41
answered Sep 26 '17 at 20:03
Kusalananda
106k14209327
answered Sep 26 '17 at 20:03
Kusalananda
106k14209327
answered Sep 26 '17 at 20:03
Kusalananda
106k14209327
106k14209327
Might be easier to simply rename the potentially offending file(s) rather than trying to shoehorn them into TextEdit without accidentally making them non-plaintext files.
– DopeGhoti
Sep 26 '17 at 20:18
@DopeGhoti That's another good option.
– Kusalananda
Sep 26 '17 at 20:23
add a comment |Â
Might be easier to simply rename the potentially offending file(s) rather than trying to shoehorn them into TextEdit without accidentally making them non-plaintext files.
– DopeGhoti
Sep 26 '17 at 20:18
@DopeGhoti That's another good option.
– Kusalananda
Sep 26 '17 at 20:23
Might be easier to simply rename the potentially offending file(s) rather than trying to shoehorn them into TextEdit without accidentally making them non-plaintext files.
– DopeGhoti
Sep 26 '17 at 20:18
Might be easier to simply rename the potentially offending file(s) rather than trying to shoehorn them into TextEdit without accidentally making them non-plaintext files.
– DopeGhoti
Sep 26 '17 at 20:18
@DopeGhoti That's another good option.
– Kusalananda
Sep 26 '17 at 20:23
@DopeGhoti That's another good option.
– Kusalananda
Sep 26 '17 at 20:23
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f394623%2fbash-terminal-stuck-in-process-process-completed%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
