In summary, it doesn't, as I have a full installation...
-
Julio Rojas
jcredbe...@gmail.com
On Tue, Jul 1, 2014 at 2:25 AM, Denis Navas Vega
wrote:
> I have never used TexLive, but I once read that TexLive was not conceived
> for Windows.
>
> Pro
I have never used TexLive, but I once read that TexLive was not
conceived for Windows.
Probably you have to review how TexLive automatically actualize packages
on demand (when needed).
Dear Denis,
I have TeXlive on my Windows machine, in order to avoid other problems I
have found with Lyx. Do you think that might be a source of problems?
Nevertheless, I believe that I had started Lyx's installer with
administrative privileges.
Regards,
At the begining, I have found desirable to run LyX with administrative
privileges in windows. That avoid that the operative system, block
access to some files. Since LyX will invoke MikTeX after it verifies
the installed packages, is important that MikTeX is configured to
automatically instal
Thanks everybody. What I did was killing lualatex.exe at the very moment it
is started by the configuration script, which in turn continues without any
more hiccups until Lyx is started correctly.
Regards.
-
Julio Rojas
jcredbe...@gmail.com
On Sun
On Sun, Jun 8, 2014 at 3:04 PM, Richard Heck wrote:
> On 06/07/2014 10:12 PM, Julio Rojas wrote:
>
>> Dear all,
>>
>> I have just tried to install Lyx 2.1 on my Windows 7 PC on which I
>> already had Lyx 2.0.6 and TexLive 2013, so I went the update way. During
>> configuration, Lyx runs LuaLatex
On 06/07/2014 10:12 PM, Julio Rojas wrote:
Dear all,
I have just tried to install Lyx 2.1 on my Windows 7 PC on which I
already had Lyx 2.0.6 and TexLive 2013, so I went the update way.
During configuration, Lyx runs LuaLatex which in turn gets stuck and
start bloating and eating all the reso
Dear all,
I have just tried to install Lyx 2.1 on my Windows 7 PC on which I already
had Lyx 2.0.6 and TexLive 2013, so I went the update way. During
configuration, Lyx runs LuaLatex which in turn gets stuck and start
bloating and eating all the resources. I tried killing the script
(python.exe).