On Wed, May 24, 2017 at 01:29:45PM -0400, Cris Fuhrman wrote:
> On Tue, May 23, 2017 at 10:38 PM, Scott Kostyshak <skost...@lyx.org> wrote:
> 
> > On Wed, Apr 19, 2017 at 11:29:12AM +0200, Jean-Marc Lasgouttes wrote:
> > > I understand that this gives minor debugging information (that can
> > probably
> > > be obtained via a debugging channel), but it is not the first time that
> > it
> > > triggers LaTeX file length limits.
> >
> > Chris, do you feel like writing up a bug/enhancement request at
> >
> >     https://www.lyx.org/trac
> >
> > ? A reproducible example would indeed give us a push to look into an
> > improvement.
> >
> >
> I have 2 Win 10 machines (an older Win 7 that was upgraded and a newer
> Surface Pro 4). The newer machine seems not to have the problem today (I
> couldn't reproduce it). I'll try this at home on my upgraded PC, which is
> where I know I had it before. It could be system-dependent. As I recall, it
> was one of the file conversion routines that was failing, not producing the
> output it should, and the next step in the LyX processing was getting a
> file not found error.
> 
> On a related note, the MikTeX distribution servers were intentionally
> offline again yesterday. I got a couple more upvotes to my answer at
> https://tex.stackexchange.com/a/254393/17868. I posted this issue in the
> MikTeX tracker: https://sourceforge.net/p/miktex/bugs/2604/ -- it directly
> affects the LyX installations relying on MikTeX.

Thanks for the detailed update, Chris. Let us know if there's anything
you think we can do or should change to help prevent these issues.

Scott

Attachment: signature.asc
Description: PGP signature

Reply via email to