. bashrc/. profile 没有加载到新的 tmux 会话(或窗口)上——为什么？

当 tmux 启动或打开一个新窗口时，它不加载我的 .profile或 .bashrc。我每次都输入 . ~/.bashrc。有没有什么方法可以让这种情况自动发生？

37832 次浏览
小开

From this thread:

seems using .bash_profile would work.

小开
最佳答案

Yes, at the end of your .bash_profile, put the line:

. ~/.bashrc

This automatically sources the rc file under those circumstances where it would normally only process the profile.

The rules as to when bash runs certain files are complicated, and depend on the type of shell being started (login/non-login, interactive or not, and so forth), along with command line arguments and environment variables.

You can see them in the man bash output, just look for INVOCATION - you'll probably need some time to digest and decode it though :-)

小开

Running bash explicitly worked for me, by adding this line to my ~/.tmux.conf file:

set-option -g default-command "exec /bin/bash"
小开

I had the same problem and the solutions so far didn't work for me. The solution that ended up working for me can be found here.

In short, tmux windows/sessions use a login shell which looks for a ~/.profile among other files when it starts.

What I wanted was to have zsh start with each new tmux window so I put exec zsh at the bottom of my ~/.profile.

小开

The solution that worked for me is the following:

  • Create a .bash_profile file if you don't have one in ~
  • At the end of .bash_profile put source ~/.bashrc or source ~/.profile
  • Restart tmux.

The issue should now be fixed.

小开

Former answers provided solutions but didn't explain the reason. Here it is.

This is related to the Bash init files. By default, ~/.bashrc is used in an interactive, non-login shell. It won't be sourced in a login shell. Tmux uses a login shell by default. Hence, shells started by tmux skip ~/.bashrc.

default-command shell-command

The default is an empty string, which instructs tmux to create a login shell using the value of the default-shell option.

Init files for Bash,

  1. login mode:
    1. /etc/profile
    2. ~/.bash_profile, ~/.bash_login, ~/.profile (only first one that exists)
  2. interactive non-login:
    1. /etc/bash.bashrc (some Linux; not on Mac OS X)
    2. ~/.bashrc
  3. non-interactive:
    1. source file in $BASH_ENV

The weird interactive, non-login loading requirement confuses people in other situations as well. The best solution is to change the loading requirement of ~/.bashrc as interactive only, which is exactly what some distros, like Ubuntu, are doing.

# write content below into ~/.profile, or ~/.bash_profile


# if running bash
if [ -n "$BASH_VERSION" ]; then
# include .bashrc if it exists
if [ -f "$HOME/.bashrc" ]; then
. "$HOME/.bashrc"
fi
fi

This should be the solution you desire. And I recommend every Bash user setup this in the profile.

References


提交答案