Ubuntu – How to reinitialize a terminal window instead of closing it and starting a new one

You can't do it like this because /home/user/ is not a command. It't more like a static string.

From man bash (somewhere at line 1984):

Aliases allow a string to be substituted for a word when it is used as the first word of a simple command.

In your case, execloc will never be the first word of a simple command.

But, instead to define execloc as an alias, you can define it as an environment variable:

export execloc='/home/user/'

And then you can use it everywhere you want as follow:

cd $exeloc/temp/somefolder

You have few options. One is to stop the script (CtrlZ), get the PID of the script and send SIGKILL to the process group.

When a command is executed in a shell, the process it starts and all its children are part of the same process group (in this case, the foreground process group). To send a signal to all processes in this group, you send it to the process leader. For the kill command, process leader is denoted thus:

kill -PID

Where PID is the process ID of the script.

Example:

Consider a script test.sh which launches some processes. Say you ran it in a shell:

$ ./test.sh

In another terminal,

$ pgrep test.sh
17802
$ pstree -ps `!!`
pstree -ps `pgrep test.sh`
init(1)───sshd(1211)───sshd(17312)───sshd(17372)───zsh(17788)───test.sh(17802)─┬─dd(17804)
                                                                               ├─sleep(17805)
                                                                               └─yes(17803)

In this case, to send a signal to process group created by test.sh, you'd do:

kill -INT -17802

-INT is used to send SIGINT, and so this command is the equivalent of pressing CtrlC on the terminal. To send SIGKILL:

kill -KILL -17802

You only need to stop the script if you can't open another terminal. If you can, use pgrep to find the PID.

One of the commands that the script launches may be trapping SIGINT, which is probably why CtrlC is ineffective. However, SIGKILL can't be trapped, and it is usually a last-resort option. You might want to try SIGTERM (-TERM) before going for the kill. Neither SIGKILL or SIGTERM can be set up as a keyboard shortcut the way SIGINT is.

All this is moot if your script doesn't contain a shebang line. From this SO answer:

Usually the parent shell guesses that the script is written for the the same shell (minimal Bourne-like shells run the script with /bin/sh, bash runs it as a bash subprocess) ...

Because of this, when the script is executed, you won't find a process named after script (or a process with the script's name in the command line) and pgrep will fail.

Always use a shebang line.