blocks|key|2072993|text|使用dirname+"$0"|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2072994|#!/bin/bash
echo+"The+script+you+are+running+has+basename+`basename+"$0"`,+dirname+`dirname+"$0"`"
echo+"The+present+working+directory+is+`pwd`"|code-block|syntax|javascript|2072995|如果不是从脚本所在的目录运行脚本，则仅使用pwd将不起作用。|2072996|[matt@server1+~]$+pwd
/home/matt
[matt@server1+~]$+./test2.sh
The+script+you+are+running+has+basename+test2.sh,+dirname+.
The+present+working+directory+is+/home/matt
[matt@server1+~]$+cd+/tmp
[matt@server1+tmp]$+~/test2.sh
The+script+you+are+running+has+basename+test2.sh,+dirname+/home/matt
The+present+working+directory+is+/tmp|2072997|entityMap^0|2|C|0|0|L|3|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|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|M|3|N|5|H|7|X|8|@]|D|@]|E|$I|J]]|$1|O|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|P|$]]

Use <code>dirname &quot;$0&quot;</code>:
<pre><code>#!/bin/bash
echo &quot;The script you are running has basename `basename &quot;$0&quot;`, dirname `dirname &quot;$0&quot;`&quot;
echo &quot;The present working directory is `pwd`&quot;
</code></pre>
Using <code>pwd</code> alone will not work if you are not running the script from the directory it is contained in.
<pre><code>[matt@server1 ~]$ pwd
/home/matt
[matt@server1 ~]$ ./test2.sh
The script you are running has basename test2.sh, dirname .
The present working directory is /home/matt
[matt@server1 ~]$ cd /tmp
[matt@server1 tmp]$ ~/test2.sh
The script you are running has basename test2.sh, dirname /home/matt
The present working directory is /tmp
</code></pre>

blocks|key|2073097|text|您可以使用$BASH_SOURCE|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2073098|#!/bin/bash

scriptdir=`dirname+"$BASH_SOURCE"`|code-block|syntax|javascript|2073099|请注意，您需要使用#!/bin/bash而不是#!/bin/sh，因为它是一个Bash扩展。|2073100|entityMap^0|5|C|0|0|9|B|N|9|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]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|N|$]]

You can use <code>$BASH_SOURCE</code>:

<pre><code>#!/bin/bash

scriptdir=`dirname "$BASH_SOURCE"`
</code></pre>

Note that you need to use <code>#!/bin/bash</code> and not <code>#!/bin/sh</code> since it's a Bash extension.

blocks|key|1859655|text|简短的回答：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1859656|`dirname+$0`|code-block|syntax|javascript|1859657|或(preferably)：|offset|length|1859658|$(dirname+"$0")|1859659|entityMap|0|LINK|mutability|MUTABLE|url|http://mywiki.wooledge.org/BashFAQ/082^0|0|0|2|A|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@$I|X|J|Y|1|Z]]|A|$]]|$1|K|3|L|5|D|7|10|8|@]|9|@]|A|$E|F]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

Short answer:

<pre><code>`dirname $0`
</code></pre>

or (<a href="http://mywiki.wooledge.org/BashFAQ/082" rel="noreferrer">preferably</a>):

<pre><code>$(dirname "$0")
</code></pre>

blocks|key|1861092|text|这应该可以做到：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1861093|DIR="$(dirname+"$(realpath+"$0")")"|code-block|syntax|javascript|1861094|这适用于路径中的符号链接和空格。|1861095|请参阅dirname和realpath的手册页。|offset|length|style|CODE|1861096|请添加有关如何支持MacOS的评论。很抱歉我可以核实一下。|1861097|entityMap^0|0|0|0|3|7|B|8|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|V|8|@$K|W|L|X|M|N]|$K|Y|L|Z|M|N]]|9|@]|A|$]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|R|$]]

This should do it:
<pre><code>DIR=&quot;$(dirname &quot;$(realpath &quot;$0&quot;)&quot;)&quot;
</code></pre>
This works with symlinks and spaces in path.
Please see the man pages for <code>dirname</code> and <code>realpath</code>.
Please add a comment on how to support MacOS. I'm sorry I can verify it.

blocks|key|1861492|text|下面是一个很容易记住的脚本：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1861493|DIR="$(dirname+"${BASH_SOURCE[0]}")"++#+Get+the+directory+name
DIR="$(realpath+"${DIR}")"++++#+Resolve+its+full+path+if+need+be|code-block|syntax|javascript|1861494|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Here is an easy-to-remember script:
<pre><code>DIR=&quot;$(dirname &quot;${BASH_SOURCE[0]}&quot;)&quot; # Get the directory name
DIR=&quot;$(realpath &quot;${DIR}&quot;)&quot; # Resolve its full path if need be
</code></pre>

blocks|key|2073301|text|pwd可用于查找当前工作目录，dirname可用于查找特定文件的目录(运行的命令为$0，因此dirname+$0应为您提供当前脚本的目录)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2073302|然而，dirname精确地给出了文件名的目录部分，它很可能是相对于当前工作目录的。如果您的脚本出于某种原因需要更改目录，那么dirname的输出将变得毫无意义。|2073303|我的建议如下：|2073304|#!/bin/bash

reldir=`dirname+$0`
cd+$reldir
directory=`pwd`

echo+"Directory+is+$directory"|code-block|syntax|javascript|2073305|这样，您得到的是绝对目录，而不是相对目录。|2073306|由于脚本将在单独的Bash实例中运行，因此不需要在以后恢复工作目录，但是如果您出于某种原因想要在脚本中更改回原来的目录，则可以在更改目录之前轻松地将pwd的值赋给变量，以备将来使用。|2073307|尽管只是|2073308|cd+`dirname+$0`|2073309|解决了问题中的特定场景，我发现拥有绝对路径通常更有用。|2073310|entityMap^0|0|3|F|7|15|2|1A|A|0|3|7|1Q|7|0|0|0|0|22|3|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@$9|11|A|12|B|C]|$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]]|D|@]|E|$]]|$1|H|3|I|5|6|7|1E|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|1F|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|1G|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1H|8|@$9|1I|A|1J|B|C]]|D|@]|E|$]]|$1|S|3|T|5|6|7|1K|8|@]|D|@]|E|$]]|$1|U|3|V|5|L|7|1L|8|@]|D|@]|E|$M|N]]|$1|W|3|X|5|6|7|1M|8|@]|D|@]|E|$]]|$1|Y|3|-4|5|6|7|1N|8|@]|D|@]|E|$]]]|Z|$]]

<code>pwd</code> can be used to find the current working directory, and <code>dirname</code> to find the directory of a particular file (command that was run, is <code>$0</code>, so <code>dirname $0</code> should give you the directory of the current script).
However, <code>dirname</code> gives precisely the directory portion of the filename, which more likely than not is going to be relative to the current working directory. If your script needs to change directory for some reason, then the output from <code>dirname</code> becomes meaningless.
I suggest the following:
<pre><code>#!/bin/bash

reldir=`dirname $0`
cd $reldir
directory=`pwd`

echo &quot;Directory is $directory&quot;
</code></pre>
This way, you get an absolute, rather than a relative directory.
Since the script will be run in a separate Bash instance, there isn't any need to restore the working directory afterwards, but if you do want to change back in your script for some reason, you can easily assign the value of <code>pwd</code> to a variable before you change directory, for future use.
Although just
<pre><code>cd `dirname $0`
</code></pre>
solves the specific scenario in the question, I find having the absolute path to more more useful generally.

blocks|key|2073182|text|我认为这并不像其他人所说的那么容易。pwd不起作用，因为当前目录不一定是包含脚本的目录。$0也不总是有这些信息。考虑以下三种调用脚本的方法：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2073183|./script

/usr/bin/script

script|code-block|syntax|javascript|2073184|在第一种和第三种方式中，$0没有完整的路径信息。在第二和第三种情况下，pwd不起作用。以第三种方式获取目录的唯一方法是遍历路径并找到具有正确匹配的文件。基本上，代码必须重做操作系统所做的事情。|2073185|要实现您的要求，一种方法是对/usr/share目录中的数据进行硬编码，并通过其完整路径引用它。数据无论如何都不应该在/usr/bin目录中，所以这可能是要做的事情。|2073186|entityMap^0|I|3|18|2|0|0|C|2|Z|3|0|E|A|1N|8|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|M|3|N|5|6|7|11|8|@$9|12|A|13|B|C]|$9|14|A|15|B|C]]|D|@]|E|$]]|$1|O|3|-4|5|6|7|16|8|@]|D|@]|E|$]]]|P|$]]

I don't think this is as easy as others have made it out to be. <code>pwd</code> doesn't work, as the current directory is not necessarily the directory with the script. <code>$0</code> doesn't always have the information either. Consider the following three ways to invoke a script:

<pre><code>./script

/usr/bin/script

script
</code></pre>

In the first and third ways <code>$0</code> doesn't have the full path information. In the second and third, <code>pwd</code> does not work. The only way to get the directory in the third way would be to run through the path and find the file with the correct match. Basically the code would have to redo what the OS does.

One way to do what you are asking would be to just hardcode the data in the <code>/usr/share</code> directory, and reference it by its full path. Data shoudn't be in the <code>/usr/bin</code> directory anyway, so this is probably the thing to do.

blocks|key|1860116|text|SCRIPT_DIR=$(+cd+${0%25/*}+&&+pwd+-P+)|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1860117|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>SCRIPT_DIR=$( cd ${0%/*} &amp;&amp; pwd -P )
</code></pre>

blocks|key|1860188|text|这将获取Mac OS X v10.6.6+(雪豹)上的当前工作目录：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1860189|DIR=$(cd+"$(dirname+"$0")";+pwd)|code-block|syntax|javascript|1860190|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Mac_OS_X_Snow_Leopard^0|4|G|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

This gets the current working directory on <a href="https://en.wikipedia.org/wiki/Mac_OS_X_Snow_Leopard" rel="nofollow noreferrer">Mac OS X v10.6.6</a> (Snow Leopard):
<pre><code>DIR=$(cd &quot;$(dirname &quot;$0&quot;)&quot;; pwd)
</code></pre>

blocks|key|2074072|text|$(dirname+"$(readlink+-f+"$BASH_SOURCE")")|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|2074073|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>$(dirname "$(readlink -f "$BASH_SOURCE")")
</code></pre>

blocks|key|1859483|text|这是特定于Linux的，但您可以使用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1859484|SELF=$(readlink+/proc/$$/fd/255)|code-block|syntax|javascript|1859485|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This is Linux specific, but you could use:

<pre><code>SELF=$(readlink /proc/$$/fd/255)
</code></pre>

blocks|key|1860376|text|下面是一个与POSIX兼容的一行代码：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1860377|SCRIPT_PATH=`dirname+"$0"`;+SCRIPT_PATH=`eval+"cd+\"$SCRIPT_PATH\"+&&+pwd"`

#+test
echo+$SCRIPT_PATH|code-block|syntax|javascript|1860378|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Here is a POSIX compliant one-liner:

<pre><code>SCRIPT_PATH=`dirname "$0"`; SCRIPT_PATH=`eval "cd \"$SCRIPT_PATH\" &amp;&amp; pwd"`

# test
echo $SCRIPT_PATH
</code></pre>

blocks|key|2075846|text|要做到这一点，最短最优雅的方法是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2075847|#!/bin/bash
DIRECTORY=$(cd+`dirname+$0`+&&+pwd)
echo+$DIRECTORY|code-block|syntax|javascript|2075848|这将在所有平台上工作，并且非常干净。|2075849|更多细节可以在"Which+directory+is+that+bash+script+in?“中找到。|offset|length|2075850|entityMap|0|LINK|mutability|MUTABLE|url|https://www.electrictoolbox.com/bash-script-directory/^0|0|0|0|8|13|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|X|8|@]|9|@$K|Y|L|Z|1|10]]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

The shortest and most elegant way to do this is:

<pre class="lang-sh prettyprint-override"><code>#!/bin/bash
DIRECTORY=$(cd `dirname $0` &amp;&amp; pwd)
echo $DIRECTORY
</code></pre>

This would work on all platforms and is super clean.

More details can be found in "<a href="https://www.electrictoolbox.com/bash-script-directory/" rel="noreferrer">Which directory is that bash script in?</a>".

blocks|key|1859333|text|#!/bin/sh
PRG="$0"

#+need+this+for+relative+symlinks
while+[+-h+"$PRG"+]+;+do
+++PRG=`readlink+"$PRG"`
done

scriptdir=`dirname+"$PRG"`|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1859334|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>#!/bin/sh
PRG="$0"

# need this for relative symlinks
while [ -h "$PRG" ] ; do
 PRG=`readlink "$PRG"`
done

scriptdir=`dirname "$PRG"`
</code></pre>

blocks|key|2073951|text|我尝试了所有这些方法，但都不起作用。其中一个非常接近，但它有一个很小的bug，严重破坏了它；他们忘记了用引号括起来。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2073952|另外，很多人认为你是在shell中运行脚本，所以当你打开一个新的脚本时，他们会忘记它默认在你的家里。|2073953|尝试此目录的大小：|2073954|/var/No+one/Thought/About+Spaces+Being/In+a+Directory/Name/And+Here's+your+file.text|code-block|syntax|javascript|2073955|无论您如何或在何处运行它，它都会正确运行：|2073956|#!/bin/bash
echo+"pwd:+`pwd`"
echo+"\$0:+$0"
echo+"basename:+`basename+"$0"`"
echo+"dirname:+`dirname+"$0"`"|2073957|因此，为了让它真正有用，下面是如何切换到运行脚本的目录：|2073958|cd+"`dirname+"$0"`"|2073959|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|Z|8|@]|9|@]|A|$I|J]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|R|5|H|7|11|8|@]|9|@]|A|$I|J]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

I tried all of these and none worked. One was very close, but it had a tiny bug that broke it badly; they forgot to wrap the path in quotation marks.
Also a lot of people assume you're running the script from a shell, so they forget when you open a new script it defaults to your home.
Try this directory on for size:
<pre><code>/var/No one/Thought/About Spaces Being/In a Directory/Name/And Here's your file.text
</code></pre>
This gets it right regardless how or where you run it:
<pre><code>#!/bin/bash
echo &quot;pwd: `pwd`&quot;
echo &quot;\$0: $0&quot;
echo &quot;basename: `basename &quot;$0&quot;`&quot;
echo &quot;dirname: `dirname &quot;$0&quot;`&quot;
</code></pre>
So to make it actually useful, here's how to change to the directory of the running script:
<pre><code>cd &quot;`dirname &quot;$0&quot;`&quot;
</code></pre>

blocks|key|1859999|text|这是对their+answer中指出的解决方案e-satis和3bcdnlklvc04a的轻微修订|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1860000|SCRIPT_DIR=''
pushd+"$(dirname+"$(readlink+-f+"$BASH_SOURCE")")"+>+/dev/null+&&+{
++++SCRIPT_DIR="$PWD"
++++popd+>+/dev/null
}|code-block|syntax|javascript|1860001|这应该仍然适用于他们列出的所有情况。|1860002|这将防止在pushd失败后出现popd。多亏了konsolebox。|style|CODE|1860003|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/59895/can-a-bash-script-tell-what-directory-its-in/179231#179231^0|3|C|0|0|0|0|5|5|F|4|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|F|7|10|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|11|8|@]|9|@]|C|$]]|$1|K|3|L|5|6|7|12|8|@$A|13|B|14|M|N]|$A|15|B|16|M|N]]|9|@]|C|$]]|$1|O|3|-4|5|6|7|17|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]]]

This is a slight revision to the solution e-satis and 3bcdnlklvc04a pointed out in <a href="https://stackoverflow.com/questions/59895/can-a-bash-script-tell-what-directory-its-in/179231#179231" title="their answer">their answer</a>:
<pre><code>SCRIPT_DIR=''
pushd &quot;$(dirname &quot;$(readlink -f &quot;$BASH_SOURCE&quot;)&quot;)&quot; &gt; /dev/null &amp;&amp; {
 SCRIPT_DIR=&quot;$PWD&quot;
 popd &gt; /dev/null
}
</code></pre>
This should still work in all the cases they listed.
This will prevent <code>popd</code> after a failed <code>pushd</code>. Thanks to konsolebox.

blocks|key|1860294|text|我会使用类似这样的东西：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1860295|#+Retrieve+the+full+pathname+of+the+called+script
scriptPath=$(which+$0)

#+Check+whether+the+path+is+a+link+or+not
if+[+-L+$scriptPath+];+then

++++#+It+is+a+link+then+retrieve+the+target+path+and+get+the+directory+name
++++sourceDir=$(dirname+$(readlink+-f+$scriptPath))

else

++++#+Otherwise+just+get+the+directory+name+of+the+script+path
++++sourceDir=$(dirname+$scriptPath)

fi|code-block|syntax|javascript|1860296|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I would use something like this:
<pre><code># Retrieve the full pathname of the called script
scriptPath=$(which $0)

# Check whether the path is a link or not
if [ -L $scriptPath ]; then

 # It is a link then retrieve the target path and get the directory name
 sourceDir=$(dirname $(readlink -f $scriptPath))

else

 # Otherwise just get the directory name of the script path
 sourceDir=$(dirname $scriptPath)

fi
</code></pre>

blocks|key|1860853|text|对于具有GNU+readlink的系统(例如，Linux)：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1860854|$(readlink+-f+"$(dirname+"$0")")|code-block|syntax|javascript|1860855|当$0包含脚本文件名时，不需要使用BASH_SOURCE。|1860856|entityMap^0|8|8|0|0|1|2|H|B|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]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|N|$]]

For systems having GNU coreutils <code>readlink</code> (for example, Linux):
<pre><code>$(readlink -f &quot;$(dirname &quot;$0&quot;)&quot;)
</code></pre>
There's no need to use <code>BASH_SOURCE</code> when <code>$0</code> contains the script filename.

blocks|key|2074153|text|尝试使用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2074154|real=$(realpath+"$(dirname+"$0")")|code-block|syntax|javascript|2074155|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Try using:
<pre><code>real=$(realpath &quot;$(dirname &quot;$0&quot;)&quot;)
</code></pre>

blocks|key|2074136|text|值得一提的是，$_是$0的替代方案。如果您正在运行来自Bash的脚本，则可以将接受的答案缩短为：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2074137|DIR="$(+dirname+"$_"+)"|code-block|syntax|javascript|2074138|请注意，这必须是脚本中的第一个语句。|2074139|entityMap|0|LINK|mutability|MUTABLE|url|http://www.gnu.org/s/bash/manual/bash.html#Environment^0|7|2|A|2|7|2|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@$9|Z|A|10|1|11]]|E|$]]|$1|F|3|G|5|H|7|12|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|13|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|14|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

<a href="http://www.gnu.org/s/bash/manual/bash.html#Environment" rel="nofollow noreferrer"><code>$_</code></a> is worth mentioning as an alternative to <code>$0</code>. If you're running a script from Bash, the accepted answer can be shortened to:

<pre><code>DIR="$( dirname "$_" )"
</code></pre>

Note that this has to be the first statement in your script.

blocks|key|2073478|text|这在Bash+3.2中有效：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2073479|path="$(+dirname+"$(+which+"$0"+)"+)"|code-block|syntax|javascript|2073480|如果您的$PATH中有一个~/bin目录，那么在此目录中就有A。它提供了脚本~/bin/lib/B。您知道所包含的脚本相对于lib子目录中原始脚本的位置，但不知道它相对于用户当前目录的位置。|offset|length|style|CODE|2073481|这可以通过以下方式解决(在A内部)：|2073482|source+"$(+dirname+"$(+which+"$0"+)"+)/lib/B"|2073483|用户在哪里或者他/她如何调用脚本都无关紧要。这将总是有效的。|2073484|entityMap^0|0|0|4|5|D|5|U|1|12|B|1Q|3|0|D|1|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@$I|X|J|Y|K|L]|$I|Z|J|10|K|L]|$I|11|J|12|K|L]|$I|13|J|14|K|L]|$I|15|J|16|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|17|8|@$I|18|J|19|K|L]]|9|@]|A|$]]|$1|O|3|P|5|D|7|1A|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|1B|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|T|$]]

This works in Bash 3.2:
<pre><code>path=&quot;$( dirname &quot;$( which &quot;$0&quot; )&quot; )&quot;
</code></pre>
If you have a <code>~/bin</code> directory in your <code>$PATH</code>, you have <code>A</code> inside this directory. It sources the script <code>~/bin/lib/B</code>. You know where the included script is relative to the original one, in the <code>lib</code> subdirectory, but not where it is relative to the user's current directory.
This is solved by the following (inside <code>A</code>):
<pre><code>source &quot;$( dirname &quot;$( which &quot;$0&quot; )&quot; )/lib/B&quot;
</code></pre>
It doesn't matter where the user is or how he/she calls the script. This will always work.

blocks|key|1861357|text|以下是获取脚本信息的简单方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1861358|文件夹和文件：|1861359|++++Script:+"/tmp/src+dir/test.sh"
++++Calling+folder:+"/tmp/src+dir/other"|code-block|syntax|javascript|1861360|使用以下命令：|1861361|++++echo+Script-Dir+:+`dirname+"$(realpath+$0)"`
++++echo+Script-Dir+:+$(+cd+${0%25/*}+&&+pwd+-P+)
++++echo+Script-Dir+:+$(dirname+"$(readlink+-f+"$0")")
++++echo
++++echo+Script-Name+:+`basename+"$(realpath+$0)"`
++++echo+Script-Name+:+`basename+$0`
++++echo
++++echo+Script-Dir-Relative+:+`dirname+"$BASH_SOURCE"`
++++echo+Script-Dir-Relative+:+`dirname+$0`
++++echo
++++echo+Calling-Dir+:+`pwd`|1861362|我得到了下面的输出：|1861363|+++++Script-Dir+:+/tmp/src+dir
+++++Script-Dir+:+/tmp/src+dir
+++++Script-Dir+:+/tmp/src+dir

+++++Script-Name+:+test.sh
+++++Script-Name+:+test.sh

+++++Script-Dir-Relative+:+..
+++++Script-Dir-Relative+:+..

+++++Calling-Dir+:+/tmp/src+dir/other|1861364|另请参阅：https://pastebin.com/J8KjxrPF|offset|length|1861365|entityMap|0|LINK|mutability|MUTABLE|url|https://pastebin.com/J8KjxrPF^0|0|0|0|0|0|0|0|5|T|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|F|7|16|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|17|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|18|8|@]|9|@]|A|$G|H]]|$1|Q|3|R|5|6|7|19|8|@]|9|@$S|1A|T|1B|1|1C]]|A|$]]|$1|U|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11]]]]

These are short ways to get script information:

Folders and files:

<pre><code> Script: "/tmp/src dir/test.sh"
 Calling folder: "/tmp/src dir/other"
</code></pre>

Using these commands:

<pre><code> echo Script-Dir : `dirname "$(realpath $0)"`
 echo Script-Dir : $( cd ${0%/*} &amp;&amp; pwd -P )
 echo Script-Dir : $(dirname "$(readlink -f "$0")")
 echo
 echo Script-Name : `basename "$(realpath $0)"`
 echo Script-Name : `basename $0`
 echo
 echo Script-Dir-Relative : `dirname "$BASH_SOURCE"`
 echo Script-Dir-Relative : `dirname $0`
 echo
 echo Calling-Dir : `pwd`
</code></pre>

And I got this output:

<pre><code> Script-Dir : /tmp/src dir
 Script-Dir : /tmp/src dir
 Script-Dir : /tmp/src dir

 Script-Name : test.sh
 Script-Name : test.sh

 Script-Dir-Relative : ..
 Script-Dir-Relative : ..

 Calling-Dir : /tmp/src dir/other
</code></pre>

Also see: <a href="https://pastebin.com/J8KjxrPF" rel="noreferrer">https://pastebin.com/J8KjxrPF</a>

blocks|key|1860799|text|我相信我已经找到这个了。我来晚了，但我想如果有人遇到这个话题，他们会很高兴来到这里的。评论应该解释：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1860800|#!/bin/sh+#+dash+bash+ksh+#+!zsh+(issues).+G.+Nixon,+12/2013.+Public+domain.

##+'linkread'+or+'fullpath'+or+(you+choose)+is+a+little+tool+to+recursively
##+dereference+symbolic+links+(ala+'readlink')+until+the+originating+file
##+is+found.+This+is+effectively+the+same+function+provided+in+stdlib.h+as
##+'realpath'+and+on+the+command+line+in+GNU+'readlink+-f'.

##+Neither+of+these+tools,+however,+are+particularly+accessible+on+the+many
##+systems+that+do+not+have+the+GNU+implementation+of+readlink,+nor+ship
##+with+a+system+compiler+(not+to+mention+the+requisite+knowledge+of+C).

##+This+script+is+written+with+portability+and+(to+the+extent+possible,+speed)
##+in+mind,+hence+the+use+of+printf+for+echo+and+case+statements+where+they
##+can+be+substituded+for+test,+though+I've+had+to+scale+back+a+bit+on+that.

##+It+is+(to+the+best+of+my+knowledge)+written+in+standard+POSIX+shell,+and
##+has+been+tested+with+bash-as-bin-sh,+dash,+and+ksh93.+zsh+seems+to+have
##+issues+with+it,+though+I'm+not+sure+why;+so+probably+best+to+avoid+for+now.

##+Particularly+useful+(in+fact,+the+reason+I+wrote+this)+is+the+fact+that
##+it+can+be+used+within+a+shell+script+to+find+the+path+of+the+script+itself.
##+(I+am+sure+the+shell+knows+this+already;+but+most+likely+for+the+sake+of
##+security+it+is+not+made+readily+available.+The+implementation+of+"$0"
##+specificies+that+the+$0+must+be+the+location+of+**last**+symbolic+link+in
##+a+chain,+or+wherever+it+resides+in+the+path.)+This+can+be+used+for+some
##+...interesting+things,+like+self-duplicating+and+self-modifiying+scripts.

##+Currently+supported+are+three+errors:+whether+the+file+specified+exists
##+(ala+ENOENT),+whether+its+target+exists/is+accessible;+and+the+special
##+case+of+when+a+sybolic+link+references+itself+"foo+->+foo":+a+common+error
##+for+beginners,+since+'ln'+does+not+produce+an+error+if+the+order+of+link
##+and+target+are+reversed+on+the+command+line.+(See+POSIX+signal+ELOOP.)

##+It+would+probably+be+rather+simple+to+write+to+use+this+as+a+basis+for
##+a+pure+shell+implementation+of+the+'symlinks'+util+included+with+Linux.

##+As+an+aside,+the+amount+of+code+below+**completely**+belies+the+amount
##+effort+it+took+to+get+this+right+--+but+I+guess+that's+coding+for+you.

##===-------------------------------------------------------------------===##

for+argv;+do+:;+done+#+Last+parameter+on+command+line,+for+options+parsing.

##+Error+messages.+Use+functions+so+that+we+can+sub+in+when+the+error+occurs.

recurses(){+printf+"Self-referential:\n\t$argv+->\n\t$argv\n"+;}
dangling(){+printf+"Broken+symlink:\n\t$argv+->\n\t"$(readlink+"$argv")"\n"+;}
errnoent(){+printf+"No+such+file:+"$@"\n"+;}+#+Borrow+a+horrible+signal+name.

#+Probably+best+not+to+install+as+'pathfull',+if+you+can+avoid+it.

pathfull(){+cd+"$(dirname+"$@")";+link="$(readlink+"$(basename+"$@")")"

##+'test+and+'ls'+report+different+status+for+bad+symlinks,+so+we+use+this.

+if+[+!+-e+"$@"+];+then+if+$(ls+-d+"$@"+2>/dev/null)+2>/dev/null;++then
++++errnoent+1>&2;+exit+1;+elif+[+!+-e+"$@"+-a+"$link"+=+"$@"+];+++then
++++recurses+1>&2;+exit+1;+elif+[+!+-e+"$@"+]+&&+[+!+-z+"$link"+];+then
++++dangling+1>&2;+exit+1;+fi
+fi

##+Not+a+link,+but+there+might+be+one+in+the+path,+so+'cd'+and+'pwd'.

+if+[+-z+"$link"+];+then+if+[+"$(dirname+"$@"+%7C+cut+-c1)"+=+'/'+];+then
+++printf+"$@\n";+exit+0;+else+printf+"$(pwd)/$(basename+"$@")\n";+fi;+exit+0
+fi

##+Walk+the+symlinks+back+to+the+origin.+Calls+itself+recursivly+as+needed.

+while+[+"$link"+];+do
+++cd+"$(dirname+"$link")";+newlink="$(readlink+"$(basename+"$link")")"
+++case+"$newlink"+in
++++"$link")+dangling+1>&2+&&+exit+1+++++++++++++++++++++++++++++++++++++++;;
+++++++++'')+printf+"$(pwd)/$(basename+"$link")\n";+exit+0+++++++++++++++++;;
++++++++++*)+link="$newlink"+&&+pathfull+"$link"+++++++++++++++++++++++++++;;
+++esac
+done
+printf+"$(pwd)/$(basename+"$newlink")\n"
}

##+Demo.+Install+somewhere+deep+in+the+filesystem,+then+symlink+somewhere+
##+else,+symlink+again+(maybe+with+a+different+name)+elsewhere,+and+link
##+back+into+the+directory+you+started+in+(or+something.)+The+absolute+path
##+of+the+script+will+always+be+reported+in+the+usage,+along+with+"$0".

if+[+-z+"$argv"+];+then+scriptname="$(pathfull+"$0")"

#+Yay+ANSI+l33t+codes!+Fancy.
+printf+"\n\033[3mfrom/as:+\033[4m$0\033[0m\n\n\033[1mUSAGE:\033[0m+++"
+printf+"\033[4m$scriptname\033[24m+[+link+%7C+file+%7C+dir+]\n\n+++++++++"
+printf+"Recursive+readlink+for+the+authoritative+file,+symlink+after+"
+printf+"symlink.\n\n\n+++++++++\033[4m$scriptname\033[24m\n\n++++++++"
+printf+"+From+within+an+invocation+of+a+script,+locate+the+script's+"
+printf+"own+file\n+++++++++(no+matter+where+it+has+been+linked+or+"
+printf+"from+where+it+is+being+called).\n\n"

else+pathfull+"$@"
fi|code-block|syntax|javascript|1860801|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I believe I've got this one. I'm late to the party, but I think some will appreciate it being here if they come across this thread. The comments should explain:

<pre><code>#!/bin/sh # dash bash ksh # !zsh (issues). G. Nixon, 12/2013. Public domain.

## 'linkread' or 'fullpath' or (you choose) is a little tool to recursively
## dereference symbolic links (ala 'readlink') until the originating file
## is found. This is effectively the same function provided in stdlib.h as
## 'realpath' and on the command line in GNU 'readlink -f'.

## Neither of these tools, however, are particularly accessible on the many
## systems that do not have the GNU implementation of readlink, nor ship
## with a system compiler (not to mention the requisite knowledge of C).

## This script is written with portability and (to the extent possible, speed)
## in mind, hence the use of printf for echo and case statements where they
## can be substituded for test, though I've had to scale back a bit on that.

## It is (to the best of my knowledge) written in standard POSIX shell, and
## has been tested with bash-as-bin-sh, dash, and ksh93. zsh seems to have
## issues with it, though I'm not sure why; so probably best to avoid for now.

## Particularly useful (in fact, the reason I wrote this) is the fact that
## it can be used within a shell script to find the path of the script itself.
## (I am sure the shell knows this already; but most likely for the sake of
## security it is not made readily available. The implementation of "$0"
## specificies that the $0 must be the location of **last** symbolic link in
## a chain, or wherever it resides in the path.) This can be used for some
## ...interesting things, like self-duplicating and self-modifiying scripts.

## Currently supported are three errors: whether the file specified exists
## (ala ENOENT), whether its target exists/is accessible; and the special
## case of when a sybolic link references itself "foo -&gt; foo": a common error
## for beginners, since 'ln' does not produce an error if the order of link
## and target are reversed on the command line. (See POSIX signal ELOOP.)

## It would probably be rather simple to write to use this as a basis for
## a pure shell implementation of the 'symlinks' util included with Linux.

## As an aside, the amount of code below **completely** belies the amount
## effort it took to get this right -- but I guess that's coding for you.

##===-------------------------------------------------------------------===##

for argv; do :; done # Last parameter on command line, for options parsing.

## Error messages. Use functions so that we can sub in when the error occurs.

recurses(){ printf "Self-referential:\n\t$argv -&gt;\n\t$argv\n" ;}
dangling(){ printf "Broken symlink:\n\t$argv -&gt;\n\t"$(readlink "$argv")"\n" ;}
errnoent(){ printf "No such file: "$@"\n" ;} # Borrow a horrible signal name.

# Probably best not to install as 'pathfull', if you can avoid it.

pathfull(){ cd "$(dirname "$@")"; link="$(readlink "$(basename "$@")")"

## 'test and 'ls' report different status for bad symlinks, so we use this.

 if [ ! -e "$@" ]; then if $(ls -d "$@" 2&gt;/dev/null) 2&gt;/dev/null; then
 errnoent 1&gt;&amp;2; exit 1; elif [ ! -e "$@" -a "$link" = "$@" ]; then
 recurses 1&gt;&amp;2; exit 1; elif [ ! -e "$@" ] &amp;&amp; [ ! -z "$link" ]; then
 dangling 1&gt;&amp;2; exit 1; fi
 fi

## Not a link, but there might be one in the path, so 'cd' and 'pwd'.

 if [ -z "$link" ]; then if [ "$(dirname "$@" | cut -c1)" = '/' ]; then
 printf "$@\n"; exit 0; else printf "$(pwd)/$(basename "$@")\n"; fi; exit 0
 fi

## Walk the symlinks back to the origin. Calls itself recursivly as needed.

 while [ "$link" ]; do
 cd "$(dirname "$link")"; newlink="$(readlink "$(basename "$link")")"
 case "$newlink" in
 "$link") dangling 1&gt;&amp;2 &amp;&amp; exit 1 ;;
 '') printf "$(pwd)/$(basename "$link")\n"; exit 0 ;;
 *) link="$newlink" &amp;&amp; pathfull "$link" ;;
 esac
 done
 printf "$(pwd)/$(basename "$newlink")\n"
}

## Demo. Install somewhere deep in the filesystem, then symlink somewhere 
## else, symlink again (maybe with a different name) elsewhere, and link
## back into the directory you started in (or something.) The absolute path
## of the script will always be reported in the usage, along with "$0".

if [ -z "$argv" ]; then scriptname="$(pathfull "$0")"

# Yay ANSI l33t codes! Fancy.
 printf "\n\033[3mfrom/as: \033[4m$0\033[0m\n\n\033[1mUSAGE:\033[0m "
 printf "\033[4m$scriptname\033[24m [ link | file | dir ]\n\n "
 printf "Recursive readlink for the authoritative file, symlink after "
 printf "symlink.\n\n\n \033[4m$scriptname\033[24m\n\n "
 printf " From within an invocation of a script, locate the script's "
 printf "own file\n (no matter where it has been linked or "
 printf "from where it is being called).\n\n"

else pathfull "$@"
fi
</code></pre>

blocks|key|2073647|text|嗯，如果在路径中，basename和dirname就是不会切割它，并且遍历路径是困难的(如果父级没有导出路径怎么办？！)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2073648|但是，shell必须有一个指向其脚本的开放句柄，而在Bash中，该句柄是#255。|2073649|SELF=`readlink+/proc/$$/fd/255`|code-block|syntax|javascript|2073650|这对我很有效。|2073651|entityMap|0|LINK|mutability|MUTABLE|url|https://linux.die.net/man/1/basename|1|https://linux.die.net/man/1/dirname^0|9|8|I|7|9|8|0|I|7|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]|$9|11|A|12|B|C]]|D|@$9|13|A|14|1|15]|$9|16|A|17|1|18]]|E|$]]|$1|F|3|G|5|6|7|19|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|1A|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|1B|8|@]|D|@]|E|$]]|$1|O|3|-4|5|6|7|1C|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]|W|$5|R|S|T|E|$U|X]]]]

Hmm, if in the path, <a href="https://linux.die.net/man/1/basename" rel="nofollow noreferrer"><code>basename</code></a> and <a href="https://linux.die.net/man/1/dirname" rel="nofollow noreferrer"><code>dirname</code></a> are just not going to cut it and walking the path is hard (what if the parent didn't export PATH?!).
However, the shell has to have an open handle to its script, and in Bash the handle is #255.
<pre><code>SELF=`readlink /proc/$$/fd/255`
</code></pre>
works for me.

blocks|key|2074567|text|在我看来，最好的紧凑解决方案是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2074568|"$(+cd+"$(+echo+"${BASH_SOURCE[0]%25/*}"+)";+pwd+)"|code-block|syntax|javascript|2074569|除了Bash之外，不依赖任何其他东西。使用dirname、readlink和basename最终会导致兼容性问题，所以最好尽量避免使用它们。|offset|length|style|CODE|2074570|entityMap|0|LINK|mutability|MUTABLE|url|https://linux.die.net/man/1/dirname|1|https://linux.die.net/man/1/readlink|2|https://linux.die.net/man/1/basename^0|0|0|L|7|T|8|12|8|L|7|0|T|8|1|12|8|2|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@$I|11|J|12|K|L]|$I|13|J|14|K|L]|$I|15|J|16|K|L]]|9|@$I|17|J|18|1|19]|$I|1A|J|1B|1|1C]|$I|1D|J|1E|1|1F]]|A|$]]|$1|M|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]|U|$5|P|Q|R|A|$S|V]]|W|$5|P|Q|R|A|$S|X]]]]

The best compact solution in my view would be:
<pre><code>&quot;$( cd &quot;$( echo &quot;${BASH_SOURCE[0]%/*}&quot; )&quot;; pwd )&quot;
</code></pre>
There is no reliance on anything other than Bash. The use of <a href="https://linux.die.net/man/1/dirname" rel="nofollow noreferrer"><code>dirname</code></a>, <a href="https://linux.die.net/man/1/readlink" rel="nofollow noreferrer"><code>readlink</code></a> and <a href="https://linux.die.net/man/1/basename" rel="nofollow noreferrer"><code>basename</code></a> will eventually lead to compatibility issues, so they are best avoided if at all possible.

blocks|key|2073980|text|这些其他答案都不适用于Finder在OS X中启动的Bash脚本。我最终使用了：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2073981|SCRIPT_LOC="`ps+-p+$$+%7C+sed+/PID/d+%7C+sed+s:.*/Network/:/Network/:+%7C
sed+s:.*/Volumes/:/Volumes/:`"|code-block|syntax|javascript|2073982|它不是很漂亮，但它能完成工作。|2073983|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Finder_(software)|1|https://en.wikipedia.org/wiki/Mac_OS_X^0|B|6|0|I|4|1|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]|$A|Y|B|Z|1|10]]|C|$]]|$1|D|3|E|5|F|7|11|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|12|8|@]|9|@]|C|$]]|$1|K|3|-4|5|6|7|13|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]|S|$5|N|O|P|C|$Q|T]]]]

None of these other answers worked for a Bash script launched by <a href="https://en.wikipedia.org/wiki/Finder_(software)" rel="nofollow noreferrer">Finder</a> in <a href="https://en.wikipedia.org/wiki/Mac_OS_X" rel="nofollow noreferrer">OS X</a>. I ended up using:
<pre><code>SCRIPT_LOC=&quot;`ps -p $$ | sed /PID/d | sed s:.*/Network/:/Network/: |
sed s:.*/Volumes/:/Volumes/:`&quot;
</code></pre>
It is not pretty, but it gets the job done.

blocks|key|2074029|text|使用readlink和dirname的组合来规范化名称(如果是符号链接，则可以追随其返回其源)并提取目录名：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2074030|script="`readlink+-f+"${BASH_SOURCE[0]}"`"
dir="`dirname+"$script"`"|code-block|syntax|javascript|2074031|entityMap|0|LINK|mutability|MUTABLE|url|https://linux.die.net/man/1/readlink|1|https://linux.die.net/man/1/dirname^0|2|8|0|B|7|1|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]|$A|W|B|X|1|Y]]|C|$]]|$1|D|3|E|5|F|7|Z|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]|Q|$5|L|M|N|C|$O|R]]]]

Use a combination of <a href="https://linux.die.net/man/1/readlink" rel="nofollow noreferrer">readlink</a> to canonicalize the name (with a bonus of following it back to its source if it is a symlink) and <a href="https://linux.die.net/man/1/dirname" rel="nofollow noreferrer">dirname</a> to extract the directory name:
<pre><code>script=&quot;`readlink -f &quot;${BASH_SOURCE[0]}&quot;`&quot;
dir=&quot;`dirname &quot;$script&quot;`&quot;
</code></pre>

blocks|key|1861292|text|当这里的其他答案不起作用时，这对我来说是有效的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1861293|thisScriptPath=`realpath+$0`
thisDirPath=`dirname+$thisScriptPath`
echo+$thisDirPath|code-block|syntax|javascript|1861294|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This worked for me when the other answers here did not:

<pre><code>thisScriptPath=`realpath $0`
thisDirPath=`dirname $thisScriptPath`
echo $thisDirPath
</code></pre>

blocks|key|2076095|text|顶部响应并不是在所有情况下都有效...|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2076096|由于我在通过"sh+my_script.sh“调用外壳脚本时，在一些非常新的和较新安装的Ubuntu 16.04+(Xenial+Xerus)系统上使用包含的'cd‘方法遇到了BASH_SOURCE问题，所以我尝试了一些不同的方法，到目前为止，似乎运行得相当流畅。这种方法在脚本中更加紧凑，而且更加不那么神秘。|offset|length|2076097|这种替代方法使用来自coreutils包的外部应用程序'realpath‘和'dirname’。(好吧，不是每个人都喜欢调用辅助进程的开销-但当看到解析真实对象的多行脚本时，在一个二进制使用中解析它也不会那么糟糕。)|2076098|因此，让我们看一下上述任务的替代解决方案的一个示例，即查询某个文件的真实绝对路径：|2076099|PATH_TO_SCRIPT=`realpath+-s+$0`
PATH_TO_SCRIPT_DIR=`dirname+$PATH_TO_SCRIPT`|code-block|syntax|javascript|2076100|但最好是使用这个演进版本，以支持使用带有空格的路径(或者甚至一些其他特殊字符)：|2076101|PATH_TO_SCRIPT=`realpath+-s+"$0"`
PATH_TO_SCRIPT_DIR=`dirname+"$PATH_TO_SCRIPT"`|2076102|实际上，如果您不需要脚本变量的值，那么您可以将这两行代码合并为甚至一行。但是为什么你真的要为此付出努力呢？|2076103|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Ubuntu_version_history#Ubuntu_16.04_LTS_.28Xenial_Xerus.29|1|https://linux.die.net/man/1/realpath|2|https://linux.die.net/man/1/dirname^0|0|18|C|0|0|S|8|1|13|7|2|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|17|8|@]|9|@$D|18|E|19|1|1A]]|A|$]]|$1|F|3|G|5|6|7|1B|8|@]|9|@$D|1C|E|1D|1|1E]|$D|1F|E|1G|1|1H]]|A|$]]|$1|H|3|I|5|6|7|1I|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|1J|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|1K|8|@]|9|@]|A|$]]|$1|Q|3|R|5|L|7|1L|8|@]|9|@]|A|$M|N]]|$1|S|3|T|5|6|7|1M|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11]]|12|$5|X|Y|Z|A|$10|13]]|14|$5|X|Y|Z|A|$10|15]]]]

The top response does not work in all cases...
As I had problems with the BASH_SOURCE with the included 'cd' approach on some very fresh and also on less fresh installed <a href="https://en.wikipedia.org/wiki/Ubuntu_version_history#Ubuntu_16.04_LTS_.28Xenial_Xerus.29" rel="nofollow noreferrer">Ubuntu 16.04</a> (Xenial Xerus) systems when invoking the shell script by means of &quot;sh my_script.sh&quot;, I tried out something different that as of now seems to run quite smoothly for my purposes. The approach is a bit more compact in the script and is further much lesser cryptic feeling.
This alternate approach uses the external applications '<a href="https://linux.die.net/man/1/realpath" rel="nofollow noreferrer">realpath</a>' and '<a href="https://linux.die.net/man/1/dirname" rel="nofollow noreferrer">dirname</a>' from the coreutils package. (Okay, not anyone likes the overhead of invoking secondary processes - but when seeing the multi-line scripting for resolving the true object it won't be that bad either having it solve in a single binary usage.)
So let’s see one example of those alternate solution for the described task of querying the true absolute path to a certain file:
<pre><code>PATH_TO_SCRIPT=`realpath -s $0`
PATH_TO_SCRIPT_DIR=`dirname $PATH_TO_SCRIPT`
</code></pre>
But preferably you should use this evolved version to also support the use of paths with spaces (or maybe even some other special characters):
<pre><code>PATH_TO_SCRIPT=`realpath -s &quot;$0&quot;`
PATH_TO_SCRIPT_DIR=`dirname &quot;$PATH_TO_SCRIPT&quot;`
</code></pre>
Indeed, if you don’t need the value of the SCRIPT variable then you might be able to merge this two-liner into even a single line. But why really shall you spend the effort for this?

blocks|key|1862532|text|如果在目录名称的末尾有任何换行符，则当前的解决方案都不起作用-它们将被命令替换剥离。要解决此问题，您可以在命令替换中附加一个非换行符，然后只去掉该字符：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1862533|dir="$(cd+"$(dirname+"${BASH_SOURCE[0]}")"+&&+pwd+&&+echo+x)"
dir="${dir%25x}"|code-block|syntax|javascript|1862534|这可以防止两种非常常见的情况:意外和破坏。脚本不应该因为某人在某处执行了mkdir+$'\n'而以不可预知的方式失败。|offset|length|style|CODE|1862535|entityMap^0|0|0|10|B|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

None of the current solutions work if there are any newlines at the end of the directory name - They will be stripped by the command substitution. To work around this you can append a non-newline character inside the command substitution and then strip just that character off:
<pre class="lang-sh prettyprint-override"><code>dir=&quot;$(cd &quot;$(dirname &quot;${BASH_SOURCE[0]}&quot;)&quot; &amp;&amp; pwd &amp;&amp; echo x)&quot;
dir=&quot;${dir%x}&quot;
</code></pre>
This protects against two very common situations: Accidents and sabotage. A script shouldn't fail in unpredictable ways just because someone, somewhere, did a <code>mkdir $'\n'</code>.

blocks|key|2073839|text|这是我发现的唯一可靠的方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2073840|SCRIPT_DIR=$(dirname+$(cd+"$(dirname+"$BASH_SOURCE")";+pwd))|code-block|syntax|javascript|2073841|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This is the only way I've found to tell reliably:

<pre><code>SCRIPT_DIR=$(dirname $(cd "$(dirname "$BASH_SOURCE")"; pwd))
</code></pre>

blocks|key|2075687|text|我通常使用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2075688|dirname+$(which+$BASH_SOURCE)|code-block|syntax|javascript|2075689|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I usually use:
<pre><code>dirname $(which $BASH_SOURCE)
</code></pre>

blocks|key|2075762|text|下面是一个在Bash或zsh下工作的命令，无论是独立执行还是源码执行：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2075763|[+-n+"$ZSH_VERSION"+]+&&+this_dir=$(dirname+"${(%25):-%25x}")+\
++++%7C%7C+this_dir=$(dirname+"${BASH_SOURCE[0]:-$0}")|code-block|syntax|javascript|2075764|它是如何工作的|2075765|zsh当前文件扩展名：${(%25):-%25x}|offset|length|style|CODE|2075766|zsh中的${(%25):-%25x}扩展到当前正在执行的文件的路径。|2075767|备用替换运算符:-|2075768|您已经知道${...}会替换字符串中的变量。您可能不知道在替换过程中可以对变量执行某些操作(在Bash和zsh中)，比如后备展开运算符:-|2075769|%25+x=ok
%25+echo+"${x}"
ok

%25+echo+"${x:-fallback}"
ok

%25+x=
%25+echo+"${x:-fallback}"
fallback

%25+y=yvalue
%25+echo+"${x:-$y}"
yvalue|2075770|%25x提示转义代码|2075771|接下来，我们将介绍提示转义代码，这是一个仅限zsh的特性。在prompt+strings中，%25x将展开到文件的路径，但通常只有在对zsh进行展开时才会这样做。为了在我们的替换中启用这些代码，我们可以在变量名之前添加一个(%25)标志：|2075772|%25+cat+apath/test.sh
fpath=%25x
echo+"${(%25)fpath}"

%25+source+apath/test.sh
apath/test.sh

%25+cd+apath
%25+source+test.sh
test.sh|2075773|不太可能的匹配:百分比逃逸和后退|2075774|到目前为止，我们所做的一切都是有效的，但是避免创建额外的fpath变量会更整洁。我们可以使用:-并将%25x放在回退字符串中，而不是将%25x放在fpath中：|2075775|%25+cat+test.sh
echo+"${(%25):-%25x}"

%25+source+test.sh
test.sh|2075776|请注意，我们通常会在(%25)和:-之间放置一个变量名，但我们将其保留为空。不能声明或设置名称为空的变量，因此总是会触发回退。|2075777|结束语：print+-P+%25x如何|2075778|现在我们几乎有了脚本的目录。我们可以使用print+-P+%25x来获得相同的文件路径，但在我们的例子中，我们需要将其作为参数传递给dirname，这将需要启动一个新的子subshell的开销：|2075779|%25+cat+apath/test.sh
dirname+"$(print+-P+%25x)"++#+$(...)+runs+a+command+in+a+new+process
dirname+"${(%25):-%25x}"

%25+source+apath/test.sh
apath
apath|2075780|事实证明，hacky方法更具性能和简洁性。|2075781|entityMap|0|LINK|mutability|MUTABLE|url|http://tldp.org/LDP/abs/html/parameter-substitution.html|1|http://zsh.sourceforge.net/Doc/Release/Expansion.html#Parameter-Expansion|2|http://zsh.sourceforge.net/Doc/Release/Prompt-Expansion.html#Shell-state^0|0|0|0|B|A|0|5|A|0|7|2|0|5|6|1V|2|1B|4|0|1G|3|1|0|0|0|2|0|1A|2|31|3|U|E|2|0|0|0|S|5|1A|2|1E|2|1T|2|1X|5|0|0|A|3|E|2|0|4|B|0|K|B|1S|7|0|0|0^^$0|@$1|2|3|4|5|6|7|1U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|1W|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|1X|8|@$K|1Y|L|1Z|M|N]]|9|@]|A|$]]|$1|O|3|P|5|6|7|20|8|@$K|21|L|22|M|N]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|23|8|@$K|24|L|25|M|N]]|9|@]|A|$]]|$1|S|3|T|5|6|7|26|8|@$K|27|L|28|M|N]|$K|29|L|2A|M|N]]|9|@$K|2B|L|2C|1|2D]|$K|2E|L|2F|1|2G]]|A|$]]|$1|U|3|V|5|D|7|2H|8|@]|9|@]|A|$E|F]]|$1|W|3|X|5|6|7|2I|8|@$K|2J|L|2K|M|N]]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|2L|8|@$K|2M|L|2N|M|N]|$K|2O|L|2P|M|N]]|9|@$K|2Q|L|2R|1|2S]]|A|$]]|$1|10|3|11|5|D|7|2T|8|@]|9|@]|A|$E|F]]|$1|12|3|13|5|6|7|2U|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|2V|8|@$K|2W|L|2X|M|N]|$K|2Y|L|2Z|M|N]|$K|30|L|31|M|N]|$K|32|L|33|M|N]|$K|34|L|35|M|N]]|9|@]|A|$]]|$1|16|3|17|5|D|7|36|8|@]|9|@]|A|$E|F]]|$1|18|3|19|5|6|7|37|8|@$K|38|L|39|M|N]|$K|3A|L|3B|M|N]]|9|@]|A|$]]|$1|1A|3|1B|5|6|7|3C|8|@$K|3D|L|3E|M|N]]|9|@]|A|$]]|$1|1C|3|1D|5|6|7|3F|8|@$K|3G|L|3H|M|N]|$K|3I|L|3J|M|N]]|9|@]|A|$]]|$1|1E|3|1F|5|D|7|3K|8|@]|9|@]|A|$E|F]]|$1|1G|3|1H|5|6|7|3L|8|@]|9|@]|A|$]]|$1|1I|3|-4|5|6|7|3M|8|@]|9|@]|A|$]]]|1J|$1K|$5|1L|1M|1N|A|$1O|1P]]|1Q|$5|1L|1M|1N|A|$1O|1R]]|1S|$5|1L|1M|1N|A|$1O|1T]]]]

Here's a command that works under either Bash or zsh, and whether executed stand-alone or sourced:
<pre><code>[ -n &quot;$ZSH_VERSION&quot; ] &amp;&amp; this_dir=$(dirname &quot;${(%):-%x}&quot;) \
 || this_dir=$(dirname &quot;${BASH_SOURCE[0]:-$0}&quot;)
</code></pre>
<h1>How it works</h1>
<h2>The zsh current file expansion: <code>${(%):-%x}</code></h2>
<code>${(%):-%x}</code> in zsh expands to the path of the currently-executing file.
<h3>The fallback substitution operator <code>:-</code></h3>
You know already that <code>${...}</code> substitutes variables inside of strings. You might not know that certain operations are possible (in both <a href="http://tldp.org/LDP/abs/html/parameter-substitution.html" rel="nofollow noreferrer">Bash</a> and <a href="http://zsh.sourceforge.net/Doc/Release/Expansion.html#Parameter-Expansion" rel="nofollow noreferrer">zsh</a>) on the variables during substitution, like the fallback expansion operator <code>:-</code>:
<pre><code>% x=ok
% echo &quot;${x}&quot;
ok

% echo &quot;${x:-fallback}&quot;
ok

% x=
% echo &quot;${x:-fallback}&quot;
fallback

% y=yvalue
% echo &quot;${x:-$y}&quot;
yvalue
</code></pre>
<h3>The <code>%x</code> prompt escape code</h3>
Next, we'll introduce prompt escape codes, a zsh-only feature. In zsh, <code>%x</code> will expand to the path of the file, but normally this is only when doing expansion for <a href="http://zsh.sourceforge.net/Doc/Release/Prompt-Expansion.html#Shell-state" rel="nofollow noreferrer">prompt strings</a>. To enable those codes in our substitution, we can add a <code>(%)</code> flag before the variable name:
<pre><code>% cat apath/test.sh
fpath=%x
echo &quot;${(%)fpath}&quot;

% source apath/test.sh
apath/test.sh

% cd apath
% source test.sh
test.sh
</code></pre>
<h3>An unlikely match: the percent escape and the fallback</h3>
What we have so far works, but it would be tidier to avoid creating the extra <code>fpath</code> variable. Instead of putting <code>%x</code> in <code>fpath</code>, we can use <code>:-</code> and put <code>%x</code> in the fallback string:
<pre><code>% cat test.sh
echo &quot;${(%):-%x}&quot;

% source test.sh
test.sh
</code></pre>
Note that we normally would put a variable name between <code>(%)</code> and <code>:-</code>, but we left it blank. The variable with a blank name can't be declared or set, so the fallback is always triggered.
<h3>Finishing up: what about <code>print -P %x</code>?</h3>
Now we almost have the directory of our script. We could have used <code>print -P %x</code> to get the same file path with fewer hacks, but in our case, where we need to pass it as an argument to <code>dirname</code>, that would have required the overhead of a starting a new subshell:
<pre><code>% cat apath/test.sh
dirname &quot;$(print -P %x)&quot; # $(...) runs a command in a new process
dirname &quot;${(%):-%x}&quot;

% source apath/test.sh
apath
apath
</code></pre>
It turns out that the hacky way is both more performant and succinct.

blocks|key|2076299|text|令人恼火的是，当可执行脚本是符号链接时，这是我发现的唯一可以在Linux和macOS上运行的一行程序：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2076300|SCRIPT_DIR=$(python+-c+"import+os,+sys;+print(os.path.dirname(os.path.realpath('${BASH_SOURCE[0]}')))")|code-block|syntax|javascript|2076301|在Linux和macOS上进行了测试，并与本文中的其他解决方案进行了比较：https://gist.github.com/ptc-mrucci/61772387878ed53a6c717d51a21d9371|offset|length|2076302|entityMap|0|LINK|mutability|MUTABLE|url|https://gist.github.com/ptc-mrucci/61772387878ed53a6c717d51a21d9371^0|0|0|11|1V|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

This is, annoyingly, the only one-liner I've found that works on both Linux and macOS when the executable script is a symlink:
<pre><code>SCRIPT_DIR=$(python -c &quot;import os, sys; print(os.path.dirname(os.path.realpath('${BASH_SOURCE[0]}')))&quot;)
</code></pre>
Tested on Linux and macOS and compared to other solutions in this gist: <a href="https://gist.github.com/ptc-mrucci/61772387878ed53a6c717d51a21d9371" rel="nofollow noreferrer">https://gist.github.com/ptc-mrucci/61772387878ed53a6c717d51a21d9371</a>

blocks|key|2075251|text|如果您的Bash脚本是一个符号链接，则可以这样做：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2075252|#!/usr/bin/env+bash

dirn="$(dirname+"$0")"
rl="$(readlink+"$0")";
exec_dir="$(dirname+$(dirname+"$rl"))";
my_path="$dirn/$exec_dir";
X="$(cd+$(dirname+${my_path})+&&+pwd)/$(basename+${my_path})"|code-block|syntax|javascript|2075253|X是包含Bash脚本的目录(原始文件，而不是符号链接)。我对天发誓，这是我知道的唯一正确的方法。|2075254|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

If your Bash script is a symlink, then this is the way to do it:
<pre><code>#!/usr/bin/env bash

dirn=&quot;$(dirname &quot;$0&quot;)&quot;
rl=&quot;$(readlink &quot;$0&quot;)&quot;;
exec_dir=&quot;$(dirname $(dirname &quot;$rl&quot;))&quot;;
my_path=&quot;$dirn/$exec_dir&quot;;
X=&quot;$(cd $(dirname ${my_path}) &amp;&amp; pwd)/$(basename ${my_path})&quot;
</code></pre>
X is the directory that contains your Bash script (the original file, not the symlink). I swear to God this works, and it is the only way I know of doing this properly.

blocks|key|2076109|text|Python被提到过几次。下面是JavaScript+(即Node.js)替代方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2076110|baseDirRelative=$(dirname+"$0")
baseDir=$(node+-e+"console.log(require('path').resolve('$baseDirRelative'))")+#+Get+absolute+path+using+Node.js

echo+$baseDir|code-block|syntax|javascript|2076111|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Node.js^0|T|7|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

Python was mentioned a few times. Here is the JavaScript (i.e., <a href="https://en.wikipedia.org/wiki/Node.js" rel="nofollow noreferrer">Node.js</a>) alternative:
<pre class="lang-sh prettyprint-override"><code>baseDirRelative=$(dirname &quot;$0&quot;)
baseDir=$(node -e &quot;console.log(require('path').resolve('$baseDirRelative'))&quot;) # Get absolute path using Node.js

echo $baseDir
</code></pre>

blocks|key|2076248|text|我尝试了以下3种不同的执行方式。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2076249|echo+$(realpath+$_)|offset|length|style|CODE|2076250|.+application+++++++++#+/correct/path/to/dir+or+/path/to/temporary_dir
bash+application++++++#+/path/to/bash
/PATH/TO/application++#+/correct/path/to/dir|code-block|syntax|javascript|2076251|echo+$(realpath+$(dirname+$0))|2076252|.+application+++++++++#+failed+with+`realpath:+missing+operand`
bash+application++++++#+/correct/path/to/dir
/PATH/TO/application++#+/correct/path/to/dir|2076253|echo+$(realpath+$BASH_SOURCE)|2076254|$BASH_SOURCE和${BASH_SOURCE[0]}基本上是一样的。|2076255|.+application+++++++++#+/correct/path/to/dir
bash+application++++++#+/correct/path/to/dir
/PATH/TO/application++#+/correct/path/to/dir|2076256|似乎只有$(realpath+$BASH_SOURCE)是可靠的。|2076257|entityMap^0|0|0|J|0|0|0|U|0|0|0|T|0|0|C|D|H|0|0|4|O|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@$D|12|E|13|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|14|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|15|8|@$D|16|E|17|F|G]]|9|@]|A|$]]|$1|O|3|P|5|J|7|18|8|@]|9|@]|A|$K|L]]|$1|Q|3|R|5|6|7|19|8|@$D|1A|E|1B|F|G]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1C|8|@$D|1D|E|1E|F|G]|$D|1F|E|1G|F|G]]|9|@]|A|$]]|$1|U|3|V|5|J|7|1H|8|@]|9|@]|A|$K|L]]|$1|W|3|X|5|6|7|1I|8|@$D|1J|E|1K|F|G]]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1L|8|@]|9|@]|A|$]]]|Z|$]]

I tried the followings with 3 different executions.
<h3><code>echo $(realpath $_)</code></h3>
<pre><code>. application # /correct/path/to/dir or /path/to/temporary_dir
bash application # /path/to/bash
/PATH/TO/application # /correct/path/to/dir
</code></pre>
<h3><code>echo $(realpath $(dirname $0))</code></h3>
<pre><code>. application # failed with `realpath: missing operand`
bash application # /correct/path/to/dir
/PATH/TO/application # /correct/path/to/dir
</code></pre>
<h3><code>echo $(realpath $BASH_SOURCE)</code></h3>
<code>$BASH_SOURCE</code> is basically the same with <code>${BASH_SOURCE[0]}</code>.
<pre><code>. application # /correct/path/to/dir
bash application # /correct/path/to/dir
/PATH/TO/application # /correct/path/to/dir
</code></pre>
Only <code>$(realpath $BASH_SOURCE)</code> seems to be reliable.

blocks|key|1861407|text|这是我在我的脚本上的工作方式：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1861408|pathvar="$(+cd+"$(+dirname+$0+)"+&&+pwd+)"|code-block|syntax|javascript|1861409|这将告诉您正在从哪个目录执行启动器(当前脚本)。|1861410|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

This is how I work it on my scripts:
<pre><code>pathvar=&quot;$( cd &quot;$( dirname $0 )&quot; &amp;&amp; pwd )&quot;
</code></pre>
This will tell you which directory the Launcher (current script) is being executed from.

blocks|key|1862437|text|这种方法的一个优点是，它不涉及Bash本身以外的任何内容，也不派生任何子subshell。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1862438|首先，使用模式替换将任何不以/开头的内容(即相对路径)替换为$PWD/。因为我们使用替换来匹配$0的第一个字符，所以我们还必须将它追加回来(替换中的${0:0:1})。|offset|length|style|CODE|1862439|现在我们有了脚本的完整路径；我们可以通过删除最后一个/和后面的任何内容(即脚本名称)来获得目录。然后，可以在cd中使用该目录，或者将其用作相对于脚本的其他路径的前缀。|1862440|#!/bin/bash

BIN=${0/#[!\/]/"$PWD/${0:0:1}"}
DIR=${BIN%25/*}

cd+"$DIR"|code-block|syntax|javascript|1862441|如果您的脚本可能是源代码而不是执行的，那么您当然可以用${BASH_SOURCE[0]}替换$0，例如：|1862442|BIN=${BASH_SOURCE[0]/#[!\/]/"$PWD/${BASH_SOURCE[0]:0:1}"}|1862443|这也适用于可执行脚本。它更长，但更多价。|1862444|entityMap^0|0|E|1|U|5|1B|2|22|8|0|Q|1|1I|2|0|0|R|H|1A|2|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@$D|Y|E|Z|F|G]|$D|10|E|11|F|G]|$D|12|E|13|F|G]|$D|14|E|15|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|16|8|@$D|17|E|18|F|G]|$D|19|E|1A|F|G]]|9|@]|A|$]]|$1|J|3|K|5|L|7|1B|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|1C|8|@$D|1D|E|1E|F|G]|$D|1F|E|1G|F|G]]|9|@]|A|$]]|$1|Q|3|R|5|L|7|1H|8|@]|9|@]|A|$M|N]]|$1|S|3|T|5|6|7|1I|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]]|V|$]]

One advantage of this method is that it doesn't involve anything outside Bash itself and does not fork any subshell neither.
First, use pattern substitution to replace anything not starting with <code>/</code> (i.e., a relative path) with <code>$PWD/</code>. Since we use a substitution to match the first character of <code>$0</code>, we also have to append it back (<code>${0:0:1}</code> in the substitution).
Now we have a full path to the script; we can get the directory by removing the last <code>/</code> and anything the follows (i.e., the script name). That directory can then be used in <code>cd</code> or as a prefix to other paths relative to your script.
<pre class="lang-sh prettyprint-override"><code>#!/bin/bash

BIN=${0/#[!\/]/&quot;$PWD/${0:0:1}&quot;}
DIR=${BIN%/*}

cd &quot;$DIR&quot;
</code></pre>
If your script may be sourced rather than executed, you can of course replace <code>$0</code> with <code>${BASH_SOURCE[0]}</code>, such as:
<pre class="lang-sh prettyprint-override"><code>BIN=${BASH_SOURCE[0]/#[!\/]/&quot;$PWD/${BASH_SOURCE[0]:0:1}&quot;}
</code></pre>
This will work for executable scripts too. It's longer, but more polyvalent.

blocks|key|2076279|text|大多数答案要么不处理通过相对路径符号链接的文件，要么不是一行程序，要么不处理BSD+(Mac)。一个能完成所有这三项任务的解决方案是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2076280|HERE=$(cd+"$(dirname+"$BASH_SOURCE")";+cd+-P+"$(dirname+"$(readlink+"$BASH_SOURCE"+%7C%7C+echo+.)")";+pwd)|code-block|syntax|javascript|2076281|首先，cd+to+bash对脚本目录的概念。然后重新链接该文件，以查看它是否是符号链接(相对的或其他的)，如果是，则cd到该目录。如果不是，则cd到当前目录(保持一行程序是必要的)。然后通过pwd回显当前目录。|offset|length|style|CODE|2076282|您可以将--添加到cd和readlink的参数中，以避免命名为like选项的目录出现问题，但在大多数情况下，我并不为此费心。|2076283|你可以在这里看到完整的解释和插图：|2076284|https://www.binaryphile.com/bash/2020/01/12/determining-the-location-of-your-script-in-bash.html|2076285|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|2N|3|0|4|2|0|0|0|2O|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|10|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|11|8|@$I|12|J|13|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|14|8|@$I|15|J|16|K|L]]|9|@]|A|$]]|$1|O|3|P|5|6|7|17|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|18|8|@]|9|@$I|19|J|1A|1|1B]]|A|$]]|$1|S|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|R]]]]

Most answers either don't handle files which are symlinked via a relative path, aren't one-liners or don't handle BSD (Mac). A solution which does all three is:
<pre><code>HERE=$(cd &quot;$(dirname &quot;$BASH_SOURCE&quot;)&quot;; cd -P &quot;$(dirname &quot;$(readlink &quot;$BASH_SOURCE&quot; || echo .)&quot;)&quot;; pwd)
</code></pre>
First, cd to bash's conception of the script's directory. Then readlink the file to see if it is a symlink (relative or otherwise), and if so, cd to that directory. If not, cd to the current directory (necessary to keep things a one-liner). Then echo the current directory via <code>pwd</code>.
You could add <code>--</code> to the arguments of cd and readlink to avoid issues of directories named like options, but I don't bother for most purposes.
You can see the full explanation with illustrations here:
<a href="https://www.binaryphile.com/bash/2020/01/12/determining-the-location-of-your-script-in-bash.html" rel="nofollow noreferrer">https://www.binaryphile.com/bash/2020/01/12/determining-the-location-of-your-script-in-bash.html</a>

blocks|key|1859674|text|我通常这样做：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1859675|LIBDIR=$(dirname+"$(readlink+-f+"$(type+-P+$0+%7C%7C+echo+$0)")")
source+$LIBDIR/lib.sh|code-block|syntax|javascript|1859676|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I usually do:

<pre><code>LIBDIR=$(dirname "$(readlink -f "$(type -P $0 || echo $0)")")
source $LIBDIR/lib.sh
</code></pre>

blocks|key|2074215|text|这是一个纯Bash解决方案|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2074216|$+cat+a.sh
BASENAME=${BASH_SOURCE/*\/}
DIRNAME=${BASH_SOURCE%25$BASENAME}.
echo+$DIRNAME

$+a.sh
/usr/local/bin/.

$+./a.sh
./.

$+.+a.sh
/usr/local/bin/.

$+/usr/local/bin/a.sh
/usr/local/bin/.|code-block|syntax|javascript|2074217|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Here is a pure Bash solution

<pre><code>$ cat a.sh
BASENAME=${BASH_SOURCE/*\/}
DIRNAME=${BASH_SOURCE%$BASENAME}.
echo $DIRNAME

$ a.sh
/usr/local/bin/.

$ ./a.sh
./.

$ . a.sh
/usr/local/bin/.

$ /usr/local/bin/a.sh
/usr/local/bin/.
</code></pre>

blocks|key|1861750|text|下面将脚本的目录路径存储在dir变量中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1861751|(它还试图支持在Windows的Cygwin下执行。)|1861752|最后，它使用"$@"使用传递给此脚本的所有参数运行my-sample-app可执行文件|1861753|#!/usr/bin/env+sh

dir=$(cd+"${0%25[/\\]*}"+>+/dev/null+&&+pwd)

if+[+-d+/proc/cygdrive+];+then
++++case+"$(uname+-s)"+in
++++++++CYGWIN*%7CMINGW32*%7CMSYS*%7CMINGW*)
++++++++++++#+We+are+under+Windows,+so+translate+path+to+Windows+format.
++++++++++++dir=$(cygpath+-m+"$dir");
++++++++++++;;
++++esac
fi

#+Runs+the+executable+which+is+beside+this+script
"${dir}/my-sample-app"+"$@"|code-block|syntax|javascript|1861754|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Cygwin^0|D|3|0|G|6|0|0|6|4|P|D|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|6|7|Z|8|@]|D|@$9|10|A|11|1|12]]|E|$]]|$1|H|3|I|5|6|7|13|8|@$9|14|A|15|B|C]|$9|16|A|17|B|C]]|D|@]|E|$]]|$1|J|3|K|5|L|7|18|8|@]|D|@]|E|$M|N]]|$1|O|3|-4|5|6|7|19|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]]]

The below stores the script's directory path in the <code>dir</code> variable.
(It also tries to support being executed under <a href="https://en.wikipedia.org/wiki/Cygwin" rel="nofollow noreferrer">Cygwin</a> in Windows.)
And at last it runs the <code>my-sample-app</code> executable with all arguments passed to this script using <code>&quot;$@&quot;</code>:
<pre class="lang-sh prettyprint-override"><code>#!/usr/bin/env sh

dir=$(cd &quot;${0%[/\\]*}&quot; &gt; /dev/null &amp;&amp; pwd)

if [ -d /proc/cygdrive ]; then
 case &quot;$(uname -s)&quot; in
 CYGWIN*|MINGW32*|MSYS*|MINGW*)
 # We are under Windows, so translate path to Windows format.
 dir=$(cygpath -m &quot;$dir&quot;);
 ;;
 esac
fi

# Runs the executable which is beside this script
&quot;${dir}/my-sample-app&quot; &quot;$@&quot;
</code></pre>

blocks|key|2076117|text|我认为最简单的答案是原始变量的参数扩展：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2076118|#!/usr/bin/env+bash

DIR="$(+cd+"$(+dirname+"${BASH_SOURCE[0]}"+)"+>/dev/null+2>&1+&&+pwd+)"
echo+"opt1;+original+answer:+$DIR"
echo+''

echo+"opt2;+simple+answer++:+${BASH_SOURCE[0]%25/*}"|code-block|syntax|javascript|2076119|它应该产生如下输出：|2076120|$+/var/tmp/test.sh
opt1;+original+answer:+/var/tmp

opt2;+simple+answer++:+/var/tmp|2076121|变量/参数扩展${BASH_SOURCE[0]%25/*}"似乎更易于维护。|offset|length|style|CODE|2076122|entityMap^0|0|0|0|0|7|L|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|W|8|@$M|X|N|Y|O|P]]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

I think the simplest answer is a parameter expansion of the original variable:
<pre><code>#!/usr/bin/env bash

DIR=&quot;$( cd &quot;$( dirname &quot;${BASH_SOURCE[0]}&quot; )&quot; &gt;/dev/null 2&gt;&amp;1 &amp;&amp; pwd )&quot;
echo &quot;opt1; original answer: $DIR&quot;
echo ''

echo &quot;opt2; simple answer : ${BASH_SOURCE[0]%/*}&quot;
</code></pre>
It should produce output like:
<pre><code>$ /var/tmp/test.sh
opt1; original answer: /var/tmp

opt2; simple answer : /var/tmp
</code></pre>
The variable/parameter expansion <code>${BASH_SOURCE[0]%/*}&quot;</code> seems much easier to maintain.

blocks|key|1859968|text|function+getScriptAbsoluteDir+{+#+fold>>
++++#+@description+used+to+get+the+script+path
++++#+@param+$1+the+script+$0+parameter
++++local+script_invoke_path="$1"
++++local+cwd=`pwd`

++++#+absolute+path+?+if+so,+the+first+character+is+a+/
++++if+test+"x${script_invoke_path:0:1}"+=+'x/'
++++then
++++++++RESULT=`dirname+"$script_invoke_path"`
++++else
++++++++RESULT=`dirname+"$cwd/$script_invoke_path"`
++++fi
}+#+<<fold|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1859969|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>function getScriptAbsoluteDir { # fold&gt;&gt;
 # @description used to get the script path
 # @param $1 the script $0 parameter
 local script_invoke_path="$1"
 local cwd=`pwd`

 # absolute path ? if so, the first character is a /
 if test "x${script_invoke_path:0:1}" = 'x/'
 then
 RESULT=`dirname "$script_invoke_path"`
 else
 RESULT=`dirname "$cwd/$script_invoke_path"`
 fi
} # &lt;&lt;fold
</code></pre>

blocks|key|1860588|text|我通常在我的脚本的顶部包含以下内容，这些内容在大多数情况下都有效：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1860589|[+"$(dirname+$0)"+=+'.'+]+&&+SOURCE_DIR=$(pwd)+%7C%7C+SOURCE_DIR=$(dirname+$0);
ls+-l+$0+%7C+grep+-q+%5El+&&+SOURCE_DIR=$(ls+-l+$0+%7C+awk+'{print+$NF}');|code-block|syntax|javascript|1860590|如果从当前路径运行，第一行根据pwd的值分配源；如果从其他地方调用，则根据dirname的值分配源。|offset|length|style|CODE|1860591|第二行检查路径以查看它是否是符号链接，如果是，则将SOURCE_DIR更新为链接本身的位置。|1860592|可能有更好的解决方案，但这是我自己想出的最干净的解决方案。|1860593|entityMap|0|LINK|mutability|MUTABLE|url|https://linux.die.net/man/1/dirname^0|0|0|F|3|11|7|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@$I|11|J|12|K|L]]|9|@$I|13|J|14|1|15]]|A|$]]|$1|M|3|N|5|6|7|16|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|17|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]]]

I usually include the following at the top of my scripts which works in the majority of cases:
<pre><code>[ &quot;$(dirname $0)&quot; = '.' ] &amp;&amp; SOURCE_DIR=$(pwd) || SOURCE_DIR=$(dirname $0);
ls -l $0 | grep -q ^l &amp;&amp; SOURCE_DIR=$(ls -l $0 | awk '{print $NF}');
</code></pre>
The first line assigns source based on the value of <code>pwd</code> if run from the current path or <a href="https://linux.die.net/man/1/dirname" rel="nofollow noreferrer">dirname</a> if called from elsewhere.
The second line examines the path to see if it is a symlink and if so, updates SOURCE_DIR to the location of the link itself.
There are probably better solutions out there, but this is the cleanest I've managed to come up with myself.

blocks|key|2074489|text|尝试如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2074490|function+get_realpath()+{

if+[[+-f+"$1"+]]
then
++++#+The+file+*must*+exist
++++if+cd+"$(echo+"${1%25/*}")"+&>/dev/null
++++then
++++++++#+The+file+*may*+not+be+local.
++++++++#+The+exception+is+./file.ext
++++++++#+tTry+'cd+.;+cd+-;'+*works!*
++++++++local+tmppwd="$PWD"
++++++++cd+-+&>/dev/null
++++else
++++++++#+file+*must*+be+local
++++++++local+tmppwd="$PWD"
++++fi
else
++++#+The+file+*cannot*+exist
++++return+1+#+Failure
fi

#+Reassemble+realpath
echo+"$tmppwd"/"${1##*/}"
return+0+#+Success

}

function+get_dirname(){

local+realpath="$(get_realpath+"$1")"
if+((+$?+))+#+True+when+non-zero.
then
++++return+$?+#+Failure
fi
echo+"${realpath%25/*}"
return+0+#+Success

}

#+Then+from+the+top+level:
get_dirname+'./script.sh'

#+Or+within+a+script:
get_dirname+"$0"

#+Can+even+test+the+outcome!
if+((+$?+))+#+True+when+non-zero.
then
++++exit+1+#+Failure
fi|code-block|syntax|javascript|2074491|这些功能和相关工具是我们产品的一部分，已经免费提供给社区，可以在GitHub上以realpath-lib的形式找到。它简单，干净，文档记录良好(非常适合学习)，纯Bash，没有依赖关系。对于跨平台的使用也很好。因此，对于上面的示例，您可以在脚本中简单地：|offset|length|2074492|source+'/path/to/realpath-lib'

get_dirname+"$0"

if+((+$?+))+#+True+when+non-zero.
then
++++exit+1+#+Failure
fi|2074493|entityMap|0|LINK|mutability|MUTABLE|url|http://asymlabs.github.io/realpath-lib/^0|0|0|14|C|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@$I|X|J|Y|1|Z]]|A|$]]|$1|K|3|L|5|D|7|10|8|@]|9|@]|A|$E|F]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

Try something like this:
<pre><code>function get_realpath() {

if [[ -f &quot;$1&quot; ]]
then
 # The file *must* exist
 if cd &quot;$(echo &quot;${1%/*}&quot;)&quot; &amp;&gt;/dev/null
 then
 # The file *may* not be local.
 # The exception is ./file.ext
 # tTry 'cd .; cd -;' *works!*
 local tmppwd=&quot;$PWD&quot;
 cd - &amp;&gt;/dev/null
 else
 # file *must* be local
 local tmppwd=&quot;$PWD&quot;
 fi
else
 # The file *cannot* exist
 return 1 # Failure
fi

# Reassemble realpath
echo &quot;$tmppwd&quot;/&quot;${1##*/}&quot;
return 0 # Success

}

function get_dirname(){

local realpath=&quot;$(get_realpath &quot;$1&quot;)&quot;
if (( $? )) # True when non-zero.
then
 return $? # Failure
fi
echo &quot;${realpath%/*}&quot;
return 0 # Success

}

# Then from the top level:
get_dirname './script.sh'

# Or within a script:
get_dirname &quot;$0&quot;

# Can even test the outcome!
if (( $? )) # True when non-zero.
then
 exit 1 # Failure
fi
</code></pre>
These functions and related tools are part of our product that has been made available to the community for free and can be found at GitHub as <a href="http://asymlabs.github.io/realpath-lib/" rel="nofollow noreferrer">realpath-lib</a>. It's simple, clean and well documented (great for learning), pure Bash and has no dependencies. Good for cross-platform use too. So for the above example, within a script you could simply:
<pre><code>source '/path/to/realpath-lib'

get_dirname &quot;$0&quot;

if (( $? )) # True when non-zero.
then
 exit 1 # Failure
fi
</code></pre>

blocks|key|2074658|text|cur_dir=`old=\`pwd\`;+cd+\`dirname+$0\`;+echo+\`pwd\`;+cd+$old;`|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|2074659|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>cur_dir=`old=\`pwd\`; cd \`dirname $0\`; echo \`pwd\`; cd $old;`
</code></pre>

blocks|key|2074737|text|没有fork(除了subshell)，并且可以处理“外来”路径名形式，就像一些人声称的那样，带有换行符：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2074738|IFS=+read+-rd+''+DIR+<+<([[+$BASH_SOURCE+!=+*/*+]]+%7C%7C+cd+"${BASH_SOURCE%25/*}/"+>&-+&&+echo+-n+"$PWD")|code-block|syntax|javascript|2074739|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

No forks (besides subshell) and can handle "alien" pathname forms like those with newlines as some would claim:

<pre><code>IFS= read -rd '' DIR &lt; &lt;([[ $BASH_SOURCE != */* ]] || cd "${BASH_SOURCE%/*}/" &gt;&amp;- &amp;&amp; echo -n "$PWD")
</code></pre>

blocks|key|2074865|text|关键部分是我缩小了问题的范围:我禁止通过path间接执行脚本(就像在/bin/sh+[script+path+relative+to+path+component]中一样)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2074866|可以检测到这一点，因为$0将是一个相对路径，它不会解析到相对于当前文件夹的任何文件。我相信使用#!机制的直接执行总是会产生一个绝对的$0，包括在路径中找到脚本的时候。|2074867|我还要求路径名和符号链接链上的任何路径名只包含一个合理的字符子集，特别是不能包含\n、>、*或?。这是解析逻辑所必需的。|2074868|还有一些更隐含的期望，我将不会深入讨论(请看this+answer)，并且我不会尝试处理对$0的故意破坏(因此请考虑任何安全问题)。我希望这可以在几乎所有具有类似伯恩的/bin/sh的类Unix系统上工作。|2074869|#!/bin/sh
(
++++path="${0}"
++++while+test+-n+"${path}";+do
++++++++#+Make+sure+we+have+at+least+one+slash+and+no+leading+dash.
++++++++expr+"${path}"+:+/+>+/dev/null+%7C%7C+path="./${path}"
++++++++#+Filter+out+bad+characters+in+the+path+name.
++++++++expr+"${path}"+:+".*[*?<>\\]"+>+/dev/null+&&+exit+1
++++++++#+Catch+embedded+new-lines+and+non-existing+(or+path-relative)+files.
++++++++#+$0+should+always+be+absolute+when+scripts+are+invoked+through+"#!".
++++++++test+"`ls+-l+-d+"${path}"+2>+/dev/null+%7C+wc+-l`"+-eq+1+%7C%7C+exit+1
++++++++#+Change+to+the+folder+containing+the+file+to+resolve+relative+links.
++++++++folder=`expr+"${path}"+:+"$.*/$[%5E/][%5E/]*/*$"`+%7C%7C+exit+1
++++++++path=`expr+"x\`ls+-l+-d+"${path}"\`"+:+"[%5E>]*+->+$.*$"`
++++++++cd+"${folder}"
++++++++#+If+the+last+path+was+not+a+link+then+we+are+in+the+target+folder.
++++++++test+-n+"${path}"+%7C%7C+pwd
++++done
)|code-block|syntax|javascript|2074870|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/4794711/213180^0|Y|1C|0|B|2|1B|2|1U|2|0|14|2|17|1|19|1|1B|1|0|19|2|2C|7|M|B|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|11|8|@$9|12|A|13|B|C]|$9|14|A|15|B|C]|$9|16|A|17|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|18|8|@$9|19|A|1A|B|C]|$9|1B|A|1C|B|C]|$9|1D|A|1E|B|C]|$9|1F|A|1G|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|1H|8|@$9|1I|A|1J|B|C]|$9|1K|A|1L|B|C]]|D|@$9|1M|A|1N|1|1O]]|E|$]]|$1|L|3|M|5|N|7|1P|8|@]|D|@]|E|$O|P]]|$1|Q|3|-4|5|6|7|1Q|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X]]]]

The key part is that I am reducing the scope of the problem: I forbid indirect execution of the script via the path (as in <code>/bin/sh [script path relative to path component]</code>).
This can be detected because <code>$0</code> will be a relative path which does not resolve to any file relative to the current folder. I believe that direct execution using the <code>#!</code> mechanism always results in an absolute <code>$0</code>, including when the script is found on the path.
I also require that the pathname and any pathnames along a chain of symbolic links only contain a reasonable subset of characters, notably not <code>\n</code>, <code>&gt;</code>, <code>*</code> or <code>?</code>. This is required for the parsing logic.
There are a few more implicit expectations which I will not go into (look at <a href="https://stackoverflow.com/a/4794711/213180">this answer</a>), and I do not attempt to handle deliberate sabotage of <code>$0</code> (so consider any security implications). I expect this to work on almost any Unix-like system with a Bourne-like <code>/bin/sh</code>.
<pre><code>#!/bin/sh
(
 path=&quot;${0}&quot;
 while test -n &quot;${path}&quot;; do
 # Make sure we have at least one slash and no leading dash.
 expr &quot;${path}&quot; : / &gt; /dev/null || path=&quot;./${path}&quot;
 # Filter out bad characters in the path name.
 expr &quot;${path}&quot; : &quot;.*[*?&lt;&gt;\\]&quot; &gt; /dev/null &amp;&amp; exit 1
 # Catch embedded new-lines and non-existing (or path-relative) files.
 # $0 should always be absolute when scripts are invoked through &quot;#!&quot;.
 test &quot;`ls -l -d &quot;${path}&quot; 2&gt; /dev/null | wc -l`&quot; -eq 1 || exit 1
 # Change to the folder containing the file to resolve relative links.
 folder=`expr &quot;${path}&quot; : &quot;$.*/$[^/][^/]*/*$&quot;` || exit 1
 path=`expr &quot;x\`ls -l -d &quot;${path}&quot;\`&quot; : &quot;[^&gt;]* -&gt; $.*$&quot;`
 cd &quot;${folder}&quot;
 # If the last path was not a link then we are in the target folder.
 test -n &quot;${path}&quot; || pwd
 done
)
</code></pre>

blocks|key|2074973|text|基于this+answer，我建议将SCRIPT_HOME作为任何当前运行的Bash脚本的包含文件夹的澄清版本：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2074974|s=${BASH_SOURCE[0]}+;+s=`dirname+$s`+;+SCRIPT_HOME=`cd+$s+;+pwd`
echo+$SCRIPT_HOME|code-block|syntax|javascript|2074975|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/59895/can-a-bash-script-tell-which-directory-it-is-stored-in/246128#246128^0|I|B|2|B|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@$9|V|A|W|1|X]]|E|$]]|$1|F|3|G|5|H|7|Y|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|L|$M|$5|N|O|P|E|$Q|R]]]]

Based on <a href="https://stackoverflow.com/questions/59895/can-a-bash-script-tell-which-directory-it-is-stored-in/246128#246128">this answer</a>, I suggest the clarified version that gets <code>SCRIPT_HOME</code> as the containing folder of any currently-running Bash script:
<pre><code>s=${BASH_SOURCE[0]} ; s=`dirname $s` ; SCRIPT_HOME=`cd $s ; pwd`
echo $SCRIPT_HOME
</code></pre>

blocks|key|2075905|text|我想对上面的答案()进行评论，但我没有足够的名气来这么做。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2075906|两年前，我在苹果的文档网站上找到了一个解决方案：https://developer.apple.com/library/archive/documentation/OpenSource/Conceptual/ShellScripting/AdvancedTechniques/AdvancedTechniques.html。后来我坚持了这个方法。它不能处理软链接，但在其他方面对我来说很好。我在这里把它张贴给任何需要它的人，并作为一个评论的请求。|offset|length|2075907|#!/bin/sh

#+Get+an+absolute+path+for+the+poem.txt+file.
POEM="$PWD/../poem.txt"

#+Get+an+absolute+path+for+the+script+file.
SCRIPT="$(which+$0)"
if+[+"x$(echo+$SCRIPT+%7C+grep+'%5E\/')"+=+"x"+]+;+then
++++SCRIPT="$PWD/$SCRIPT"
fi|code-block|syntax|javascript|2075908|如代码所示，获取脚本的绝对路径后，可以使用dirname命令获取目录的路径。|style|CODE|2075909|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.apple.com/library/archive/documentation/OpenSource/Conceptual/ShellScripting/AdvancedTechniques/AdvancedTechniques.html|1|https://linux.die.net/man/1/dirname^0|0|O|3T|0|0|0|L|7|L|7|1|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@$D|10|E|11|1|12]]|A|$]]|$1|F|3|G|5|H|7|13|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|14|8|@$D|15|E|16|M|N]]|9|@$D|17|E|18|1|19]]|A|$]]|$1|O|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]|W|$5|R|S|T|A|$U|X]]]]

I want to comment on the previous answer up there (<a href="https://stackoverflow.com/questions/59895/how-can-i-get-the-source-directory-of-a-bash-script-from-within-the-script-itsel/201915#201915">How can I get the source directory of a Bash script from within the script itself?</a>), but don't have enough reputation to do that.
I found a solution for this two years ago on Apple's documentation site: <a href="https://developer.apple.com/library/archive/documentation/OpenSource/Conceptual/ShellScripting/AdvancedTechniques/AdvancedTechniques.html" rel="nofollow noreferrer">https://developer.apple.com/library/archive/documentation/OpenSource/Conceptual/ShellScripting/AdvancedTechniques/AdvancedTechniques.html</a>. And I stuck to this method afterwards. It cannot handle soft link, but otherwise works pretty well for me. I'm posting it here for any who needs it and as a request for comment.
<pre><code>#!/bin/sh

# Get an absolute path for the poem.txt file.
POEM=&quot;$PWD/../poem.txt&quot;

# Get an absolute path for the script file.
SCRIPT=&quot;$(which $0)&quot;
if [ &quot;x$(echo $SCRIPT | grep '^\/')&quot; = &quot;x&quot; ] ; then
 SCRIPT=&quot;$PWD/$SCRIPT&quot;
fi
</code></pre>
As shown by the code, after you get the absolute path of the script, then you can use the <a href="https://linux.die.net/man/1/dirname" rel="nofollow noreferrer"><code>dirname</code></a> command to get the path of the directory.

blocks|key|1862282|text|这是我多年来精心制作的，作为我的Bash脚本的标题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1862283|##+BASE+BRAIN+-+Get+where+you're+from+and+who+you+are.
MYPID=$$
ORIGINAL_DIR="$(pwd)"+#+This+is+not+a+hot+air+balloon+ride..
fa="$0"+#+First+Assumption
ta=+#+Temporary+Assumption
wa=+#+Weighed+Assumption
while+true;+do
++++[+"${fa:0:1}"+=+"/"+]+&&+wa=$0+&&+break
++++[+"${fa:0:2}"+=+"./"+]+&&+ta="${ORIGINAL_DIR}/${fa:2}"+&&+[+-e+"$ta"+]+&&+wa="$ta"+&&+break
++++ta="${ORIGINAL_DIR}/${fa}"+&&+[+-e+"$ta"+]+&&+wa="$ta"+&&+break
done
SW="$wa"
SWDIR="$(dirname+"$wa")"
SWBIN="$(basename+"$wa")"
unset+ta+fa+wa
(+[+!+-e+"$SWDIR/$SWBIN"+]+%7C%7C+[+-z+"$SW"+]+)+&&+echo+"I+could+not+find+my+way+around+:(+possible+bug+in+the+TOP+script"+&&+exit+1|code-block|syntax|javascript|1862284|此时，您的变量SW、SWDIR和SWBIN包含了所需的内容。|1862285|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

This is what I crafted throughout the years to use as a header on my Bash scripts:
<pre><code>## BASE BRAIN - Get where you're from and who you are.
MYPID=$$
ORIGINAL_DIR=&quot;$(pwd)&quot; # This is not a hot air balloon ride..
fa=&quot;$0&quot; # First Assumption
ta= # Temporary Assumption
wa= # Weighed Assumption
while true; do
 [ &quot;${fa:0:1}&quot; = &quot;/&quot; ] &amp;&amp; wa=$0 &amp;&amp; break
 [ &quot;${fa:0:2}&quot; = &quot;./&quot; ] &amp;&amp; ta=&quot;${ORIGINAL_DIR}/${fa:2}&quot; &amp;&amp; [ -e &quot;$ta&quot; ] &amp;&amp; wa=&quot;$ta&quot; &amp;&amp; break
 ta=&quot;${ORIGINAL_DIR}/${fa}&quot; &amp;&amp; [ -e &quot;$ta&quot; ] &amp;&amp; wa=&quot;$ta&quot; &amp;&amp; break
done
SW=&quot;$wa&quot;
SWDIR=&quot;$(dirname &quot;$wa&quot;)&quot;
SWBIN=&quot;$(basename &quot;$wa&quot;)&quot;
unset ta fa wa
( [ ! -e &quot;$SWDIR/$SWBIN&quot; ] || [ -z &quot;$SW&quot; ] ) &amp;&amp; echo &quot;I could not find my way around :( possible bug in the TOP script&quot; &amp;&amp; exit 1
</code></pre>
At this point, your variables SW, SWDIR, and SWBIN contain what you need.

blocks|key|2073725|text|我希望确保该脚本在其目录中运行。所以|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2073726|cd+$(dirname+$(which+$0)+)|code-block|syntax|javascript|2073727|在这之后，如果你真的想知道你在哪里运行，那么运行下面的命令。|2073728|DIR=$(/usr/bin/pwd)|2073729|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I want to make sure that the script is running in its directory. So

<pre><code>cd $(dirname $(which $0) )
</code></pre>

After this, if you really want to know where the you are running then run the command below.

<pre><code>DIR=$(/usr/bin/pwd)
</code></pre>

blocks|key|1861191|text|即使已使用bash+-c+<script>从Windows中调用脚本，此一行程序也可在Cygwin上运行|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1861192|set+mydir="$(cygpath+"$(dirname+"$0")")"|code-block|syntax|javascript|1861193|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Cygwin^0|5|G|17|6|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@$9|V|A|W|1|X]]|E|$]]|$1|F|3|G|5|H|7|Y|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|L|$M|$5|N|O|P|E|$Q|R]]]]

This one-liner works on <a href="https://en.wikipedia.org/wiki/Cygwin" rel="nofollow noreferrer">Cygwin</a> even if the script has been called from Windows with <code>bash -c &lt;script&gt;</code>:
<pre><code>set mydir=&quot;$(cygpath &quot;$(dirname &quot;$0&quot;)&quot;)&quot;
</code></pre>

blocks|key|1861819|text|没有100%25可移植和可靠的方法来请求当前脚本目录的路径。特别是在不同的后端之间，如Cygwin，MinGW，MSYS，Linux等，这个问题在Bash中很久没有得到正确和完全的解决。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1861820|例如，如果您想在source命令之后请求路径以嵌套包含另一个Bash脚本，则无法解决此问题，而该脚本又使用相同的source命令来包含另一个Bash脚本，依此类推。|style|CODE|1861821|在使用source命令的情况下，我建议将source命令替换为以下内容：|1861822|function+include()
{
++if+[[+-n+"$CURRENT_SCRIPT_DIR"+]];+then
++++local+dir_path=...+get+directory+from+`CURRENT_SCRIPT_DIR/$1`,+depends+if+$1+is+absolute+path+or+relative+...
++++local+include_file_path=...
++else
++++local+dir_path=...+request+the+directory+from+the+"$1"+argument+using+one+of+answered+here+methods...
++++local+include_file_path=...
++fi
++...+push+$CURRENT_SCRIPT_DIR+in+to+stack+...
++export+CURRENT_SCRIPT_DIR=...+export+current+script+directory+using+$dir_path+...
++source+"$include_file_path"
++...+pop+$CURRENT_SCRIPT_DIR+from+stack+...
}|code-block|syntax|javascript|1861823|从现在开始，include(...)的使用将基于脚本中以前的CURRENT_SCRIPT_DIR。|1861824|只有当您可以用include命令替换所有source命令时，这才有效。如果你做不到，那你就别无选择。至少在Bash解释器的开发人员发出显式命令来请求当前运行的脚本目录路径之前是这样。|1861825|我自己最接近这一点的实现：https://sourceforge.net/p/tacklelib/tacklelib/HEAD/tree/trunk/bash/tacklelib/bash_tacklelib|1861826|(搜索tkl_include函数)|1861827|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Cygwin|1|https://en.wikipedia.org/wiki/MinGW|2|https://en.wikipedia.org/wiki/MinGW#History|3|https://linux.die.net/man/1/source|4|https://sourceforge.net/p/tacklelib/tacklelib/HEAD/tree/trunk/bash/tacklelib/bash_tacklelib^0|15|6|0|1C|5|1|1I|4|2|0|8|6|1K|6|0|3|6|K|6|3|6|3|0|0|6|C|U|I|0|7|7|K|6|0|D|2J|4|0|3|B|0^^$0|@$1|2|3|4|5|6|7|1C|8|@]|9|@$A|1D|B|1E|1|1F]|$A|1G|B|1H|1|1I]|$A|1J|B|1K|1|1L]]|C|$]]|$1|D|3|E|5|6|7|1M|8|@$A|1N|B|1O|F|G]|$A|1P|B|1Q|F|G]]|9|@]|C|$]]|$1|H|3|I|5|6|7|1R|8|@$A|1S|B|1T|F|G]|$A|1U|B|1V|F|G]]|9|@$A|1W|B|1X|1|1Y]]|C|$]]|$1|J|3|K|5|L|7|1Z|8|@]|9|@]|C|$M|N]]|$1|O|3|P|5|6|7|20|8|@$A|21|B|22|F|G]|$A|23|B|24|F|G]]|9|@]|C|$]]|$1|Q|3|R|5|6|7|25|8|@$A|26|B|27|F|G]|$A|28|B|29|F|G]]|9|@]|C|$]]|$1|S|3|T|5|6|7|2A|8|@]|9|@$A|2B|B|2C|1|2D]]|C|$]]|$1|U|3|V|5|6|7|2E|8|@$A|2F|B|2G|F|G]]|9|@]|C|$]]|$1|W|3|-4|5|6|7|2H|8|@]|9|@]|C|$]]]|X|$Y|$5|Z|10|11|C|$12|13]]|14|$5|Z|10|11|C|$12|15]]|16|$5|Z|10|11|C|$12|17]]|18|$5|Z|10|11|C|$12|19]]|1A|$5|Z|10|11|C|$12|1B]]]]

There is no 100% portable and reliable way to request a path to a current script directory. Especially between different backends like <a href="https://en.wikipedia.org/wiki/Cygwin" rel="nofollow noreferrer">Cygwin</a>, <a href="https://en.wikipedia.org/wiki/MinGW" rel="nofollow noreferrer">MinGW</a>, <a href="https://en.wikipedia.org/wiki/MinGW#History" rel="nofollow noreferrer">MSYS</a>, Linux, etc. This issue was not properly and completely resolved in Bash for ages.
For example, this could not be resolved if you want to request the path after the <code>source</code> command to make nested inclusion of another Bash script which is in turn use the same <code>source</code> command to include another Bash script and so on.
In case of the <a href="https://linux.die.net/man/1/source" rel="nofollow noreferrer"><code>source</code></a> command, I suggest to replace the <code>source</code> command with something like this:
<pre><code>function include()
{
 if [[ -n &quot;$CURRENT_SCRIPT_DIR&quot; ]]; then
 local dir_path=... get directory from `CURRENT_SCRIPT_DIR/$1`, depends if $1 is absolute path or relative ...
 local include_file_path=...
 else
 local dir_path=... request the directory from the &quot;$1&quot; argument using one of answered here methods...
 local include_file_path=...
 fi
 ... push $CURRENT_SCRIPT_DIR in to stack ...
 export CURRENT_SCRIPT_DIR=... export current script directory using $dir_path ...
 source &quot;$include_file_path&quot;
 ... pop $CURRENT_SCRIPT_DIR from stack ...
}
</code></pre>
From now on, the use of <code>include(...)</code> is based on previous <code>CURRENT_SCRIPT_DIR</code> in your script.
This only works when you can replace all <code>source</code> commands by <code>include</code> command. If you can't, then you have no choice. At least until developers of the Bash interpreter make an explicit command to request the current running script directory path.
My own closest implementation to this:
<a href="https://sourceforge.net/p/tacklelib/tacklelib/HEAD/tree/trunk/bash/tacklelib/bash_tacklelib" rel="nofollow noreferrer">https://sourceforge.net/p/tacklelib/tacklelib/HEAD/tree/trunk/bash/tacklelib/bash_tacklelib</a>
(search for the <code>tkl_include</code> function)

blocks|key|1861603|text|chosen+answer运行得非常好。我将我的解决方案发布给那些寻找更短的替代方案的人，这些替代方案仍然可以解决源、执行、完整路径、相对路径和符号链接等问题。最后，这将在macOS上工作，因为不能假设GNU版本的readlink是可用的。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1861604|问题是它没有使用Bash，但它很容易在Bash脚本中使用。虽然OP没有对解决方案的语言施加任何限制，但最好是大多数都留在Bash世界中。这只是一种选择，可能是一种不受欢迎的选择。|1861605|默认情况下，PHP在macOS上可用，并安装在许多其他平台上，但在默认情况下不一定如此。我知道这是一个缺点，但无论如何，我会把这个留给任何来自搜索引擎的人。|1861606|export+SOURCE_DIRECTORY="$(php+-r+'echo+dirname(realpath($argv[1]));'+--+"${BASH_SOURCE[0]}")"|code-block|syntax|javascript|1861607|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/59895/how-can-i-get-the-source-directory-of-a-bash-script-from-within-the-script-itsel/246128#246128|1|https://en.wikipedia.org/wiki/MacOS|2|https://linux.die.net/man/1/readlink^0|0|D|0|2E|5|1|2Z|8|2|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]|$A|12|B|13|1|14]|$A|15|B|16|1|17]]|C|$]]|$1|D|3|E|5|6|7|18|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|19|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|1A|8|@]|9|@]|C|$K|L]]|$1|M|3|-4|5|6|7|1B|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]|U|$5|P|Q|R|C|$S|V]]|W|$5|P|Q|R|C|$S|X]]]]

The <a href="https://stackoverflow.com/questions/59895/how-can-i-get-the-source-directory-of-a-bash-script-from-within-the-script-itsel/246128#246128">chosen answer</a> works very well. I'm posting my solution for anyone looking for shorter alternatives that still addresses sourcing, executing, full paths, relative paths, and symlinks. Finally, this will work on <a href="https://en.wikipedia.org/wiki/MacOS" rel="nofollow noreferrer">macOS</a>, given that it cannot be assumed that GNU's coreutils' version of <a href="https://linux.die.net/man/1/readlink" rel="nofollow noreferrer">readlink</a> is available.
The gotcha is that it's not using Bash, but it is easy to use in a Bash script. While the OP did not place any constraints on the language of the solution, it's probably best that most have stayed within the Bash world. This is just an alternative, and possibly an unpopular one.
PHP is available on macOS by default, and installed on a number of other platforms, though not necessarily by default. I realize this is a shortcoming, but I'll leave this here for any people coming from search engines, anyway.
<pre class="lang-bash prettyprint-override"><code>export SOURCE_DIRECTORY=&quot;$(php -r 'echo dirname(realpath($argv[1]));' -- &quot;${BASH_SOURCE[0]}&quot;)&quot;
</code></pre>

blocks|key|2076113|text|保持简单。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2076114|#!/usr/bin/env+bash
sourceDir=`pwd`
echo+$sourceDir|code-block|syntax|javascript|2076115|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Keep it simple.

<pre><code>#!/usr/bin/env bash
sourceDir=`pwd`
echo $sourceDir
</code></pre>

blocks|key|1860929|text|FOLDERNAME=${PWD##*/}|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1860930|这是我知道的最快的方法。|unstyled|1860931|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|J|8|@]|9|@]|A|$]]|$1|G|3|-4|5|F|7|K|8|@]|9|@]|A|$]]]|H|$]]

<pre><code>FOLDERNAME=${PWD##*/}
</code></pre>
That is the quickest way I know.

How do I get the path of the directory in which a <a href="http://en.wikipedia.org/wiki/Bash_%28Unix_shell%29" rel="noreferrer">Bash</a> script is located, inside that script?
I want to use a Bash script as a launcher for another application. I want to change the working directory to the one where the Bash script is located, so I can operate on the files in that directory, like so:
<pre><code>$ ./application
</code></pre>

How can I get the source directory of a Bash script from within the script itself?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

如何在脚本中获取该脚本所在目录的路径？我想使用Bash脚本作为另一个应用程序的启动器。我想将工作目录更改为Bash脚本所在的目录，这样我就可以对该目录中的文件进行操作，如下所示：$ ./application

问如何从脚本内部获取Bash脚本的源目录？
EN

回答 59

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何从脚本内部获取Bash脚本的源目录？EN

回答 59

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何从脚本内部获取Bash脚本的源目录？
EN