On Mar 3, 2016, at 5:34 PM, Guillaume Munch wrote:
> Le 03/03/2016 23:48, Jerry a écrit :
>> the behavior is the same--Reconfigure
>> runs quickly without and crashing luatex, and the Python command
>> appears to be running very long
>>
>
> I am not sure I understand.
>
What I
Le 03/03/2016 23:48, Jerry a écrit :
the behavior is the same--Reconfigure
runs quickly without and crashing luatex, and the Python command
appears to be running very long
I am not sure I understand.
On Feb 28, 2016, at 12:36 PM, Guillaume Munch wrote:
>
> Le 27/02/2016 03:44, Jerry a écrit :
>> If I remove
>> /Library/TeX/texbin:/usr/texbin:/sw/bin:/sw/sbin:/opt/local/teTeX/bin:
>>
>> from the front of the PATH prefix and run Reconfigure, it runs in
>> 15-20 seconds. The
Le 27/02/2016 03:44, Jerry a écrit :
If I remove
/Library/TeX/texbin:/usr/texbin:/sw/bin:/sw/sbin:/opt/local/teTeX/bin:
from the front of the PATH prefix and run Reconfigure, it runs in
15-20 seconds. The first time I saw a luatex instance in Activity
Monitor but on subsequent runs it did not
On Feb 26, 2016, at 8:54 AM, Stephan Witt wrote:
>
>> Am 26.02.2016 um 16:41 schrieb Guillaume Munch :
>>
>> Le 26/02/2016 10:08, Jerry a écrit :
>>> I don't know if you could infer that from my previous comments, but
>>> more or less what happens.
>>
>> I
Le 26/02/16 23:34, Richard Heck a écrit :
The backtrace suggests that it is taking a very long time just to
collect directory info. If one had a really, really big TeX
installation, could that cause this kind of problem? (That's a question
for JMarc, Jerry, not for you.)
I do not know... Could
On 02/26/2016 05:30 PM, Jerry wrote:
> On Feb 26, 2016, at 3:27 AM, Jean-Marc Lasgouttes wrote:
>
>> Le 26/02/2016 11:09, Jerry a écrit :
>>> On Feb 25, 2016, at 6:52 AM, Jean-Marc Lasgouttes
>>> wrote:
>>>
Le 25/02/2016 10:01, Jerry a écrit :
>
On Feb 26, 2016, at 3:27 AM, Jean-Marc Lasgouttes wrote:
> Le 26/02/2016 11:09, Jerry a écrit :
>>
>> On Feb 25, 2016, at 6:52 AM, Jean-Marc Lasgouttes wrote:
>>
>>> Le 25/02/2016 10:01, Jerry a écrit :
When I ran the Python command in a terminal,
> Am 26.02.2016 um 16:41 schrieb Guillaume Munch :
>
> Le 26/02/2016 10:08, Jerry a écrit :
>> I don't know if you could infer that from my previous comments, but
>> more or less what happens.
>
> I could infer, more or less :)
>
>> The luatex process starts almost as soon
>> as
Le 26/02/2016 10:08, Jerry a écrit :
I don't know if you could infer that from my previous comments, but
more or less what happens.
I could infer, more or less :)
The luatex process starts almost as soon
as I hit Reconfigure. I Quit it (force quit not required) using
Activity Monitor. LyX is
On Friday, February 26, 2016 11:27:25 AM Jean-Marc Lasgouttes wrote:
> Also, there is a question you may already have answered. What happens if
> you interrupt the running confogure.py with Ctrl+C? Does python give you
> a backtrace showing where it is in the configure.py script?
>
> JMarc
It
Le 26/02/2016 11:09, Jerry a écrit :
On Feb 25, 2016, at 6:52 AM, Jean-Marc Lasgouttes wrote:
Le 25/02/2016 10:01, Jerry a écrit :
When I ran the Python command in a terminal, it proceeded quickly to "+Indexing TeX
files..." and stayed there for about 34 minutes and
On Feb 25, 2016, at 6:52 AM, Jean-Marc Lasgouttes wrote:
> Le 25/02/2016 10:01, Jerry a écrit :
>> When I ran the Python command in a terminal, it proceeded quickly to
>> "+Indexing TeX files..." and stayed there for about 34 minutes and
>> everything else took no more
On Feb 25, 2016, at 9:15 AM, Guillaume Munch wrote:
> Le 25/02/2016 00:54, Jerry a écrit :
>> On Feb 24, 2016, at 6:49 AM, Guillaume Munch wrote:
>>
>>> I may have had a similar issue involving LuaTeX taking huge amounts
>>> of time to configure, at some point,
Le 25/02/2016 00:54, Jerry a écrit :
On Feb 24, 2016, at 6:49 AM, Guillaume Munch wrote:
I may have had a similar issue involving LuaTeX taking huge amounts
of time to configure, at some point, with LyX 2.1 and TeXLive
2012/2013. It got solved by upgrading TeXLive. Jerry, do you
Le 25/02/2016 10:01, Jerry a écrit :
When I ran the Python command in a terminal, it proceeded quickly to "+Indexing TeX
files..." and stayed there for about 34 minutes and everything else took no more
than about a minute--just as before installing texlive-fonts-recommended.
Does this mean
On Feb 24, 2016, at 5:48 PM, Jerry wrote:
>
> On Feb 24, 2016, at 3:04 AM, Jean-Marc Lasgouttes wrote:
>
>> Le 24/02/2016 10:06, Jerry a écrit :
>>> I have two TeX installations. One I installed from the TUG (I think that's
>>> what it's called)
On Feb 24, 2016, at 6:49 AM, Guillaume Munch wrote:
> I may have had a similar issue involving LuaTeX taking huge amounts of
> time to configure, at some point, with LyX 2.1.3 and TeXLive 2012/2013.
> It got solved by upgrading TeXLive. Jerry, do you have lots of fonts
> installed?
On Feb 24, 2016, at 2:32 AM, Jean-Marc Lasgouttes wrote:
> Le 24/02/2016 05:18, Jerry a écrit :
>> +checking for default encoding (this may take a long time)
>>
>> kpathsea: Running mktextfm ecrm1000
>> /opt/local/share/texmf-texlive/web2c/mktexnam: Could not map source
>>
On Feb 24, 2016, at 3:04 AM, Jean-Marc Lasgouttes wrote:
> Le 24/02/2016 10:06, Jerry a écrit :
>> I have two TeX installations. One I installed from the TUG (I think that's
>> what it's called) binary installer, probably TeXlive-2013, and the other as
>> part of MacPorts,
I may have had a similar issue involving LuaTeX taking huge amounts of
time to configure, at some point, with LyX 2.1.3 and TeXLive 2012/2013.
It got solved by upgrading TeXLive. Jerry, do you have lots of fonts
installed?
Le 24/02/2016 09:06, Jerry a écrit :
On Feb 23, 2016, at 9:46 PM,
Le 24/02/2016 10:06, Jerry a écrit :
I have two TeX installations. One I installed from the TUG (I think that's what it's called)
binary installer, probably TeXlive-2013, and the other as part of MacPorts, macports.org;
this -> "texlive-bin @2015_8+x11 (active)" I think is relevant information
On Feb 23, 2016, at 9:46 PM, Scott Kostyshak wrote:
> On Tue, Feb 23, 2016 at 09:18:50PM -0700, Jerry wrote:
>>
>> On Feb 23, 2016, at 3:28 PM, Scott Kostyshak wrote:
>
>>> Jerry does this happen even when Flexiglass is not running?
>>
>> Yes. The
Le 24/02/2016 05:18, Jerry a écrit :
+checking for default encoding (this may take a long time)
kpathsea: Running mktextfm ecrm1000
/opt/local/share/texmf-texlive/web2c/mktexnam: Could not map source
abbreviation for ecrm1000.
/opt/local/share/texmf-texlive/web2c/mktexnam: Need to update ?
On Tue, Feb 23, 2016 at 09:18:50PM -0700, Jerry wrote:
>
> On Feb 23, 2016, at 3:28 PM, Scott Kostyshak wrote:
> > Jerry does this happen even when Flexiglass is not running?
>
> Yes. The behavior is the same, which is, using a non-new LyX but running
> Reconfigure, one
On Feb 23, 2016, at 3:28 PM, Scott Kostyshak wrote:
> On Fri, Feb 19, 2016 at 08:08:27PM -0700, Jerry wrote:
>>
>> On Feb 18, 2016, at 9:49 AM, Scott Kostyshak wrote:
>>
>>> On Thu, Feb 18, 2016 at 02:18:51AM -0700, Jerry wrote:
*Every*time* I first
On Fri, Feb 19, 2016 at 08:08:27PM -0700, Jerry wrote:
>
> On Feb 18, 2016, at 9:49 AM, Scott Kostyshak wrote:
>
> > On Thu, Feb 18, 2016 at 02:18:51AM -0700, Jerry wrote:
> >> *Every*time* I first launch a new version of LyX, something like this
> >> happens:
> >
> > So to
On Feb 18, 2016, at 9:49 AM, Scott Kostyshak wrote:
> On Thu, Feb 18, 2016 at 02:18:51AM -0700, Jerry wrote:
>> *Every*time* I first launch a new version of LyX, something like this
>> happens:
>
> So to confirm, this is nothing new in 2.2.0 right? You remember seeing
>
On Thu, Feb 18, 2016 at 02:18:51AM -0700, Jerry wrote:
> *Every*time* I first launch a new version of LyX, something like this
> happens:
So to confirm, this is nothing new in 2.2.0 right? You remember seeing
this in 2.1.x?
> LyX hangs, using about 5K of RAM. Force quit. Relaunch. Lyx stalls
*Every*time* I first launch a new version of LyX, something like this happens:
LyX hangs, using about 5K of RAM. Force quit. Relaunch. Lyx stalls with maybe 5
MB RAM but two luatex processes start up. Over a few minutes, they ramp up so
that each consumes 200+ MB and up to nearly 100% CPU
30 matches
Mail list logo