blocks|key|57553|text|在包括++()之前，您可以在以下位置设置它们：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|57554|~/.MacOSX/environment.plist|code-block|syntax|javascript|57555|请参见：|57556|57557|https://developer.apple.com/legacy/library/qa/qa1067/_index.html|unordered-list-item|57558|https://developer.apple.com/library/content/documentation/MacOSX/Conceptual/BPRuntimeConfig/Articles/EnvironmentVars.html|57559|57560|对于终端中的路径，您应该能够在.bash_profile或.profile中进行设置(尽管您可能必须创建它)|CODE|57561|适用于++(山狮)和beyond+you+need+to+use+launchd+and+launchctl的。|57562|entityMap|0|LINK|mutability|MUTABLE|url|1|2|http://www.dowdandassociates.com/blog/content/howto-set-an-environment-variable-in-mac-os-x-slash-etc-slash-launchd-dot-conf/^0|5|2|0|0|0|0|0|1S|0|0|0|3D|1|0|0|F|D|T|8|0|5|B|1J|1|X|7|19|9|H|11|2|0^^$0|@$1|2|3|4|5|6|7|18|8|@$9|19|A|1A|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|1B|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|1C|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|1D|8|@]|D|@]|E|$]]|$1|N|3|O|5|P|7|1E|8|@]|D|@$9|1F|A|1G|1|1H]]|E|$]]|$1|Q|3|R|5|P|7|1I|8|@]|D|@$9|1J|A|1K|1|1L]]|E|$]]|$1|S|3|-4|5|6|7|1M|8|@]|D|@]|E|$]]|$1|T|3|U|5|6|7|1N|8|@$9|1O|A|1P|B|V]|$9|1Q|A|1R|B|V]]|D|@]|E|$]]|$1|W|3|X|5|6|7|1S|8|@$9|1T|A|1U|B|C]|$9|1V|A|1W|B|C]|$9|1X|A|1Y|B|V]|$9|1Z|A|20|B|V]]|D|@$9|21|A|22|1|23]]|E|$]]|$1|Y|3|-4|5|6|7|24|8|@]|D|@]|E|$]]]|Z|$10|$5|11|12|13|E|$14|O]]|15|$5|11|12|13|E|$14|R]]|16|$5|11|12|13|E|$14|17]]]]

Up to and including <a href="http://en.wikipedia.org/wiki/Mac_OS_X_Lion" rel="noreferrer">OS&nbsp;X&nbsp;v10.7</a> (Lion) you can set them in:

<pre><code>~/.MacOSX/environment.plist
</code></pre>

See:

<ul>
<li><a href="https://developer.apple.com/legacy/library/qa/qa1067/_index.html" rel="noreferrer">https://developer.apple.com/legacy/library/qa/qa1067/_index.html</a></li>
<li><a href="https://developer.apple.com/library/content/documentation/MacOSX/Conceptual/BPRuntimeConfig/Articles/EnvironmentVars.html" rel="noreferrer">https://developer.apple.com/library/content/documentation/MacOSX/Conceptual/BPRuntimeConfig/Articles/EnvironmentVars.html</a></li>
</ul>

For PATH in the Terminal, you should be able to set in <code>.bash_profile</code> or <code>.profile</code> (you'll probably have to create it though)

For <a href="http://en.wikipedia.org/wiki/OS_X_Mountain_Lion" rel="noreferrer">OS&nbsp;X&nbsp;v10.8</a> (Mountain Lion) and beyond <a href="http://www.dowdandassociates.com/blog/content/howto-set-an-environment-variable-in-mac-os-x-slash-etc-slash-launchd-dot-conf/" rel="noreferrer">you need to use <code>launchd</code> and <code>launchctl</code></a>.

blocks|key|58274|text|任何Bash启动文件--+~/.bashrc、~/.bash_profile、~/.profile。对于图形用户界面应用程序中的环境变量，还有一个名为~/.MacOSX/environment.plist的奇怪文件。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|58275|entityMap^0|D|9|N|F|13|A|23|R|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|G|$]]

Any of the Bash startup files -- <code>~/.bashrc</code>, <code>~/.bash_profile</code>, <code>~/.profile</code>. There's also some sort of weird file named <code>~/.MacOSX/environment.plist</code> for environment variables in GUI applications.

blocks|key|2757532|text|对于单个用户修改，请使用您列出的~/.profile。下面的链接解释了Bash何时读取不同的文件。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2757533|http://telin.ugent.be/~slippens/drupal/bashrc_and_others|2757534|如果要为gui应用程序设置环境变量，则需要~/..MacOSX/+environment+ment.plist文件|2757535|entityMap|0|LINK|mutability|MUTABLE|url^0|G|A|0|0|1K|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@]|D|@$9|U|A|V|1|W]]|E|$]]|$1|H|3|I|5|6|7|X|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|G]]]]

For a single user modification, use <code>~/.profile</code> of the ones you listed. The following link explains when the different files are read by Bash.

<a href="http://telin.ugent.be/~slippens/drupal/bashrc_and_others" rel="nofollow noreferrer">http://telin.ugent.be/~slippens/drupal/bashrc_and_others</a>

If you want to set the environment variable for gui applications you need the ~/.MacOSX/environment.plist file

blocks|key|2545766|text|我对/etc/paths和~/.MacOSX/environment.plist文件不太确定。这些都是新的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2545767|但是使用Bash时，您应该知道每次新的shell调用都会执行.bashrc，而.bash_profile只在启动时执行一次。|2545768|我不知道这种情况在Mac和OS-X中有多频繁，我认为这种区别已经随着window系统启动一切而被打破了。|2545769|就我个人而言，我通过创建一个包含我需要的所有内容的.bashrc文件来消除混淆，然后执行以下操作：|2545770|ln+-s+.bashrc+.bash_profile|code-block|syntax|javascript|2545771|entityMap^0|2|A|D|R|0|U|7|13|D|0|0|P|7|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@$9|Y|A|Z|B|C]|$9|10|A|11|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|12|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|13|8|@$9|14|A|15|B|C]]|D|@]|E|$]]|$1|L|3|M|5|N|7|16|8|@]|D|@]|E|$O|P]]|$1|Q|3|-4|5|6|7|17|8|@]|D|@]|E|$]]]|R|$]]

Well, I'm unsure about the <code>/etc/paths</code> and <code>~/.MacOSX/environment.plist</code> files. Those are new.

But with Bash, you should know that <code>.bashrc</code> is executed with every new shell invocation
and <code>.bash_profile</code> is only executed once at startup.

I don't know how often this is with Mac&nbsp;OS&nbsp;X. I think the distinction has broken down with the window system launching everything.

Personally, I eliminate the confusion by creating a <code>.bashrc</code> file with everything I need and then do:

<pre><code>ln -s .bashrc .bash_profile
</code></pre>

blocks|key|56678|text|有时之前的所有答案都不起作用。如果您想在Eclipse或IntelliJ+IDEA中访问系统变量(如M2_HOME)，在这种情况下，对我来说唯一有效的方法是：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|56679|首先(步骤1)编辑/etc/launchd.conf，使其包含如下行："setenv+value“，然后(步骤2)重新启动。|56680|简单地修改.bash_profile是行不通的，因为在OS中，应用程序不会像在其他Unix中那样启动；它们不会继承父操作系统的外壳变量。所有其他修改都不会起作用，原因我也不知道。也许其他人可以澄清这一点。|56681|entityMap^0|1E|7|0|9|H|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|R|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|K|$]]

Sometimes all of the previous answers simply don't work. If you want to have access to a system variable (like <code>M2_HOME</code>) in Eclipse or in IntelliJ IDEA the only thing that works for me in this case is:

First (step 1) edit <code>/etc/launchd.conf</code> to contain a line like this: "setenv VAR value" and then (step 2) reboot.

Simply modifying .bash_profile won't work because in OS&nbsp;X the applications are not started as in other Unix'es; they don't inherit the parent's shell variables. All the other modifications won't work for a reason that is unknown to me. Maybe someone else can clarify about this.

blocks|key|58331|text|布鲁诺走上了正轨。我做了大量的研究，如果你想设置在所有图形用户界面应用程序中可用的变量，你唯一的选择就是/etc/launchd.conf。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|58332|请注意，environment.plist+does+not+work+for+applications+launched+via+Spotlight.+This+is+documented+by+Steve+Sexton+here。|58333|58334|打开终端提示符|ordered-list-item|58335|类型sudo+vi+/etc/launchd.conf+(注意:此文件可能还不存在)|58336|将如下内容放入此处的fileSet环境变量中，以便它们全局可用于所有应用程序#(和终端)，包括那些通过Spotlight启动的应用程序。##编辑完该文件后，在终端执行以下命令，无需重启即可全局更新#环境变量。#注意:您仍然需要重新启动相关的应用程序(包括#+Terminal)才能使更改生效！#+grep+-E+"%5Esetenv“/etc/launchd.conf+%7C+xargs+-t+-L+1启动etc##请参阅http://www.digitaledgesw.com/node/31+#和http://stackoverflow.com/questions/135688/setting-environment-variables-in-os-x/+##请注意，您必须硬编码下面的路径，不要使用环境变量。#您还需要用引号将多个值括起来，请参阅下面的MAVEN_OPTS示例。#+setenv+JAVA_VERSION+1.6+setenv+JAVA_HOME+/System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home+setenv+GROOVY_HOME+/Applications/Dev/groovy+setenv+GRAILS_HOME+/Applications/Dev/Dev/grails+setenv+NEXUS_HOME+/Applications/Dev/nexus/nexus-webapp+setenv+JRUBY_HOME+/Applications/Dev/jruby+setenv+ANT_HOME+/Applications/Dev/apache-ant+setenv+ANT_OPTS+-Xmx512M+setenv+MAVEN_OPTS+"-Xmx1024M+-XX:MaxPermSize=512m“setenv+M2_HOME+/Applications/Dev/apache-maven+setenv+JMETER_HOME在vi中/Applications/Dev/jakarta-jmeter|58337|Save你的更改，然后重启你的Mac。或者使用上面的代码注释中所示的grep/xargs命令。|58338|通过打开终端窗口并键入export来证明您的变量正在工作，您应该会看到新的变量。这些也将在IntelliJ+IDEA和通过Spotlight启动的其他图形用户界面应用程序中可用。|58339|58340|entityMap|0|LINK|mutability|MUTABLE|url|https://web.archive.org/web/20100212232552/https://www.digitaledgesw.com/node/31|1|http://www.digitaledgesw.com/node/31|2|http://stackoverflow.com/questions/135688/setting-environment-variables-in-os-x/|3|http://linux.die.net/man/1/grep|4|https://linux.die.net/man/1/xargs^0|1G|H|0|4|34|0|0|0|0|2|P|0|5S|10|1|6V|28|2|0|Y|4|13|5|Y|4|3|13|5|4|0|B|6|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@$9|1B|A|1C|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1D|8|@]|D|@$9|1E|A|1F|1|1G]]|E|$]]|$1|H|3|-4|5|6|7|1H|8|@]|D|@]|E|$]]|$1|I|3|J|5|K|7|1I|8|@]|D|@]|E|$]]|$1|L|3|M|5|K|7|1J|8|@$9|1K|A|1L|B|C]]|D|@]|E|$]]|$1|N|3|O|5|K|7|1M|8|@]|D|@$9|1N|A|1O|1|1P]|$9|1Q|A|1R|1|1S]]|E|$]]|$1|P|3|Q|5|K|7|1T|8|@$9|1U|A|1V|B|C]|$9|1W|A|1X|B|C]]|D|@$9|1Y|A|1Z|1|20]|$9|21|A|22|1|23]]|E|$]]|$1|R|3|S|5|K|7|24|8|@$9|25|A|26|B|C]]|D|@]|E|$]]|$1|T|3|-4|5|6|7|27|8|@]|D|@]|E|$]]|$1|U|3|-4|5|6|7|28|8|@]|D|@]|E|$]]]|V|$W|$5|X|Y|Z|E|$10|11]]|12|$5|X|Y|Z|E|$10|13]]|14|$5|X|Y|Z|E|$10|15]]|16|$5|X|Y|Z|E|$10|17]]|18|$5|X|Y|Z|E|$10|19]]]]

Bruno is right on track. I've done extensive research and if you want to set variables that are available in all GUI applications, your only option is <code>/etc/launchd.conf</code>.

Please note that <a href="https://web.archive.org/web/20100212232552/https://www.digitaledgesw.com/node/31" rel="noreferrer">environment.plist does not work for applications launched via Spotlight. This is documented by Steve Sexton here</a>.

<ol>
<li>Open a terminal prompt</li>
<li>Type <code>sudo vi /etc/launchd.conf</code> (note: this file might not yet exist)</li>
<li>Put contents like the following into the file

<pre class="lang-none prettyprint-override"><code># Set environment variables here so they are available globally to all apps
# (and Terminal), including those launched via Spotlight.
#
# After editing this file run the following command from the terminal to update
# environment variables globally without needing to reboot.
# NOTE: You will still need to restart the relevant application (including
# Terminal) to pick up the changes!
# grep -E "^setenv" /etc/launchd.conf | xargs -t -L 1 launchctl
#
# See http://www.digitaledgesw.com/node/31
# and http://stackoverflow.com/questions/135688/setting-environment-variables-in-os-x/
#
# Note that you must hardcode the paths below, don't use environment variables.
# You also need to surround multiple values in quotes, see MAVEN_OPTS example below.
#
setenv JAVA_VERSION 1.6
setenv JAVA_HOME /System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home
setenv GROOVY_HOME /Applications/Dev/groovy
setenv GRAILS_HOME /Applications/Dev/grails
setenv NEXUS_HOME /Applications/Dev/nexus/nexus-webapp
setenv JRUBY_HOME /Applications/Dev/jruby

setenv ANT_HOME /Applications/Dev/apache-ant
setenv ANT_OPTS -Xmx512M

setenv MAVEN_OPTS "-Xmx1024M -XX:MaxPermSize=512m"
setenv M2_HOME /Applications/Dev/apache-maven

setenv JMETER_HOME /Applications/Dev/jakarta-jmeter
</code></pre></li>
<li>Save your changes in vi and reboot your Mac. Or use the <a href="http://linux.die.net/man/1/grep" rel="noreferrer"><code>grep</code></a>/<a href="https://linux.die.net/man/1/xargs" rel="noreferrer"><code>xargs</code></a> command which is shown in the code comment above.</li>
<li>Prove that your variables are working by opening a Terminal window and typing <code>export</code> and you should see your new variables. These will also be available in IntelliJ IDEA and other GUI applications you launch via Spotlight.</li>
</ol>

blocks|key|2757641|text|我认为操作员正在寻找一种简单的、类似Windows的解决方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2757642|这就是了：|2757643|http://www.apple.com/downloads/macosx/system_disk_utilities/environmentvariablepreferencepane.html|offset|length|2757644|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|2Q|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@$F|R|G|S|1|T]]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|E]]]]

I think the OP is looking for a simple, Windows-like solution.

Here you go:

<a href="http://www.apple.com/downloads/macosx/system_disk_utilities/environmentvariablepreferencepane.html" rel="nofollow noreferrer">http://www.apple.com/downloads/macosx/system_disk_utilities/environmentvariablepreferencepane.html</a>

blocks|key|2757649|text|除了建议的方法之外，还需要注意的一件事是，至少在OS X 10.5+(豹)中，在launchd.conf中设置的变量将与在.profile中进行的设置合并。我想这可能对~/.MacOSX/environment.plist中的设置也是有效的，但我还没有验证。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2757650|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Mac_OS_X_Leopard^0|14|C|1P|8|2C|R|O|9|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]|$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@$9|U|A|V|1|W]]|E|$]]|$1|F|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

One thing to note in addition to the approaches suggested is that, in <a href="http://en.wikipedia.org/wiki/Mac_OS_X_Leopard" rel="nofollow noreferrer">OS&nbsp;X&nbsp;10.5</a> (Leopard) at least, the variables set in <code>launchd.conf</code> will be merged with the settings made in <code>.profile</code>. I suppose this is likely to be valid for the settings in <code>~/.MacOSX/environment.plist</code> too, but I haven't verified.

blocks|key|2545883|text|在OS+X中处理环境变量时，基本上有两个问题需要解决。第一个问题是从Spotlight+(+Mac菜单/状态栏右侧的放大镜图标)调用程序时，第二个问题是从Dock调用程序时。从终端应用程序/实用程序调用程序很简单，因为它从标准外壳位置(~/.profile、~/.bash_profile、~/.bashrc等)读取环境|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2545884|从Dock调用程序时，在<dict>元素包含<key>KEY</key><string>theValue</string>元素序列的情况下使用~/.MacOSX/environment.plist。|2545885|从Spotlight调用程序时，请确保已使用所需的所有键/值设置设置了launchd。|2545886|为了同时解决这两个问题，我在我的用户帐户上使用登录项目(通过系统首选项工具设置)。登录项是一个调用Emacs+lisp函数的bash脚本，当然也可以使用自己喜欢的脚本工具来完成相同的任务。这种方法有一个额外的好处，那就是它可以在任何时候工作，并且不需要重新启动，也就是说，人们可以编辑~/.profile，在一些shell中运行登录项，并且可以从Dock或Spotlight看到新调用的程序所做的更改。|2545887|详细信息：|2545888|登录项目：~/bin/macosx-startup|2545889|#!/bin/bash
bash+-l+-c+"/Applications/Emacs.app/Contents/MacOS/Emacs+--batch+-l+~/lib/emacs/elisp/macosx/environment-support.el+-f+generate-environment"|code-block|syntax|javascript|2545890|Emacs+lisp函数：~/lib/emacs/elisp/macosx/envionment-support.el|2545891|;;;+Provide+support+for+the+environment+on+Mac+OS+X

(defun+generate-environment+()
++"Dump+the+current+environment+into+the+~/.MacOSX/environment.plist+file."
++;;+The+system+environment+is+found+in+the+global+variable:
++;;+'initial-environment'+as+a+list+of+"KEY=VALUE"+pairs.
++(let+((list+initial-environment)
++++++++pair+start+command+key+value)
++++;;+clear+out+the+current+environment+settings
++++(find-file+"~/.MacOSX/environment.plist")
++++(goto-char+(point-min))
++++(setq+start+(search-forward+"<dict>\n"))
++++(search-forward+"</dict>")
++++(beginning-of-line)
++++(delete-region+start+(point))
++++(while+list
++++++(setq+pair+(split-string+(car+list)+"=")
++++++++++++list+(cdr+list))
++++++(setq+key+(nth+0+pair)
++++++++++++value+(nth+1+pair))
++++++(insert+"++<key>"+key+"</key>\n")
++++++(insert+"++<string>"+value+"</string>\n")

++++++;;+Enable+this+variable+in+launchd
++++++(setq+command+(format+"launchctl+setenv+%25s+\"%25s\""+key+value))
++++++(shell-command+command))
++++;;+Save+the+buffer.
++++(save-buffer)))|2545892|注意:这个解决方案是我之前添加的解决方案的混合体，特别是Matt+Curtis提供的解决方案，但我故意保持我的~/.bash_profile内容平台独立，并将launchd环境(一个仅限Mac的工具)的设置放在一个单独的脚本中。|2545893|entityMap^0|3A|A|3L|F|41|9|0|C|6|M|13|1Z|R|0|0|3Y|A|0|0|5|K|0|0|D|1A|0|0|1J|F|27|7|0^^$0|@$1|2|3|4|5|6|7|12|8|@$9|13|A|14|B|C]|$9|15|A|16|B|C]|$9|17|A|18|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|19|8|@$9|1A|A|1B|B|C]|$9|1C|A|1D|B|C]|$9|1E|A|1F|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|1G|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|1H|8|@$9|1I|A|1J|B|C]]|D|@]|E|$]]|$1|L|3|M|5|6|7|1K|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|1L|8|@$9|1M|A|1N|B|C]]|D|@]|E|$]]|$1|P|3|Q|5|R|7|1O|8|@]|D|@]|E|$S|T]]|$1|U|3|V|5|6|7|1P|8|@$9|1Q|A|1R|B|C]]|D|@]|E|$]]|$1|W|3|X|5|R|7|1S|8|@]|D|@]|E|$S|T]]|$1|Y|3|Z|5|6|7|1T|8|@$9|1U|A|1V|B|C]|$9|1W|A|1X|B|C]]|D|@]|E|$]]|$1|10|3|-4|5|6|7|1Y|8|@]|D|@]|E|$]]]|11|$]]

There are essentially two problems to solve when dealing with
environment variables in OS X. The first is when invoking programs
from Spotlight (the magnifying glass icon on the right side of the Mac
menu/status bar) and the second when invoking programs from the Dock.
Invoking programs from a Terminal application/utility is trivial
because it reads the environment from the standard shell locations
(<code>~/.profile</code>, <code>~/.bash_profile</code>, <code>~/.bashrc</code>, etc.)

When invoking programs from the Dock, use <code>~/.MacOSX/environment.plist</code>
where the <code>&lt;dict&gt;</code> element contains a sequence of
<code>&lt;key&gt;KEY&lt;/key&gt;&lt;string&gt;theValue&lt;/string&gt;</code> elements.

When invoking programs from Spotlight, ensure that launchd has been
setup with all the key/value settings you require.

To solve both problems simultaneously, I use a login item (set via the
System Preferences tool) on my User account. The login item is a bash script that
invokes an Emacs lisp function although one can of course use their
favorite scripting tool to accomplish the same thing. This approach
has the added benefit that it works at any time and does not require a
reboot, i.e. one can edit <code>~/.profile</code>, run the login item in some shell and have the changes visible for newly invoked programs, from either the Dock or Spotlight.

Details:

Login item: <code>~/bin/macosx-startup</code>

<pre><code>#!/bin/bash
bash -l -c "/Applications/Emacs.app/Contents/MacOS/Emacs --batch -l ~/lib/emacs/elisp/macosx/environment-support.el -f generate-environment"
</code></pre>

Emacs lisp function: <code>~/lib/emacs/elisp/macosx/envionment-support.el</code>

<pre><code>;;; Provide support for the environment on Mac OS X

(defun generate-environment ()
 "Dump the current environment into the ~/.MacOSX/environment.plist file."
 ;; The system environment is found in the global variable:
 ;; 'initial-environment' as a list of "KEY=VALUE" pairs.
 (let ((list initial-environment)
 pair start command key value)
 ;; clear out the current environment settings
 (find-file "~/.MacOSX/environment.plist")
 (goto-char (point-min))
 (setq start (search-forward "&lt;dict&gt;\n"))
 (search-forward "&lt;/dict&gt;")
 (beginning-of-line)
 (delete-region start (point))
 (while list
 (setq pair (split-string (car list) "=")
 list (cdr list))
 (setq key (nth 0 pair)
 value (nth 1 pair))
 (insert " &lt;key&gt;" key "&lt;/key&gt;\n")
 (insert " &lt;string&gt;" value "&lt;/string&gt;\n")

 ;; Enable this variable in launchd
 (setq command (format "launchctl setenv %s \"%s\"" key value))
 (shell-command command))
 ;; Save the buffer.
 (save-buffer)))
</code></pre>

NOTE: This solution is an amalgam of those coming before I added mine, particularly that offered by Matt Curtis, but I have deliberately tried to keep my <code>~/.bash_profile</code> content platform independent and put the setting of the <code>launchd</code> environment (a Mac only facility) into a separate script.

blocks|key|2757722|text|在追逐Environment+Variables+preference+pane并发现链接断开后，在苹果网站上的搜索似乎表明他们已经忘记了这一点……我又回到了难以捉摸的启动过程中。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2757723|在我的系统(MacOSX10.6.8)上，在environment.plist中定义的变量似乎可以可靠地导出到从Spotlight启动的应用程序(通过launchd)。我的问题是，这些var没有被导出到终端的新bash会话中。也就是说，我有与这里描述的相反的问题。|2757724|注意:如前所述，environment.plist看起来像JSON，而不是XML。|2757725|我能够让Spotlight应用程序看到editing+~/MacOSX/environment.plist+和的vars，我可以通过在我的.profile文件中添加以下内容来强制将相同的vars添加到新的终端会话中：|style|BOLD|2757726|eval+$(launchctl+export)|code-block|syntax|javascript|2757727|entityMap|0|LINK|mutability|MUTABLE|url|http://www.apple.com/downloads/macosx/system_disk_utilities/environmentvariablepreferencepane.html|1|http://developer.apple.com/library/mac/#documentation/MacOSX/Conceptual/BPRuntimeConfig/Articles/EnvironmentVars.html%2523//apple_ref/doc/uid/20002093-BCIJIJBH^0|3|11|0|0|0|0|1I|1|J|Y|1|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@$A|11|B|12|1|13]]|C|$]]|$1|D|3|E|5|6|7|14|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|15|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|16|8|@$A|17|B|18|J|K]]|9|@$A|19|B|1A|1|1B]]|C|$]]|$1|L|3|M|5|N|7|1C|8|@]|9|@]|C|$O|P]]|$1|Q|3|-4|5|6|7|1D|8|@]|9|@]|C|$]]]|R|$S|$5|T|U|V|C|$W|X]]|Y|$5|T|U|V|C|$W|Z]]]]

After chasing the <a href="http://www.apple.com/downloads/macosx/system_disk_utilities/environmentvariablepreferencepane.html" rel="nofollow">Environment Variables preference pane</a> and discovering that the link is broken and a search on Apple's site seems to indicate they've forgotten about it... I started back onto the trail of the elusive launchd process.

On my system (Mac OS X 10.6.8) it appears that variables defined in environment.plist are being reliably exported to apps launched from Spotlight (via launchd). My trouble is that those vars are not being exported to new bash sessions in Terminal. I.e. I have the opposite problem as portrayed here.

NOTE: environment.plist looks like JSON, not XML, as described previously

I was able to get Spotlight apps to see the vars by <a href="http://developer.apple.com/library/mac/#documentation/MacOSX/Conceptual/BPRuntimeConfig/Articles/EnvironmentVars.html%23//apple_ref/doc/uid/20002093-BCIJIJBH" rel="nofollow">editing ~/MacOSX/environment.plist</a> and
I was able to force the same vars into a new Terminal session by adding the following to my .profile file:

<pre><code>eval $(launchctl export)
</code></pre>

blocks|key|56978|text|对于Bash，尝试将您的环境变量添加到文件/etc/profile中，以使所有用户都可以使用它们。不需要重新启动，只需启动一个新的终端会话。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|56979|entityMap^0|L|C|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

For Bash, try adding your environment variables to the file <code>/etc/profile</code> to make them available for all users. No need to reboot, just start a new Terminal session.

blocks|key|2545937|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2545938|Do：|ordered-list-item|2545939|2545940|vim+~/.bash_profile|2545941|文件可能不存在(如果不存在，您可以直接创建它)。|2545942|键入以下内容并保存文件：|unordered-list-item|2545943|2545944|导出PATH=$PATH:YOUR_PATH_HERE|2545945|Run|2545946|2545947|源~/.bash_profile|2545948|entityMap^0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|V|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|W|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|X|7|@]|8|@]|9|$]]|$1|E|3|F|4|5|6|Y|7|@]|8|@]|9|$]]|$1|G|3|H|4|5|6|Z|7|@]|8|@]|9|$]]|$1|I|3|J|4|K|6|10|7|@]|8|@]|9|$]]|$1|L|3|-4|4|5|6|11|7|@]|8|@]|9|$]]|$1|M|3|N|4|5|6|12|7|@]|8|@]|9|$]]|$1|O|3|P|4|K|6|13|7|@]|8|@]|9|$]]|$1|Q|3|-4|4|5|6|14|7|@]|8|@]|9|$]]|$1|R|3|S|4|5|6|15|7|@]|8|@]|9|$]]|$1|T|3|-4|4|5|6|16|7|@]|8|@]|9|$]]]|U|$]]

<ol>
<li>Do:

<pre><code>vim ~/.bash_profile
</code></pre>

The file may not exist (if not, you can just create it).</li>
<li>Type in this and save the file:

<pre><code>export PATH=$PATH:YOUR_PATH_HERE
</code></pre></li>
<li>Run

<pre><code>source ~/.bash_profile
</code></pre></li>
</ol>

blocks|key|57676|text|$PATH变量也受制于path_helper，后者反过来使用/etc/paths文件和/etc/paths.d中的文件。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|57677|更详细的描述可以在+(2008-11)中找到|57678|entityMap^0|0|5|B|B|U|A|17|C|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|I|$]]

The <code>$PATH</code> variable is also subject to <code>path_helper</code>, which in turn makes use of the <code>/etc/paths</code> file and files in <code>/etc/paths.d</code>. 

A more thorough description can be found in <a href="http://hea-www.harvard.edu/~fine/OSX/path_helper.html" rel="nofollow noreferrer">PATH and other environment issues in Leopard</a> (2008-11)

blocks|key|2545970|text|虽然这里的答案不是“错误的”，但我将添加另一个:永远不要在OS中进行影响“所有进程”的环境变量更改，甚至在shell之外，对给定用户交互运行的所有进程进行更改。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2545971|根据我的经验，环境变量的全局更改，比如所有进程的PATH，在OS+X上比在Windows上更有可能造成破坏。原因是，许多OS+X应用程序和其他软件(可能尤其是操作系统本身的组件)在幕后依赖于UNIX命令行工具，并假定这些工具随系统提供的版本的行为，并且在执行此操作时不一定使用绝对路径(类似的注释适用于动态加载库和DYLD_*环境变量)。例如，考虑到各种Stack+Overflow问题的最高评分答案通常会说“不要这么做”。|2545972|在这方面，OS实际上与其他类UNIX操作系统(例如，Linux、FreeBSD和Solaris)没有什么不同；最可能的原因是苹果没有提供一种简单的方法来做到这一点，因为它破坏了一些东西。在一定程度上，Windows不容易出现这些问题，这是由于两件事：(1)+Windows软件不像UNIX软件那样倾向于依赖命令行工具，(2)+Microsoft在"DLL地狱“和安全问题方面有着如此广泛的历史，这些问题是由影响所有进程的更改引起的，以至于他们在较新的Windows版本中更改了动态加载的行为，以限制”全局“配置选项(如PATH+)的影响。|2545973|不管“差劲”与否，如果您将这样的更改限制在较小的范围内，您将拥有一个更加稳定的系统。|2545974|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

While the answers here aren't "wrong", I'll add another: never make environment variable changes in OS X that affect "all processes", or even, outside the shell, for all processes run interactively by a given user.

In my experience, global changes to environment variables like PATH for all processes are even more likely to break things on OS X than on Windows. Reason being, lots of OS X applications and other software (including, perhaps especially, components of the OS itself) rely on UNIX command-line tools under the hood, and assume the behavior of the versions of these tools provided with the system, and don't necessarily use absolute paths when doing so (similar comments apply to dynamically-loaded libraries and DYLD_* environment variables). Consider, for instance, that the highest-rated answers to various Stack Overflow questions about replacing OS X-supplied versions of interpreters like Python and Ruby generally say "don't do this."

OS X is really no different than other UNIX-like operating systems (e.g., Linux, FreeBSD, and Solaris) in this respect; the most likely reason Apple doesn't provide an easy way to do this is because it breaks things. To the extent Windows isn't as prone to these problems, it's due to two things: (1) Windows software doesn't tend to rely on command-line tools to the extent that UNIX software does, and (2) Microsoft has had such an extensive history of both "DLL hell" and security problems caused by changes that affect all processes that they've changed the behavior of dynamic loading in newer Windows versions to limit the impact of "global" configuration options like PATH.

"Lame" or not, you'll have a far more stable system if you restrict such changes to smaller scopes.

blocks|key|2757893|text|在Mac+OS上设置PATH环境变量|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2757894|打开终端程序(默认情况下位于Applications/Utilities文件夹中)。运行以下命令|2757895|touch+~/.bash_profile;+open+~/.bash_profile|code-block|syntax|javascript|2757896|这将在默认文本编辑器中打开该文件。|2757897|Android+SDK+示例：|offset|length|style|BOLD|2757898|您需要将路径添加到Android+SDK平台-工具和工具目录。在我的示例中，我将使用"/Development/android-+SDK+-macosx“作为SDK的安装目录。添加以下行：|2757899|export+PATH=${PATH}:/Development/android-sdk-macosx/platform-tools:/Development/android-sdk-macosx/tools|2757900|保存文件并退出文本编辑器。执行.bash_profile以更新路径：|2757901|source+~/.bash_profile|2757902|现在，每次您打开终端程序时，您的路径都将包含Android+SDK。|2757903|entityMap^0|0|0|0|0|C|3|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|14|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|15|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|16|8|@$M|17|N|18|O|P]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|19|8|@]|9|@]|A|$]]|$1|S|3|T|5|F|7|1A|8|@]|9|@]|A|$G|H]]|$1|U|3|V|5|6|7|1B|8|@]|9|@]|A|$]]|$1|W|3|X|5|F|7|1C|8|@]|9|@]|A|$G|H]]|$1|Y|3|Z|5|6|7|1D|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|11|$]]

<h2>Set up your PATH environment variable on Mac OS</h2>

Open the Terminal program (this is in your Applications/Utilities folder by default). Run the following command

<pre><code>touch ~/.bash_profile; open ~/.bash_profile
</code></pre>

This will open the file in the your default text editor.

For Android SDK as example:

You need to add the path to your Android SDK platform-tools and tools directory. In my example I will use "/Development/android-sdk-macosx" as the directory the SDK is installed in. Add the following line:

<pre><code>export PATH=${PATH}:/Development/android-sdk-macosx/platform-tools:/Development/android-sdk-macosx/tools
</code></pre>

Save the file and quit the text editor. Execute your .bash_profile to update your PATH:

<pre><code>source ~/.bash_profile
</code></pre>

Now every time you open the Terminal program your PATH will include the Android SDK.

blocks|key|57685|text|这很简单。编辑文件.profile+(vi、nano、Sublime+Text或其他文本编辑器)文件。您可以在~/目录(用户目录)中找到它，并进行如下设置：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|57686|export+MY_VAR=[your+value+here]|code-block|syntax|javascript|57687|Java+home示例：|57688|export+JAVA_HOME=/Library/Java/JavaVirtualMachines/current|57689|保存后返回终端。|57690|您可以使用以下命令重新加载它：|57691|source+.profile|57692|或者关闭并打开您的终端窗口。|57693|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/GNU_nano|1|http://en.wikipedia.org/wiki/Sublime_Text^0|9|8|1J|2|M|4|0|R|C|1|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@$9|17|A|18|B|C]|$9|19|A|1A|B|C]]|D|@$9|1B|A|1C|1|1D]|$9|1E|A|1F|1|1G]]|E|$]]|$1|F|3|G|5|H|7|1H|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|1I|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|1J|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|1K|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1L|8|@]|D|@]|E|$]]|$1|S|3|T|5|H|7|1M|8|@]|D|@]|E|$I|J]]|$1|U|3|V|5|6|7|1N|8|@]|D|@]|E|$]]|$1|W|3|-4|5|6|7|1O|8|@]|D|@]|E|$]]]|X|$Y|$5|Z|10|11|E|$12|13]]|14|$5|Z|10|11|E|$12|15]]]]

It's quite simple. Edit file <code>.profile</code> (vi, <a href="https://en.wikipedia.org/wiki/GNU_nano" rel="nofollow noreferrer">nano</a>, <a href="http://en.wikipedia.org/wiki/Sublime_Text" rel="nofollow noreferrer">Sublime Text</a> or other text editor) file. You can found it at the <code>~/</code> directory (user directory) and set like this:

<pre><code>export MY_VAR=[your value here]
</code></pre>

Example with Java home:

<pre><code>export JAVA_HOME=/Library/Java/JavaVirtualMachines/current
</code></pre>

Save it and return to the terminal.

You can reload it with:

<pre><code>source .profile
</code></pre>

Or close and open your terminal window.

blocks|key|2546005|text|就像Matt+Curtis给出的答案一样，我通过启动set设置环境变量，但我将其封装在一个名为export的函数中，这样每当我在.bash_profile中导出一个像normal这样的变量时，它也是由启动set设置的。下面是我要做的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2546006|2546007|My+.bash_profile只有一行(这只是个人喜好)。|ordered-list-item|2546008|2546009|source+.bashrc|2546010|My+.bashrc具有以下内容：|unordered-list-item|2546011|2546012|函数导出(){内置导出"$@“if+[+${#@}+-eq+1+&&”${@/%5E=+/}“]]然后启动-eq+setenv+"${@%25%25=*}”"${@#*=}“elif+[[！"${@//%5E+/}”]]然后启动-eq+setenv+"${@}“”${@}“}+export+Bash+export+-f+|2546013|上面的代码将重载Bash内置的"+export“，并正常导出所有内容(您会注意到我用它导出了"export”！)然后通过launchctl为OS+X应用程序环境正确设置它们，无论您是否使用以下任何选项：|2546014|2546015|导出LC_CTYPE=en_US.UTF-8+#+~$+launchctl+getenv版本#+en_US.UTF-8+PATH="/usr/local/bin:${+PATH+}“导出路径#+~$+launchctl+getenv路径#+/usr/local/opt/coreutils/libexec/gnubin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin导出CXX_FLAGS=”-mmacosx-+LC_CTYPE+-min=10.9“#+~$+launchctl+getenv+CXX_FLAGS+#+-mmacosx-version-min=10.9|2546016|This方式我不必每次都将每个变量都发送给min=10.9，我可以按照我想要的方式设置我的.bash_profile+/+.bashrc。打开终端窗口，使用launchctl+getenv+myVar检查您感兴趣的环境变量，更改.bash_profile/.bashrc中的某些内容，关闭终端窗口并重新打开它，使用launchctl+getenv+myVar再次检查变量，瞧，它是changed.|offset|length|style|CODE|2546017|
|2546018|Again，，就像后山狮世界的其他解决方案一样，对于任何可用于应用程序的新环境变量，您需要在更改后启动或重新启动它们。|2546019|2546020|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|26|M|4D|M|0|0|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|18|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|19|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|1A|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|1B|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1D|8|@]|9|@]|A|$]]|$1|O|3|P|5|K|7|1E|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1G|8|@]|9|@]|A|$]]|$1|T|3|U|5|K|7|1H|8|@$V|1I|W|1J|X|Y]|$V|1K|W|1L|X|Y]]|9|@]|A|$]]|$1|Z|3|10|5|6|7|1M|8|@]|9|@]|A|$]]|$1|11|3|12|5|K|7|1N|8|@]|9|@]|A|$]]|$1|13|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]|$1|14|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]]|15|$]]

Much like the answer Matt Curtis gave, I set environment variables via launchctl, but I wrap it in a function called export, so that whenever I export a variable like normal in my .bash_profile, it is also set by launchctl. Here is what I do:

<ol>
<li>My .bash_profile consists solely of one line, (This is just personal preference.)

<pre><code>source .bashrc
</code></pre></li>
<li>My .bashrc has this:

<pre><code>function export()
{
 builtin export "$@"
 if [[ ${#@} -eq 1 &amp;&amp; "${@//[^=]/}" ]]
 then
 launchctl setenv "${@%%=*}" "${@#*=}"
 elif [[ ! "${@//[^ ]/}" ]]
 then
 launchctl setenv "${@}" "${!@}"
 fi
}

export -f export
</code></pre></li>
<li>The above will overload the Bash builtin "export" and will export everything normally (you'll notice I export "export" with it!), then properly set them for OS X app environments via launchctl, whether you use any of the following:

<pre><code>export LC_CTYPE=en_US.UTF-8
# ~$ launchctl getenv LC_CTYPE
# en_US.UTF-8
PATH="/usr/local/bin:${PATH}"
PATH="/usr/local/opt/coreutils/libexec/gnubin:${PATH}"
export PATH
# ~$ launchctl getenv PATH
# /usr/local/opt/coreutils/libexec/gnubin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin
export CXX_FLAGS="-mmacosx-version-min=10.9"
# ~$ launchctl getenv CXX_FLAGS
# -mmacosx-version-min=10.9
</code></pre></li>
<li>This way I don't have to send every variable to launchctl every time, and I can just have my .bash_profile / .bashrc set up the way I want. Open a terminal window, check out your environment variables you're interested in with <code>launchctl getenv myVar</code>, change something in your .bash_profile/.bashrc, close the terminal window and re-open it, check the variable again with launchctl, and voilá, it's changed.</li>
<li>Again, like the other solutions for the post-Mountain Lion world, for any new environment variables to be available for apps, you need to launch or re-launch them after the change.</li>
</ol>

blocks|key|56806|text|我只是简单而快速地做了这件事。首先从终端创建一个~/.bash_profile：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|56807|touch+.bash_profile|code-block|syntax|javascript|56808|然后|56809|open+-a+TextEdit.app+.bash_profile|56810|添加|56811|export+TOMCAT_HOME=/Library/Tomcat/Home|56812|保存文档，你就完成了。|56813|entityMap^0|O|F|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|Z|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|10|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|11|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|12|8|@]|D|@]|E|$]]|$1|Q|3|R|5|H|7|13|8|@]|D|@]|E|$I|J]]|$1|S|3|T|5|6|7|14|8|@]|D|@]|E|$]]|$1|U|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|V|$]]

Just did this really easy and quick. First create a ~/.bash_profile from terminal:

<pre><code>touch .bash_profile
</code></pre>

then

<pre><code>open -a TextEdit.app .bash_profile
</code></pre>

add

<pre><code>export TOMCAT_HOME=/Library/Tomcat/Home
</code></pre>

save documement and you are done.

blocks|key|57012|text|要简明扼要地说明每个文件的用途|type|unstyled|depth|inlineStyleRanges|entityRanges|data|57013|57014|~/.profile是每次Bash的源码。launched|unordered-list-item|offset|length|style|CODE|57015|~/.bashrc是“传统”用于Terminal.app环境的所有导出语句的位置。set|57016|/etc/paths是Mac中的主文件，其中包含用于构建所有文件的默认路径列表。users|57017|/etc/paths.d/环境变量包含包含附加搜索路径的文件|57018|57019|非终端程序不会继承终端所继承的系统范围的PATH和MANPATH变量！要为特定用户启动的所有进程设置环境，从而使环境变量对Mac应用程序可用，必须在~/.MacOSX/environment.plist+(Apple+Technical+Q&A+QA1067)中定义这些变量|57020|使用以下命令行将您的environment.plist与/etc/paths同步|57021|defaults+write+$HOME/.MacOSX/environment+PATH+"$(tr+'\n'+':'+</etc/paths)"|code-block|syntax|javascript|57022|entityMap^0|0|0|0|A|0|0|9|0|0|A|0|0|D|0|0|22|R|0|A|H|S|A|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|13|8|@$F|14|G|15|H|I]]|9|@]|A|$]]|$1|J|3|K|5|E|7|16|8|@$F|17|G|18|H|I]]|9|@]|A|$]]|$1|L|3|M|5|E|7|19|8|@$F|1A|G|1B|H|I]]|9|@]|A|$]]|$1|N|3|O|5|E|7|1C|8|@$F|1D|G|1E|H|I]]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1F|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1G|8|@$F|1H|G|1I|H|I]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1J|8|@$F|1K|G|1L|H|I]|$F|1M|G|1N|H|I]]|9|@]|A|$]]|$1|U|3|V|5|W|7|1O|8|@]|9|@]|A|$X|Y]]|$1|Z|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]]|10|$]]

To be concise and clear about what each file is intended for

<ul>
<li><code>~/.profile</code> is sourced every time Terminal.app is launched</li>
<li><code>~/.bashrc</code> is where "traditionally" all the export statements for Bash environment are set</li>
<li><code>/etc/paths</code> is the main file in Mac OS that contains the list of default paths for building the PATH environment variable for all users</li>
<li><code>/etc/paths.d/</code> contains files that hold additional search paths</li>
</ul>

Non-terminal programs don't inherit the system wide PATH and MANPATH variables that your terminal does! To set environment for all processes launched by a specific user, thus making environment variables available to Mac OS X GUI applications, those variables must be defined in your <code>~/.MacOSX/environment.plist</code> (Apple Technical Q&amp;A QA1067)

Use the following command line to synchronize your <code>environment.plist</code> with <code>/etc/paths</code>:

<pre><code>defaults write $HOME/.MacOSX/environment PATH "$(tr '\n' ':' &lt;/etc/paths)"
</code></pre>

blocks|key|56829|text|这里有两种类型的shell。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|56830|56831|非登录:每次启动Bash+|unordered-list-item|56832|的新副本时都会重新加载.profile登录:只有当您登录或显式告诉Bash加载它并将其用作登录shell时，才会加载该shell。|56833|56834|这里需要注意的是，使用Bash时，文件.bashrc只能由交互且非登录的shell读取，您会发现人们经常在.bash_profile中加载.bashrc以克服这一限制。|offset|length|style|CODE|56835|现在你已经有了基本的理解，让我们来看看我是如何建议你设置它的。|56836|56837|.profile:将其创建为不存在。如果不存在，请将路径设置放入there.|56838|.bashrc:+create。如果不存在，请将所有别名和自定义方法放入there.|56839|.bash_profile:+create中。将以下内容放入其中。|56840|56841|.bash_file：|56842|#!/bin/bash
source+~/.profile+#+Get+the+PATH+settings
source+~/.bashrc++#+Get+Aliases+and+Functions
#|code-block|syntax|javascript|56843|entityMap^0|0|0|0|0|0|J|7|1H|D|1X|7|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|17|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|18|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|19|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|1A|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|1C|8|@$K|1D|L|1E|M|N]|$K|1F|L|1G|M|N]|$K|1H|L|1I|M|N]]|9|@]|A|$]]|$1|O|3|P|5|6|7|1J|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]|$1|R|3|S|5|E|7|1L|8|@]|9|@]|A|$]]|$1|T|3|U|5|E|7|1M|8|@]|9|@]|A|$]]|$1|V|3|W|5|E|7|1N|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1P|8|@]|9|@]|A|$]]|$1|10|3|11|5|12|7|1Q|8|@]|9|@]|A|$13|14]]|$1|15|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]]|16|$]]

There are two type of shells at play here.

<ul>
<li>Non-login: .bashrc is reloaded every time you start a new copy of Bash</li>
<li>Login: The .profile is loaded only when you either login, or explicitly tell Bash to load it and use it as a login shell.</li>
</ul>

It's important to understand here that with Bash, file <code>.bashrc</code> is only read by a shell that's both interactive and non-login, and you will find that people often load <code>.bashrc</code> in <code>.bash_profile</code> to overcome this limitation.

Now that you have the basic understanding, let’s move on to how I would advice you to set it up.

<ul>
<li>.profile: create it non-existing. Put your PATH setup in there.</li>
<li>.bashrc: create if non-existing. Put all your aliases and custom methods in there.</li>
<li>.bash_profile: create if non-existing. Put the following in there.</li>
</ul>

.bash_file:

<pre><code>#!/bin/bash
source ~/.profile # Get the PATH settings
source ~/.bashrc # Get Aliases and Functions
#
</code></pre>

blocks|key|56845|text|登录Shell|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|56846|/etc/profile|code-block|syntax|javascript|56847|外壳程序首先执行文件/etc/profile中的命令。具有root权限的用户可以设置此文件，为运行Bash的用户建立系统范围的默认特征。|CODE|56848|.bash_profile
.bash_login
.profile|56849|接下来，shell按照这个顺序查找~/.bash_profile、~/.bash_login和~/.profile+(~/是您的主目录的缩写)，执行它找到的第一个文件中的命令。您可以将命令放入其中一个文件中，以覆盖在/etc/profile中设置的默认值。在虚拟终端上运行的shell不会执行这些文件中的命令。|56850|.bash_logout|56851|当您注销时，bash将执行~/.bash_logout文件中的命令。此文件通常包含会话后清理的命令，例如删除临时文件的命令。|56852|交互式非登录Shell|56853|/etc/bashrc|56854|尽管不是由/etc/bashrc直接调用，但许多~/.bashrc文件都会调用bash。此设置允许使用root权限的用户为非登录bash+shell建立系统范围的默认特征。|56855|.bashrc|56856|交互式非登录shell执行~/.bashrc文件中的命令。通常，登录shell的启动文件会运行此文件，因此登录shell和非登录shell都会运行.bashrc中的命令。|56857|由于可能会多次执行+.bash_profile+中的命令，并且子.bash_profile继承导出的变量，因此最好将添加到+subshells+文件中的现有变量的命令放入文件中。|56858|entityMap^0|0|7|0|0|A|C|0|0|H|F|X|D|1B|A|30|C|0|0|D|E|0|0|B|0|0|5|B|O|9|0|0|D|9|21|7|0|0|9|A|D|O|11|20|H|A|D|W|D|0^^$0|@$1|2|3|4|5|6|7|19|8|@$9|1A|A|1B|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|1C|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|1D|8|@$9|1E|A|1F|B|M]]|D|@]|E|$]]|$1|N|3|O|5|H|7|1G|8|@]|D|@]|E|$I|J]]|$1|P|3|Q|5|6|7|1H|8|@$9|1I|A|1J|B|M]|$9|1K|A|1L|B|M]|$9|1M|A|1N|B|M]|$9|1O|A|1P|B|M]]|D|@]|E|$]]|$1|R|3|S|5|H|7|1Q|8|@]|D|@]|E|$I|J]]|$1|T|3|U|5|6|7|1R|8|@$9|1S|A|1T|B|M]]|D|@]|E|$]]|$1|V|3|W|5|6|7|1U|8|@$9|1V|A|1W|B|C]]|D|@]|E|$]]|$1|X|3|Y|5|H|7|1X|8|@]|D|@]|E|$I|J]]|$1|Z|3|10|5|6|7|1Y|8|@$9|1Z|A|20|B|M]|$9|21|A|22|B|M]]|D|@]|E|$]]|$1|11|3|12|5|H|7|23|8|@]|D|@]|E|$I|J]]|$1|13|3|14|5|6|7|24|8|@$9|25|A|26|B|M]|$9|27|A|28|B|M]]|D|@]|E|$]]|$1|15|3|16|5|6|7|29|8|@$9|2A|A|2B|B|C]|$9|2C|A|2D|B|C]|$9|2E|A|2F|B|C]|$9|2G|A|2H|B|C]|$9|2I|A|2J|B|M]|$9|2K|A|2L|B|M]]|D|@]|E|$]]|$1|17|3|-4|5|6|7|2M|8|@]|D|@]|E|$]]]|18|$]]

Login Shells

<pre><code>/etc/profile
</code></pre>

The shell first executes the commands in file <code>/etc/profile</code>. A user working with root privileges can set up this file to establish systemwide default characteristics for users running Bash.

<pre><code>.bash_profile
.bash_login
.profile
</code></pre>

Next the shell looks for <code>~/.bash_profile</code>, <code>~/.bash_login</code>, and <code>~/.profile</code> (~/ is short- hand for your home directory), in that order, executing the commands in the first of these files it finds. You can put commands in one of these files to override the defaults set in <code>/etc/profile</code>. A shell running on a virtual terminal does not execute commands in these files.

<pre><code>.bash_logout
</code></pre>

When you log out, bash executes commands in the <code>~/.bash_logout</code> file. This file often holds commands that clean up after a session, such as those that remove temporary files.

Interactive Nonlogin Shells

<pre><code>/etc/bashrc
</code></pre>

Although not called by bash directly, many <code>~/.bashrc</code> files call <code>/etc/bashrc</code>. This setup allows a user working with root privileges to establish systemwide default characteristics for nonlogin bash shells.

<pre><code>.bashrc
</code></pre>

An interactive nonlogin shell executes commands in the <code>~/.bashrc</code> file. Typically a startup file for a login shell, such as <code>.bash_profile</code>, runs this file, so both login and nonlogin shells run the commands in <code>.bashrc</code>.

Because commands in <code>.bashrc</code> may be executed many times, and because subshells inherit exported variables, it is a good idea to put commands that add to existing variables in the <code>.bash_profile</code> file.

blocks|key|2758019|text|从单一来源同时使用命令行和图形用户界面应用程序的解决方案(适用于Mac OS X+v10.10+(Yosemite)和Mac OS X+v10.11+(El+Capitan))|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2758020|让我们假设您的~/.bash_profile中有如下代码片段所示的环境变量定义：|style|CODE|2758021|export+JAVA_HOME="$(/usr/libexec/java_home+-v+1.8)"
export+GOPATH="$HOME/go"
export+PATH="$PATH:/usr/local/opt/go/libexec/bin:$GOPATH/bin"
export+PATH="/usr/local/opt/coreutils/libexec/gnubin:$PATH"
export+MANPATH="/usr/local/opt/coreutils/libexec/gnuman:$MANPATH"|code-block|syntax|javascript|2758022|我们需要一个启动代理，它将在每次登录时运行，并随时按需加载这些变量到用户会话。我们还需要一个shell脚本来解析这些定义，并构建要由代理执行的必要命令。|2758023|在~/Library/LaunchAgents/目录下创建一个带有plist后缀的文件(例如命名为osx-env-sync.plist)，内容如下：|2758024|<?xml+version="1.0"+encoding="UTF-8"?>
<!DOCTYPE+plist+PUBLIC+"-//Apple//DTD+PLIST+1.0//EN"+"http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist+version="1.0">
<dict>
++<key>Label</key>
++<string>osx-env-sync</string>
++<key>ProgramArguments</key>
++<array>
++++<string>bash</string>
++++<string>-l</string>
++++<string>-c</string>
++++<string>
++++++$HOME/.osx-env-sync.sh
++++</string>
++</array>
++<key>RunAtLoad</key>
++<true/>
</dict>
</plist>|2758025|在这里，-l参数至关重要；它对于使用登录shell执行shell脚本是必要的，以便在执行此脚本之前首先获取~/.bash_profile。|BOLD|2758026|现在，来看看shell脚本。在~/.osx-env-sync.sh上创建，包含以下内容：|2758027|grep+export+$HOME/.bash_profile+%7C+while+IFS='+='+read+ignoreexport+envvar+ignorevalue;+do
++launchctl+setenv+"${envvar}"+"${!envvar}"
done|2758028|确保shell脚本是可执行的：|2758029|chmod+%2Bx+~/.osx-env-sync.sh|2758030|现在，加载当前会话的启动代理：|2758031|launchctl+load+~/Library/LaunchAgents/osx-env-sync.plist|2758032|(重新)启动GUI应用程序并验证它是否可以读取环境变量。|2758033|设置是持久的。它将在重新启动和重新登录后存活下来。|2758034|在初始设置之后(您刚才这样做了)，如果您想再次将~/.bash_profile中的任何更改反映到整个环境中，重新运行launchctl+load+...命令将不会执行您想要的操作；相反，您将收到如下所示的警告：|2758035|<$HOME>/Library/LaunchAgents/osx-env-sync.plist:+Operation+already+in+progress|2758036|要在不进行注销/登录过程的情况下重新加载环境变量，请执行以下操作：|2758037|launchctl+unload+~/Library/LaunchAgents/osx-env-sync.plist
launchctl+load+~/Library/LaunchAgents/osx-env-sync.plist|2758038|最后，确保重新启动已经在运行的应用程序(包括Terminal.app)，让它们知道这些更改。|2758039|我还将这里的代码和解释推到了一个GitHub项目中：osx-env-sync。|2758040|我希望这将是最终的解决方案，至少对于最新版本的OS-X+(Yosemite+&+El+Capitan)来说是这样。|2758041|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/OS_X_Yosemite|1|https://en.wikipedia.org/wiki/OS_X_El_Capitan|2|https://github.com/ersiner/osx-env-sync^0|W|F|0|1N|F|1|0|7|F|0|0|0|1|N|X|5|1D|I|0|0|4|2|1H|F|I|7|0|F|I|0|0|0|0|0|0|0|0|O|F|1M|I|0|0|26|0|0|0|0|Q|C|2|0|0^^$0|@$1|2|3|4|5|6|7|21|8|@]|9|@$A|22|B|23|1|24]|$A|25|B|26|1|27]]|C|$]]|$1|D|3|E|5|6|7|28|8|@$A|29|B|2A|F|G]]|9|@]|C|$]]|$1|H|3|I|5|J|7|2B|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|2C|8|@]|9|@]|C|$]]|$1|O|3|P|5|6|7|2D|8|@$A|2E|B|2F|F|G]|$A|2G|B|2H|F|G]|$A|2I|B|2J|F|G]]|9|@]|C|$]]|$1|Q|3|R|5|J|7|2K|8|@]|9|@]|C|$K|L]]|$1|S|3|T|5|6|7|2L|8|@$A|2M|B|2N|F|G]|$A|2O|B|2P|F|G]|$A|2Q|B|2R|F|U]]|9|@]|C|$]]|$1|V|3|W|5|6|7|2S|8|@$A|2T|B|2U|F|G]]|9|@]|C|$]]|$1|X|3|Y|5|J|7|2V|8|@]|9|@]|C|$K|L]]|$1|Z|3|10|5|6|7|2W|8|@]|9|@]|C|$]]|$1|11|3|12|5|J|7|2X|8|@]|9|@]|C|$K|L]]|$1|13|3|14|5|6|7|2Y|8|@]|9|@]|C|$]]|$1|15|3|16|5|J|7|2Z|8|@]|9|@]|C|$K|L]]|$1|17|3|18|5|6|7|30|8|@]|9|@]|C|$]]|$1|19|3|1A|5|6|7|31|8|@]|9|@]|C|$]]|$1|1B|3|1C|5|6|7|32|8|@$A|33|B|34|F|G]|$A|35|B|36|F|G]]|9|@]|C|$]]|$1|1D|3|1E|5|6|7|37|8|@$A|38|B|39|F|G]]|9|@]|C|$]]|$1|1F|3|1G|5|6|7|3A|8|@]|9|@]|C|$]]|$1|1H|3|1I|5|J|7|3B|8|@]|9|@]|C|$K|L]]|$1|1J|3|1K|5|6|7|3C|8|@]|9|@]|C|$]]|$1|1L|3|1M|5|6|7|3D|8|@]|9|@$A|3E|B|3F|1|3G]]|C|$]]|$1|1N|3|1O|5|6|7|3H|8|@]|9|@]|C|$]]|$1|1P|3|-4|5|6|7|3I|8|@]|9|@]|C|$]]]|1Q|$1R|$5|1S|1T|1U|C|$1V|1W]]|1X|$5|1S|1T|1U|C|$1V|1Y]]|1Z|$5|1S|1T|1U|C|$1V|20]]]]

<h1>Solution for both command line and GUI applications from a single source (works with <a href="https://en.wikipedia.org/wiki/OS_X_Yosemite" rel="noreferrer">Mac OS X v10.10</a> (Yosemite) and <a href="https://en.wikipedia.org/wiki/OS_X_El_Capitan" rel="noreferrer">Mac OS X v10.11</a> (El Capitan))</h1>
Let's assume you have environment variable definitions in your <code>~/.bash_profile</code> like in the following snippet:
<pre><code>export JAVA_HOME=&quot;$(/usr/libexec/java_home -v 1.8)&quot;
export GOPATH=&quot;$HOME/go&quot;
export PATH=&quot;$PATH:/usr/local/opt/go/libexec/bin:$GOPATH/bin&quot;
export PATH=&quot;/usr/local/opt/coreutils/libexec/gnubin:$PATH&quot;
export MANPATH=&quot;/usr/local/opt/coreutils/libexec/gnuman:$MANPATH&quot;
</code></pre>
We need a Launch Agent which will run on each login and anytime on demand which is going to load these variables to the user session. We'll also need a shell script to parse these definitions and build necessary commands to be executed by the agent.
Create a file with <code>plist</code> suffix (e.g. named <code>osx-env-sync.plist</code>) in <code>~/Library/LaunchAgents/</code> directory with the following contents:
<pre><code>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
&lt;!DOCTYPE plist PUBLIC &quot;-//Apple//DTD PLIST 1.0//EN&quot; &quot;http://www.apple.com/DTDs/PropertyList-1.0.dtd&quot;&gt;
&lt;plist version=&quot;1.0&quot;&gt;
&lt;dict&gt;
 &lt;key&gt;Label&lt;/key&gt;
 &lt;string&gt;osx-env-sync&lt;/string&gt;
 &lt;key&gt;ProgramArguments&lt;/key&gt;
 &lt;array&gt;
 &lt;string&gt;bash&lt;/string&gt;
 &lt;string&gt;-l&lt;/string&gt;
 &lt;string&gt;-c&lt;/string&gt;
 &lt;string&gt;
 $HOME/.osx-env-sync.sh
 &lt;/string&gt;
 &lt;/array&gt;
 &lt;key&gt;RunAtLoad&lt;/key&gt;
 &lt;true/&gt;
&lt;/dict&gt;
&lt;/plist&gt;
</code></pre>
<code>-l</code> parameter is critical here; it's necessary for executing the shell script with a login shell so that <code>~/.bash_profile</code> is sourced in the first place before this script is executed.
Now, the shell script. Create it at <code>~/.osx-env-sync.sh</code> with the following contents:
<pre><code>grep export $HOME/.bash_profile | while IFS=' =' read ignoreexport envvar ignorevalue; do
 launchctl setenv &quot;${envvar}&quot; &quot;${!envvar}&quot;
done
</code></pre>
Make sure the shell script is executable:
<pre><code>chmod +x ~/.osx-env-sync.sh
</code></pre>
Now, load the launch agent for current session:
<pre><code>launchctl load ~/Library/LaunchAgents/osx-env-sync.plist
</code></pre>
(Re)Launch a GUI application and verify that it can read the environment variables.
The setup is persistent. It will survive restarts and relogins.
After the initial setup (that you just did), if you want to reflect any changes in your <code>~/.bash_profile</code> to your whole environment again, rerunning the <code>launchctl load ...</code> command won't perform what you want; instead you'll get a warning like the following:
<code>&lt;$HOME&gt;/Library/LaunchAgents/osx-env-sync.plist: Operation already in progress</code>
In order to reload your environment variables without going through the logout/login process do the following:
<pre><code>launchctl unload ~/Library/LaunchAgents/osx-env-sync.plist
launchctl load ~/Library/LaunchAgents/osx-env-sync.plist
</code></pre>
Finally make sure that you relaunch your already running applications (including Terminal.app) to make them aware of the changes.
I've also pushed the code and explanations here to a GitHub project: <a href="https://github.com/ersiner/osx-env-sync" rel="noreferrer">osx-env-sync</a>.
I hope this is going to be the ultimate solution, at least for the latest versions of OS X (Yosemite &amp; El Capitan).

blocks|key|2758049|text|/etc/launchd.conf未用于OS:X+v10.10+(约塞米蒂)、OS:X+v10.11+(El+Capitan)、macOS+v10.12+(塞拉)或macOS+v10.13+(高塞拉)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2758050|2758051|从launchctl手册页：|offset|length|style|CODE|2758052|/etc/launchd.conf+file+is+no+longer+consulted+for+subcommands+to+run+during+early+boot+time;
this+functionality+was+removed+for+security+considerations.|code-block|syntax|javascript|2758053|此+answer中描述的方法适用于我(在重启后)：从Dock或Spotlight启动的应用程序继承我在~/Library/LaunchAgents/my.startup.plist中设置的环境变量。(在我的例子中，对于Sublime+Text插件，我需要将LANG设置为en_US.UTF-8。)|2758054|entityMap|0|LINK|mutability|MUTABLE|url|https://apple.stackexchange.com/questions/106355/setting-the-system-wide-path-environment-variable-in-mavericks^0|0|0|1|9|0|0|1F|13|3K|4|3R|B|1|7|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|C|3|D|5|6|7|Z|8|@$E|10|F|11|G|H]]|9|@]|A|$]]|$1|I|3|J|5|K|7|12|8|@]|9|@]|A|$L|M]]|$1|N|3|O|5|6|7|13|8|@$E|14|F|15|G|H]|$E|16|F|17|G|H]|$E|18|F|19|G|H]]|9|@$E|1A|F|1B|1|1C]]|A|$]]|$1|P|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W]]]]

/etc/launchd.conf is not used in OS&nbsp;X v10.10 (Yosemite), OS&nbsp;X v10.11 (El Capitan), macOS v10.12 (Sierra), or macOS v10.13 (High Sierra).

<hr>

From the <code>launchctl</code> man page:

<pre><code>/etc/launchd.conf file is no longer consulted for subcommands to run during early boot time;
this functionality was removed for security considerations.
</code></pre>

The method described in this <a href="https://apple.stackexchange.com/questions/106355/setting-the-system-wide-path-environment-variable-in-mavericks">Ask Different answer</a> works for me (after a reboot): applications launched from the Dock or from Spotlight inherit environment variables that I set in <code>~/Library/LaunchAgents/my.startup.plist</code>. (In my case, I needed to set <code>LANG</code>, to <code>en_US.UTF-8</code>, for a Sublime Text plugin.)

blocks|key|58576|text|iOS上的所有魔力只适用于对文件使用source，您可以在其中导出您的环境变量。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|58577|为例：|BOLD|58578|您可以像这样创建一个文件：|58579|export+bim=fooo
export+bom=bar|code-block|syntax|javascript|58580|将此文件另存为bimbom.env，然后执行source+./bimbom.ev。瞧，你得到了你的环境变量。|58581|使用以下命令检查它们：|58582|echo+$bim|58583|entityMap^0|I|6|0|0|3|0|0|0|7|A|M|I|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|10|8|@$9|11|A|12|B|H]]|D|@]|E|$]]|$1|I|3|J|5|6|7|13|8|@]|D|@]|E|$]]|$1|K|3|L|5|M|7|14|8|@]|D|@]|E|$N|O]]|$1|P|3|Q|5|6|7|15|8|@$9|16|A|17|B|C]|$9|18|A|19|B|C]]|D|@]|E|$]]|$1|R|3|S|5|6|7|1A|8|@]|D|@]|E|$]]|$1|T|3|U|5|M|7|1B|8|@]|D|@]|E|$N|O]]|$1|V|3|-4|5|6|7|1C|8|@]|D|@]|E|$]]]|W|$]]

All the magic on iOS only goes with using <code>source</code> with the file, where you export your environment variables.

For example:

You can create an file like this:

<pre><code>export bim=fooo
export bom=bar
</code></pre>

Save this file as <code>bimbom.env</code>, and do <code>source ./bimbom.ev</code>.
Voilá, you got your environment variables.

Check them with:

<pre><code>echo $bim
</code></pre>

blocks|key|2546132|text|我的个人实践是.bash_profile。我在那里添加路径并附加到Path变量，|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2546133|GOPATH=/usr/local/go/bin/
MYSQLPATH=/usr/local/opt/mysql@5.6/bin

PATH=$PATH:$GOPATH:$MYSQLPATH|code-block|syntax|javascript|2546134|然后我可以通过echo+$GOPATH，echo$MYSQLPATH或all+by+echo+$PATH创建单独的路径。|2546135|entityMap^0|7|D|0|0|7|C|K|E|16|A|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|N|$]]

My personal practice is <code>.bash_profile</code>. I'm adding paths there and append to Path variable,

<pre><code>GOPATH=/usr/local/go/bin/
MYSQLPATH=/usr/local/opt/mysql@5.6/bin

PATH=$PATH:$GOPATH:$MYSQLPATH
</code></pre>

After then I can have individual Path by <code>echo $GOPATH</code>, <code>echo$MYSQLPATH</code> or all by <code>echo $PATH</code>.

blocks|key|2758078|text|2022年2月(MacOs+12%2B)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2758079|此处的解决方案应在重新启动或应用程序重新启动后工作。|2758080|CLI|2758081|打开您选择的CLI配置文件。|2758082|用于~/.zshrc的|offset|length|style|CODE|2758083|打开zsh打开bash|unordered-list-item|2758084|2758085|添加(或替换)|2758086|export+varName=varValue+|code-block|syntax|javascript|2758087|(如果varValue中有空格-用"包装它)|2758088|确保重新启动命令行应用程序。|2758089|图形用户界面|2758090|完成CLI步骤。确保GUI应用程序已关闭。从命令行打开GUI应用程序。例如：|2758091|open+/Applications/Sourcetree.app|2758092|(您还可以在.zshrc中为此命令设置别名)|2758093|原则|2758094|2758095|Mac没有为所有contexts.|2758096|Avoid设置环境变量的配置选项，可以更改您的用户配置文件之外的任何内容。|2758097|2758098|不再起作用了|2758099|2758100|launchctl+config+user+varName+varVal+(带有plist后缀|2758101|的MacOSplist文件|2758102|entityMap^0|0|0|0|0|2|8|0|0|0|0|0|3|8|H|1|0|0|0|0|0|6|6|0|0|0|0|0|0|0|0|0|10|14|5|0|6|5|0^^$0|@$1|2|3|4|5|6|7|1R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1T|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|1U|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|1V|8|@$J|1W|K|1X|L|M]]|9|@]|A|$]]|$1|N|3|O|5|P|7|1Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|20|8|@]|9|@]|A|$]]|$1|T|3|U|5|V|7|21|8|@]|9|@]|A|$W|X]]|$1|Y|3|Z|5|6|7|22|8|@$J|23|K|24|L|M]|$J|25|K|26|L|M]]|9|@]|A|$]]|$1|10|3|11|5|6|7|27|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|28|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|29|8|@]|9|@]|A|$]]|$1|16|3|17|5|V|7|2A|8|@]|9|@]|A|$W|X]]|$1|18|3|19|5|6|7|2B|8|@$J|2C|K|2D|L|M]]|9|@]|A|$]]|$1|1A|3|1B|5|6|7|2E|8|@]|9|@]|A|$]]|$1|1C|3|-4|5|6|7|2F|8|@]|9|@]|A|$]]|$1|1D|3|1E|5|P|7|2G|8|@]|9|@]|A|$]]|$1|1F|3|1G|5|P|7|2H|8|@]|9|@]|A|$]]|$1|1H|3|-4|5|6|7|2I|8|@]|9|@]|A|$]]|$1|1I|3|1J|5|6|7|2J|8|@]|9|@]|A|$]]|$1|1K|3|-4|5|6|7|2K|8|@]|9|@]|A|$]]|$1|1L|3|1M|5|P|7|2L|8|@$J|2M|K|2N|L|M]|$J|2O|K|2P|L|M]]|9|@]|A|$]]|$1|1N|3|1O|5|6|7|2Q|8|@$J|2R|K|2S|L|M]]|9|@]|A|$]]|$1|1P|3|-4|5|6|7|2T|8|@]|9|@]|A|$]]]|1Q|$]]

<h1>Feb 2022 (MacOs 12+)</h1>
Solutions here should work after reboot or application restart.
<h2>CLI</h2>
Open your CLI of choice config file.
<ul>
<li>For bash open <code>~/.bash_profile</code></li>
<li>For zsh open <code>~/.zshrc</code></li>
</ul>
add (or replace)
<pre><code>export varName=varValue 
</code></pre>
(if <code>varValue</code> has spaces in it - wrap it in <code>&quot;</code>)
Make sure to restart command line app.
<h2>GUI</h2>
Complete the CLI step.
Make sure GUI app is closed.
Open GUI app from the command line. For example:
<pre><code>open /Applications/Sourcetree.app
</code></pre>
(you can also alias this command in the <code>.zshrc</code>)
<h3>Principles</h3>
<ul>
<li>Mac does not have a configuration options that sets environment variable for all contexts.</li>
<li>Avoid changing anything outside your user profile.</li>
</ul>
<h3>Doesn't work anymore</h3>
<ul>
<li><code>launchctl config user varName varVal</code> (MacOS 12.1+)</li>
<li>Editing <code>/etc/launchd.conf</code></li>
<li>xml file with <code>plist</code> suffix</li>
</ul>

What is the proper way to modify environment variables like PATH in OS&nbsp;X?

I've looked on Google a little bit and found three different files to edit:

<ul>
<li>/etc/paths</li>
<li>~/.profile</li>
<li>~/.tcshrc</li>
</ul>

I don't even have some of these files, and I'm pretty sure that .tcshrc is wrong, since OS&nbsp;X uses bash now. Where are these variables, especially PATH, defined?

I'm running <a href="http://en.wikipedia.org/wiki/Mac_OS_X_Leopard" rel="noreferrer">OS&nbsp;X&nbsp;v10.5</a> (Leopard).

Setting environment variables on OS X

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在OS-X中修改像PATH这样的环境变量的正确方法是什么？我在Google上看了一下，发现有三个不同的文件需要编辑：/etc/paths~/.profile~/.tcshrc我甚至没有其中的一些文件，我非常确定.tcshrc是错的，因为OS-X现在使用bash。这些变量是在哪里定义的，尤其是PATH？我正在运行 (豹)...

问在OS X上设置环境变量
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在OS X上设置环境变量EN