linux - Ubuntu 中的 PATH 变量设置在哪里？

Question

<分区>

Answer 1

Grzegorz Żur's answer另一个问题很好地捕捉到了它。不幸的是，它被隐藏在许多其他答案中。

There are multiple ways to do it. The actual solution depends on the purpose.

The variable values are usually stored in either a list of assignments or a shell script that is run at the start of the system or user session. In case of the shell script you must use a specific shell syntax.

System wide

1. /etc/environment List of unique assignments. Perfect for adding system-wide directories like /usr/local/something/bin to PATH variable or defining JAVA_HOME.
2. /etc/xprofile Shell script executed while starting X Window System session. This is run for every user that logs into X Window System. It is a good choice for PATH entries that are valid for every user like /usr/local/something/bin. The file is included by other script so use POSIX shell syntax not the syntax of your user shell.
3. /etc/profile and /etc/profile.d/* Shell script. This is a good choice for shell-only systems. Those files are read only by shells.
4. /etc/<shell>.<shell>rc. Shell script. This is a poor choice because it is single shell specific.

此外，/etc/environment不是脚本文件，而是由赋值表达式组成，每行一个。由于此文件存储系统范围的区域设置和路径设置，因此它是最常引用的选择。 使用 /etc/profile不是首选。它的存在只是为了指向/etc/bash.bashrc。并从 /etc/profile.d 收集条目

User session

1. ~/.pam_environment. List of unique assignments. Loaded by PAM at the start of every user session irrelevant if it is an X Window System session or shell. You cannot reference other variable including HOME or PATH so it has limited use.
2. ~/.xprofile Shell script. This is executed when the user logs into X Window System system. The variables defined here are visible to every X application. Perfect choice for extending PATH with values such as ~/bin or ~/go/bin or defining user specific GOPATH or NPM_HOME. The file is included by other script so use POSIX shell syntax not the syntax of your user shell. Your graphical text editor or IDE started by shortcut will see those values.
3. ~/.profile Shell script. It will be visible only for programs started from terminal or terminal emulator. It is a good choice for shell-only systems.
4. ~/.<shell>rc. Shell script. This is a poor choice because it is single shell specific.