Advertisement
Advertisement


How do I reload .bashrc without logging out and back in?


Question

If I make changes to .bashrc, how do I reload it without logging out and back in?

2018/09/11
1
1695
9/11/2018 5:22:08 AM

Accepted Answer

You just have to enter the command:

source ~/.bashrc

or you can use the shorter version of the command:

. ~/.bashrc
2014/10/09
2725
10/9/2014 5:47:54 PM

Or you could use:

exec bash

This does the same thing, and is easier to remember (at least for me).

The exec command completely replaces the shell process by running the specified command-line. In our example, it replaces whatever the current shell is with a fresh instance of bash (with the updated configuration files).

2019/12/17

To complement and contrast the two most popular answers, . ~/.bashrc and exec bash:

Both solutions effectively reload ~/.bashrc, but there are differences:

  • . ~/.bashrc or source ~/.bashrc will preserve your current shell:

    • Except for the modifications that reloading ~/.bashrc into the current shell (sourcing) makes, the current shell and its state are preserved, which includes environment variables, shell variables, shell options, shell functions, and command history.
  • exec bash, or, more robustly, exec "$BASH"[1], will replace your current shell with a new instance, and therefore only preserve your current shell's environment variables (including ones you've defined ad-hoc).

    • In other words: Any ad-hoc changes to the current shell in terms of shell variables, shell functions, shell options, command history are lost.

Depending on your needs, one or the other approach may be preferred.


[1] exec bash could in theory execute a different bash executable than the one that started the current shell, if it happens to exist in a directory listed earlier in the $PATH. Since special variable $BASH always contains the full path of the executable that started the current shell, exec "$BASH" is guaranteed to use the same executable.
A note re "..." around $BASH: double-quoting ensures that the variable value is used as-is, without interpretation by Bash; if the value has no embedded spaces or other shell metacharacters (which is not likely in this case), you don't strictly need double quotes, but using them is a good habit to form.

2019/03/24

Someone edited my answer to add incorrect English, but here was the original, which is inferior to the accepted answer.

. .bashrc
2018/01/25

Depending on your environment, just typing

bash

may also work.

2012/03/08

With this, you won't even have to type "source ~/.bashrc":

Include your bashrc file:

alias rc="vim ~/.bashrc && source ~/.bashrc"

Every time you want to edit your bashrc, just run the alias "rc"

2016/05/26

Source: https://stackoverflow.com/questions/2518127
Licensed under: CC-BY-SA with attribution
Not affiliated with: Stack Overflow
Email: [email protected]