blocks|key|54392|text|您可以像上面的Windows示例那样引用它，或者用反斜杠转义空格：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|54393|+"/foo+folder+with+space/foo"+--help
+/foo\+folder\+with\+space/foo+--help|code-block|syntax|javascript|54394|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|$]]

You can either quote it like your Windows example above, or escape the spaces with backslashes:

<pre><code> "/foo folder with space/foo" --help
 /foo\ folder\ with\ space/foo --help
</code></pre>

blocks|key|54374|text|如果愿意，可以引用，也可以用前面的\来转义空格，但是大多数UNIX路径(Mac除外)中没有空格。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|54375|/Applications/Image\+Capture.app/Contents/MacOS/Image\+Capture

"/Applications/Image+Capture.app/Contents/MacOS/Image+Capture"

/Applications/"Image+Capture.app"/Contents/MacOS/"Image+Capture"|code-block|syntax|javascript|54376|在Mac下，所有文件都引用相同的可执行文件。|54377|我不确定识别路径是什么意思--如果将上述任何路径作为参数传递给程序，shell将把整个字符串放入一个变量中--您不必解析多个参数才能得到整个路径。|54378|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|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

You can quote if you like, or you can escape the spaces with a preceding \, but most UNIX paths (Mac OS X aside) don't have spaces in them.

<pre><code>/Applications/Image\ Capture.app/Contents/MacOS/Image\ Capture

"/Applications/Image Capture.app/Contents/MacOS/Image Capture"

/Applications/"Image Capture.app"/Contents/MacOS/"Image Capture"
</code></pre>

All refer to the same executable under Mac OS X.

I'm not sure what you mean about recognizing a path - if any of the above paths are passed as a parameter to a program the shell will put the entire string in one variable - you don't have to parse multiple arguments to get the entire path.

blocks|key|54121|text|由于空格用于分隔命令行参数，因此它们必须从shell中转义。这可以通过反斜杠()或引号来完成：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|54122|"/path/with/spaces+in+it/to/a/file"
somecommand+-spaced\+option
somecommand+"-spaced+option"
somecommand+'-spaced+option'|code-block|syntax|javascript|54123|这是假设你是在逃避一个外壳。如果您正在编写代码，通常可以直接传递参数，从而避免问题：|54124|perl中的示例。而不是做：|54125|print("code+sample");系统(“-spaced选项”)；|offset|length|style|CODE|54126|你可以做到|54127|print("code+sample");系统(“somecommand”、"-spaced选项“)；|54128|因为当您传递system()调用列表时，它不会像单个参数调用那样破坏空格上的参数。|54129|entityMap^0|0|0|0|0|0|L|0|0|0|L|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|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|11|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|12|8|@$M|13|N|14|O|P]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|15|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|16|8|@$M|17|N|18|O|P]]|9|@]|A|$]]|$1|U|3|V|5|6|7|19|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|X|$]]

Since spaces are used to separate command line arguments, they have to be escaped from the shell. This can be done with either a backslash () or quotes:

<pre><code>"/path/with/spaces in it/to/a/file"
somecommand -spaced\ option
somecommand "-spaced option"
somecommand '-spaced option'
</code></pre>

This is assuming you're running from a shell. If you're writing code, you can usually pass the arguments directly, avoiding the problem:

Example in perl. Instead of doing:

<code>print("code sample");</code>system("somecommand -spaced option");

you can do

<code>print("code sample");</code>system("somecommand", "-spaced option");

Since when you pass the system() call a list, it doesn't break arguments on spaces like it does with a single argument call.

blocks|key|54412|text|也要小心双引号--在Unix上，这会扩展变量。有些是显而易见的(比如$foo和\t)，但有些则不是(比如!foo)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|54413|为安全起见，请使用单引号！|54414|entityMap^0|Y|4|13|2|1G|4|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]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|R|8|@]|D|@]|E|$]]]|I|$]]

Also be careful with double-quotes -- on the Unix shell this expands variables. Some are obvious (like <code>$foo</code> and <code>\t</code>) but some are not (like <code>!foo</code>). 

For safety, use single-quotes!

blocks|key|54109|text|您可以引用窗口中的整个路径，也可以转义空格，如：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|54110|/foo\+folder\+with\+space/foo.sh+-help|code-block|syntax|javascript|54111|这两种方式都会奏效！|54112|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|$]]

You can quote the entire path as in windows or you can escape the spaces like in: 

<pre><code>/foo\ folder\ with\ space/foo.sh -help
</code></pre>

Both ways will work!

blocks|key|179460|text|我还想指出，如果您使用命令行参数作为shell脚本(.sh文件)的一部分，那么在脚本中，需要将参数用引号括起来。所以如果你的命令看起来像|type|unstyled|depth|inlineStyleRanges|entityRanges|data|179461|>scriptName.sh+arg1+arg2|code-block|syntax|javascript|179462|arg1是有空格的路径，那么在shell脚本中，您需要将它称为"+$arg1“而不是$arg1|179463|Here+are+the+details|offset|length|179464|entityMap|0|LINK|mutability|MUTABLE|url|https://unix.stackexchange.com/questions/131766/why-does-my-shell-script-choke-on-whitespace-or-other-special-characters^0|0|0|0|0|K|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]]]]

I would also like to point out that in case you are using command line arguments as part of a shell script (.sh file), then within the script, you would need to enclose the argument in quotes. So if your command looks like

<pre><code>&gt;scriptName.sh arg1 arg2
</code></pre>

And arg1 is your path that has spaces, then within the shell script, you would need to refer to it as "$arg1" instead of $arg1

<a href="https://unix.stackexchange.com/questions/131766/why-does-my-shell-script-choke-on-whitespace-or-other-special-characters">Here are the details</a>

blocks|key|179442|text|如果正常的方法不起作用，尝试用%2520替换空格。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|179443|在处理SSH和其他域样式的命令(如auto_smb+)时，这对我起了作用。|179444|entityMap^0|F|3|0|H|8|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

If the normal ways don't work, trying substituting spaces with <code>%20</code>.

This worked for me when dealing with SSH and other domain-style commands like <code>auto_smb</code>.

How does unix handle full path name with space and arguments ? 
In windows we quote the path and add the command-line arguments after, how is it in unix?

<pre><code> "c:\foo folder with space\foo.exe" -help
</code></pre>

update:

I meant how do I recognize a path from the command line arguments.

how does unix handle full path name with space and arguments?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

unix如何处理带空格和参数的完整路径名称？在windows中，我们引用路径并在之后添加命令行参数，在unix中如何？ "c:\foo folder with space\foo.exe" -help更新：我的意思是如何从命令行参数中识别路径。

问unix如何处理带空格和参数的完整路径名称？
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问unix如何处理带空格和参数的完整路径名称？EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问unix如何处理带空格和参数的完整路径名称？
EN