blocks|key|2503587|text|您可以使用来自special+builds+page的替代NSIS构建，比如定义NSIS_MAX_STRLEN=8192的large+strings+build，它应该可以防止您破坏主机路径。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2503588|实际上，在台式机上，1024字节似乎足够了，但在安装了许多工具的开发主机上(比如我的)，路径在操作后可能会中断，而构建的8192字节的字符串从未扰乱过我的机器。|2503589|为了非常确定，您可以在操作之前添加对路径长度的检查，并在路径接近NSIS_MAX_STRLEN常量的情况下尝试操作它之前中止安装程序并显示一条消息。|2503590|entityMap|0|LINK|mutability|MUTABLE|url|http://nsis.sourceforge.net/Special_Builds|1|http://nsis.sourceforge.net/Special_Builds#Large_strings^0|14|K|7|J|0|1P|J|1|0|0|W|F|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@$9|W|A|X|1|Y]|$9|Z|A|10|1|11]]|E|$]]|$1|F|3|G|5|6|7|12|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|13|8|@$9|14|A|15|B|C]]|D|@]|E|$]]|$1|J|3|-4|5|6|7|16|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]|R|$5|M|N|O|E|$P|S]]]]

You can use an alternative NSIS build from the <a href="http://nsis.sourceforge.net/Special_Builds" rel="noreferrer">special builds page</a> like the <a href="http://nsis.sourceforge.net/Special_Builds#Large_strings" rel="noreferrer">large strings build</a> that defines <code>NSIS_MAX_STRLEN=8192</code> and should prevent you from breaking the host path.

In practice, on a desktop machine, 1024 byte seems enough, but on a development host with many tools installed (like mine), the path might be broken after manipulation, while the 8192 bytes strings build had never perturbed my machine.

To be very sure, you can add a check on the path length before manipulation and abort the installer with a message in the case where the path would be close to the <code>NSIS_MAX_STRLEN</code> constant before trying to manipulate it.

blocks|key|2713593|text|真正的解决方案是编写一个自定义插件或直接使用系统插件调用Windows+API，这样就可以避免NSIS缓冲区长度限制：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2713594|!include+LogicLib.nsh
!include+WinCore.nsh
!ifndef+NSIS_CHAR_SIZE
!define+NSIS_CHAR_SIZE+1
!endif

Function+RegAppendString
System::Store+S
Pop+$R0+;+append
Pop+$R1+;+separator
Pop+$R2+;+reg+value
Pop+$R3+;+reg+path
Pop+$R4+;+reg+hkey
System::Call+'ADVAPI32::RegCreateKey(i$R4,tR3,*i.r1)i.r0'
${If}+$0+=+0
++++System::Call+'ADVAPI32::RegQueryValueEx(ir1,tR2,i0,*i.r2,i0,*i0r3)i.r0'
++++${If}+$0+<>+0
++++++++StrCpy+$2+${REG_SZ}
++++++++StrCpy+$3+0
++++${EndIf}
++++StrLen+$4+$R0
++++StrLen+$5+$R1
++++IntOp+$4+$4+%2B+$5
++++IntOp+$4+$4+%2B+1+;+For+\0
++++!if+${NSIS_CHAR_SIZE}+>+1
++++++++IntOp+$4+$4+*+${NSIS_CHAR_SIZE}
++++!endif
++++IntOp+$4+$4+%2B+$3
++++System::Alloc+$4
++++System::Call+'ADVAPI32::RegQueryValueEx(ir1,tR2,i0,i0,isr9,*ir4r4)i.r0'
++++${If}+$0+=+0
++++${OrIf}+$0+=+${ERROR_FILE_NOT_FOUND}
++++++++System::Call+'KERNEL32::lstrlen(t)(ir9)i.r0'
++++++++${If}+$0+<>+0
++++++++++++System::Call+'KERNEL32::lstrcat(t)(ir9,tR1)'
++++++++${EndIf}
++++++++System::Call+'KERNEL32::lstrcat(t)(ir9,tR0)'
++++++++System::Call+'KERNEL32::lstrlen(t)(ir9)i.r0'
++++++++IntOp+$0+$0+%2B+1
++++++++!if+${NSIS_CHAR_SIZE}+>+1
++++++++++++IntOp+$0+$0+*+${NSIS_CHAR_SIZE}
++++++++!endif
++++++++System::Call+'ADVAPI32::RegSetValueEx(ir1,tR2,i0,ir2,ir9,ir0)i.r0'
++++${EndIf}
++++System::Free+$9
++++System::Call+'ADVAPI32::RegCloseKey(ir1)'
${EndIf}
Push+$0
System::Store+L
FunctionEnd

Section

Push+${HKEY_CURRENT_USER}
Push+"Environment"
Push+"Path"
Push+";"
Push+"c:\whatever"
Call+RegAppendString
Pop+$0
DetailPrint+RegAppendString:Error=$0

SectionEnd+|code-block|syntax|javascript|2713595|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|$]]

The real solution is to write a custom plugin or call the Windows API directly with the system plugin so you can avoid the NSIS buffer length limitation:

<pre><code>!include LogicLib.nsh
!include WinCore.nsh
!ifndef NSIS_CHAR_SIZE
!define NSIS_CHAR_SIZE 1
!endif

Function RegAppendString
System::Store S
Pop $R0 ; append
Pop $R1 ; separator
Pop $R2 ; reg value
Pop $R3 ; reg path
Pop $R4 ; reg hkey
System::Call 'ADVAPI32::RegCreateKey(i$R4,tR3,*i.r1)i.r0'
${If} $0 = 0
 System::Call 'ADVAPI32::RegQueryValueEx(ir1,tR2,i0,*i.r2,i0,*i0r3)i.r0'
 ${If} $0 &lt;&gt; 0
 StrCpy $2 ${REG_SZ}
 StrCpy $3 0
 ${EndIf}
 StrLen $4 $R0
 StrLen $5 $R1
 IntOp $4 $4 + $5
 IntOp $4 $4 + 1 ; For \0
 !if ${NSIS_CHAR_SIZE} &gt; 1
 IntOp $4 $4 * ${NSIS_CHAR_SIZE}
 !endif
 IntOp $4 $4 + $3
 System::Alloc $4
 System::Call 'ADVAPI32::RegQueryValueEx(ir1,tR2,i0,i0,isr9,*ir4r4)i.r0'
 ${If} $0 = 0
 ${OrIf} $0 = ${ERROR_FILE_NOT_FOUND}
 System::Call 'KERNEL32::lstrlen(t)(ir9)i.r0'
 ${If} $0 &lt;&gt; 0
 System::Call 'KERNEL32::lstrcat(t)(ir9,tR1)'
 ${EndIf}
 System::Call 'KERNEL32::lstrcat(t)(ir9,tR0)'
 System::Call 'KERNEL32::lstrlen(t)(ir9)i.r0'
 IntOp $0 $0 + 1
 !if ${NSIS_CHAR_SIZE} &gt; 1
 IntOp $0 $0 * ${NSIS_CHAR_SIZE}
 !endif
 System::Call 'ADVAPI32::RegSetValueEx(ir1,tR2,i0,ir2,ir9,ir0)i.r0'
 ${EndIf}
 System::Free $9
 System::Call 'ADVAPI32::RegCloseKey(ir1)'
${EndIf}
Push $0
System::Store L
FunctionEnd

Section

Push ${HKEY_CURRENT_USER}
Push "Environment"
Push "Path"
Push ";"
Push "c:\whatever"
Call RegAppendString
Pop $0
DetailPrint RegAppendString:Error=$0

SectionEnd 
</code></pre>

blocks|key|2503623|text|我已经编写了NSIS+3.0示例来处理超过限制的情况，并且不需要安装任何东西。这里回答了这个问题：Set+environment+variables+with+NSIS+in+Window+7|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2503624|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/42909177/6951728^0|1D|1B|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I have been wrote the NSIS 3.0 example to handle cases longer than the limit and without a need to install anything. Answered the question here: <a href="https://stackoverflow.com/a/42909177/6951728">Set environment variables with NSIS in Window 7</a>

blocks|key|37168|text|我更喜欢通过NSIS+nsExec::Exec命令使用windows命令处理器(cmd.exe)，它允许您轻松地添加到PATH，如下所示：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|37169|;+Check+if+the+path+entry+already+exists+and+write+result+to+$0
nsExec::Exec+'echo+%25PATH%25+%7C+find+"c:\some\new\dir"'
Pop+$0+++;+gets+result+code

${If}+$0+=+0
++++nsExec::Exec+'setx+PATH=%25PATH%25;c:\some\new\dir'
${EndIf}|code-block|syntax|javascript|37170|使用此方法，CMD.EXE在内部扩展PATH变量，不受任何NSIS字符串长度限制。或者，如果您希望您的程序首先被提取，则更改%25PATH%25标记粘贴的顺序，然后使用相同的名称获取系统上可能安装的所有其他内容：|37171|++++nsExec::Exec+'setx+PATH=c:\some\new\dir;%25PATH%25'|37172|请注意，在构建新的PATH时，不要使用双引号，这一点很重要。命令处理程序永远不会在路径字符串中使用双引号，如果您添加了任何双引号，命令处理程序可能会以意外的方式运行。它仅使用分号(;)分隔路径。|37173|另请注意，此方法依赖于作为explained+by+Seki+in+his+answer的large+strings+build。|37174|nsExec::Exec与ExecWait的不同之处在于，它在内部运行，不会弹出额外的可视命令提示窗口。|37175|entityMap|0|LINK|mutability|MUTABLE|url|http://nsis.sourceforge.net/Special_Builds#Large_strings|1|https://stackoverflow.com/a/31341378/786437^0|B|C|14|7|1N|4|0|0|6|7|I|4|1Q|6|0|0|9|4|2I|1|0|D|V|0|19|J|1|0|0|C|D|8|0^^$0|@$1|2|3|4|5|6|7|14|8|@$9|15|A|16|B|C]|$9|17|A|18|B|C]|$9|19|A|1A|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|1B|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|1C|8|@$9|1D|A|1E|B|C]|$9|1F|A|1G|B|C]|$9|1H|A|1I|B|C]]|D|@]|E|$]]|$1|M|3|N|5|H|7|1J|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|1K|8|@$9|1L|A|1M|B|C]|$9|1N|A|1O|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1P|8|@]|D|@$9|1Q|A|1R|1|1S]|$9|1T|A|1U|1|1V]]|E|$]]|$1|S|3|T|5|6|7|1W|8|@$9|1X|A|1Y|B|C]|$9|1Z|A|20|B|C]]|D|@]|E|$]]|$1|U|3|-4|5|6|7|21|8|@]|D|@]|E|$]]]|V|$W|$5|X|Y|Z|E|$10|11]]|12|$5|X|Y|Z|E|$10|13]]]]

I prefer using windows command processor (<code>cmd.exe</code>) via the NSIS <code>nsExec::Exec</code> command, which allows you to append to the <code>PATH</code> easily like so:

<pre><code>; Check if the path entry already exists and write result to $0
nsExec::Exec 'echo %PATH% | find "c:\some\new\dir"'
Pop $0 ; gets result code

${If} $0 = 0
 nsExec::Exec 'setx PATH=%PATH%;c:\some\new\dir'
${EndIf}
</code></pre>

Using this method, <code>CMD.EXE</code> expands the <code>PATH</code> variable internally, safe from any NSIS string length limits. Alternatively, change the order of <code>%PATH%</code> token pasting if you want your program to be picked up first, ahead of anything and everything else that might be installed on the system by the same name:

<pre><code> nsExec::Exec 'setx PATH=c:\some\new\dir;%PATH%'
</code></pre>

Note that it's important not to include double-quotes while building the new <code>PATH</code>. The command processor never expects double-quotes in the PATH string and may behave in unexpected ways if you add any. It delimits paths by semicolon (<code>;</code>) only.

Also note that this methods depends on the <a href="https://stackoverflow.com/a/31341378/786437">large strings build</a> as <a href="http://nsis.sourceforge.net/Special_Builds#Large_strings" rel="nofollow noreferrer">explained by Seki in his answer</a>.

<code>nsExec::Exec</code> differs from <code>ExecWait</code> in that it runs internally, without popping up additional visible cmd prompt windows.

blocks|key|37208|text|我对NSIS中所有复杂的插件和字符限制感到沮丧，所以我写了一个名为PathEd的小应用程序来解决所有这些问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|37209|​|37210|📷|atomic|offset|length|37211|37212|它被设计成在你的安装程序中部署，并且可以像这样从它的部署位置调用，例如：|37213|PathEd.exe+add+"C:\Program+Files\RepoZ"或PathEd.exe+remove+"C:\Program+Files\RepoZ"|style|CODE|37214|PathEd负责分号处理、避免重复、不区分大小写检查、用户帐户控制提示、参数引用处理、安全和防御值删除等。|37215|请随意使用它。不过，别忘了在GitHub上给它打个星。|37216|请参阅https://github.com/awaescher/PathEd|37217|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/5617381a6068d45573c6140786dca4e7.png|imageAlt|1|LINK|MUTABLE|url|https://github.com/awaescher/PathEd^0|0|0|0|1|0|0|0|0|0|13|14|16|0|0|0|3|Z|1|0^^$0|@$1|2|3|4|5|6|7|19|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1A|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1B|8|@]|9|@$G|1C|H|1D|1|1E]]|A|$]]|$1|I|3|C|5|6|7|1F|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1G|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1H|8|@$G|1I|H|1J|N|O]|$G|1K|H|1L|N|O]]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1M|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1N|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1O|8|@]|9|@$G|1P|H|1Q|1|1R]]|A|$]]|$1|V|3|-4|5|6|7|1S|8|@]|9|@]|A|$]]]|W|$X|$5|Y|Z|10|A|$11|12|13|-4]]|14|$5|15|Z|16|A|$17|18]]]]

I was frustrated looking at all the complicated plugins and char limitations with the NSIS stuff so I wrote a tiny little application called PathEd to take care of all.

<a href="https://i.stack.imgur.com/I4OqU.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/I4OqU.png" alt="PathEd.exe"></a>

It is designed to be deployed within your installer and can be called from its deploy location like this, for example:

<code>PathEd.exe add "C:\Program Files\RepoZ"</code>
or
<code>PathEd.exe remove "C:\Program Files\RepoZ"</code>

PathEd takes care of the semicolon handling, duplicate avoidance, case-insensitive checks, user account control prompts, argument quote handling, safe and defensive value removal and so on.

Feel free to use it. But then, don't forget to give it a star on GitHub. 

See <a href="https://github.com/awaescher/PathEd" rel="nofollow noreferrer">https://github.com/awaescher/PathEd</a>

I've read that &quot;Strings longer than ${NSIS_MAX_STRLEN} (1024) will get truncated/corrupted.&quot;
How can I safely update <code>%PATH%</code> environment variable?

Update %PATH% environment variable using NSIS

Windows

GitHub

我读过这样一篇文章：“字符串长度超过${NSIS_MAX_STRLEN} (1024)将被截断/损坏。”如何安全地更新%PATH%环境变量? How I safely %PATH% environment variable？

问使用NSIS更新%PATH%环境变量
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用NSIS更新%PATH%环境变量EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用NSIS更新%PATH%环境变量
EN