Am 30.03.2014 23:57, schrieb Uwe Stöhr:
Am 30.03.2014 22:13, schrieb Vincent van Ravesteijn:
Yes, it works.
Great. However, NSIS gets now permanently broken:...
I found now the reason - one needs admin privileges when compiling NSIS scripts. With admin
permissions one can compile as normal
Am 30.03.2014 22:21, schrieb Vincent van Ravesteijn:
Stunningly, the setting of MikTeX is changed from "Ask me before installing
packages" to "Yes,
install packages on the fly". It would be nice to reset this setting to the
value it had before the
installer overruled it.
The installer can re
Am 30.03.2014 22:13, schrieb Vincent van Ravesteijn:
Yes, it works.
Great. However, NSIS gets now permanently broken: I have first to install the normal NSIS 2.4.6 then
I have to open makensisw and while having makensisw open I have to replace makensis.exe by the one
for long paths.
I also
Am 30.03.2014 22:17, schrieb Vincent van Ravesteijn:
Yes, now MikTeX is found, but I'm now irritated that the installer starts
installing MikTeX packages
even if I said "No" when it asked me to check for MikTeX updates
I cannot reproduce that. Is this bug only in my latest installer (with the
Vincent van Ravesteijn schreef op 30-3-2014 22:17:
Yes, now MikTeX is found, but I'm now irritated that the installer
starts installing MikTeX packages even if I said "No" when it asked me
to check for MikTeX updates, _and_ while I've told MikTeX to ask me
before automatically installing pack
Uwe Stöhr schreef op 30-3-2014 5:44:
Am 27.03.2014 23:50, schrieb Vincent van Ravesteijn:
The problem is that NSIS has a maximum string length of 1024
characters (including \r\n). My Path
variable is longer than 1024, so ReadRegStr returns an empty string.
See http://nsis.sourceforge.net/Spe
Uwe Stöhr schreef op 30-3-2014 5:44:
Am 27.03.2014 23:50, schrieb Vincent van Ravesteijn:
The problem is that NSIS has a maximum string length of 1024
characters (including \r\n). My Path
variable is longer than 1024, so ReadRegStr returns an empty string.
See http://nsis.sourceforge.net/Spe
Am 27.03.2014 23:50, schrieb Vincent van Ravesteijn:
The problem is that NSIS has a maximum string length of 1024 characters
(including \r\n). My Path
variable is longer than 1024, so ReadRegStr returns an empty string.
See http://nsis.sourceforge.net/Special_Builds#Large_strings how you can
Am 28.03.2014 00:13, schrieb Vincent van Ravesteijn:
1282 characters. Not extremely large mine was almost as large.
Poser! ;-)
Uwe
Uwe Stöhr schreef op 28-3-2014 0:11:
Am 28.03.2014 00:04, schrieb Vincent van Ravesteijn:
Hmm. you should have mentioned that to the reporters in bug #8570 ;).
I did not think that this is be the problem.
While looking at the bug again now I see that
http://www.lyx.org/trac/ticket/8570#commen
Am 28.03.2014 00:04, schrieb Vincent van Ravesteijn:
Hmm. you should have mentioned that to the reporters in bug #8570 ;).
I did not think that this is be the problem.
While looking at the bug again now I see that
http://www.lyx.org/trac/ticket/8570#comment:13
has an extremely large PATH.
How
Uwe Stöhr schreef op 28-3-2014 0:02:
Am 27.03.2014 23:50, schrieb Vincent van Ravesteijn:
To solve your MiKTeX recognition error, can you please send me the
content of your registry entry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\Environment "Path"
Well, I assur
Am 27.03.2014 23:50, schrieb Vincent van Ravesteijn:
To solve your MiKTeX recognition error, can you please send me the content of
your registry entry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment
"Path"
Well, I assure you that miktex is in the path
I wa
Uwe Stöhr schreef op 27-3-2014 22:20:
To solve your MiKTeX recognition error, can you please send me the
content of your registry entry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\Environment "Path"
Well, I assure you that miktex is in the path, but I've debugged t
14 matches
Mail list logo
