blocks|key|699537|text|像这样执行它："$VAR"。这是shell脚本中最重要的陷阱之一，因为字符串总是按字面意思替换，任何包含的空格都被视为令牌分隔符，而不是字符串的字符。可以将变量替换为一种在运行时粘贴的代码。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|699538|当您编写$VAR时，实际发生的情况是，shell尝试执行带有第一个参数Files/TortoiseGit/bin/TortoisePlink.exe的二进制/c/Program。|699539|我通过在一个大型shell脚本中为一个特定的输入得到一个奇怪的语法错误，以一种艰难的方式了解到这一点。如果运行时输入包含特殊字符，我能想到的其他语言都不会抱怨语法错误-但这是shell脚本的本质，因为像bash和sh这样的命令解释器逐行解释代码。|699540|每当您希望字符串包含空格，并且不想将其视为单独的标记时，请将其括在双引号中。|699541|entityMap^0|7|6|0|4|4|Z|13|26|A|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@$9|R|A|S|B|C]|$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|X|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|Y|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|M|$]]

Execute it like this: <code>"$VAR"</code>. This is one of the most significant gotchas in shell scripting because strings are always substituted literally and any contained spaces are treated as token delimiters rather than as characters of the string. Think of substituting a variable as a kind of code pasting at runtime.

What really happens when you write <code>$VAR</code> is that the shell tries to execute the binary <code>/c/Program</code> with a first argument <code>Files/TortoiseGit/bin/TortoisePlink.exe</code>.

I learned this the hard way by getting a strange syntax error in a big shell script for a particular input. No other languages I can think of can complain for syntax errors if the runtime input contains special characters - but that is the nature of shell scripting since command interpreters like bash and sh interpret the code line by line.

Whenever you expect a string to contain spaces and you don't want to treat it as separate tokens, enclose it in double quotes.

blocks|key|915701|text|作为参考，我在osx上解决了一个类似的问题，用转义引号封装了参数。这可能不是最好的解决方案，但它似乎是有效的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|915702|alias+sub="\"/Applications/Sublime+Text+2.app/Contents/SharedSupport/bin/subl\""|code-block|syntax|javascript|915703|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|$]]

For reference, I solved a similar issue on osx by encapsulating the argument with escaped quotations. This may not be the best solution, but it seems to work.

<pre><code>alias sub="\"/Applications/Sublime Text 2.app/Contents/SharedSupport/bin/subl\""
</code></pre>

I'm facing the next problem in MinGW shell under windows. I have in my <code>/etc/profile</code> the expression:

<pre><code>export GIT_SSH="/c/Program Files/TortoiseGit/bin/TortoisePlink.exe"
</code></pre>

This doesn't work when I use <code>git fetch</code> on the local repository. But if I do it like this (old DOS way), it works:

<pre><code>export GIT_SSH="/c/Progra~1/TortoiseGit/bin/TortoisePlink.exe"
</code></pre>

My question is:

How can I make it work using spaces in the variable? 

For testing purpose you can simulate something like this (any example is good):

<pre><code>export VAR="/c/Program Files/TortoiseGit/bin/TortoisePlink.exe"
# and try to execute like this
$VAR
</code></pre>

Is there a solution for this (other than the previous mentioned)?

Bash variables with spaces

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我正面临着windows下的MinGW shell的下一个问题。我的/etc/profile中有这样一个表达式：export GIT_SSH="/c/Program Files/TortoiseGit/bin/TortoisePlink.exe"当我在本地存储库上使用git fetch时，这不起作用。但是如果我这样做(...

问带空格的Bash变量
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问带空格的Bash变量EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问带空格的Bash变量
EN