On Wed, May 24, 2017 at 01:29:45PM -0400, Cris Fuhrman wrote:
> On Tue, May 23, 2017 at 10:38 PM, Scott Kostyshak 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
> >
On Tue, May 23, 2017 at 10:38 PM, Scott Kostyshak 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
On Wed, Apr 19, 2017 at 11:29:12AM +0200, Jean-Marc Lasgouttes wrote:
> Le 17/04/2017 à 00:47, Cris Fuhrman a écrit :
> > Another problem I encounter is with long file paths, but only when
> > using, say, PNG images in my LyX files. LyX again fails with an obscure
> > error. Debugging the image
Le 17/04/2017 à 00:47, Cris Fuhrman a écrit :
Another problem I encounter is with long file paths, but only when
using, say, PNG images in my LyX files. LyX again fails with an obscure
error. Debugging the image conversion in the cache showed that my the
filename was really long and at some
I can share a bit as a win10 user of 2.2.2.
One annoying quirk of LyX and MikTeX is the fact that MikTeX on-the-fly
installs can sometimes fail for weird but not rare reasons. For example,
you configured MikTeX to use server ABC but for some strange reason that
server's archive is broken and the
Hallo Stephan,
Can't help you directly on Mac, perhaps until i get a colleague to redo it
for me... 2-3 weeks later.
I can certainly document on win7 and win10, since all my recent Lyx
installs this week have failed the same. Not even the Lyx Help files could
compile (ctrl-r => style/class not
Am 13.04.2017 um 15:44 schrieb Mitch Gusat :
>
> Seen the same issues on Mac and Linux, but it's particularly vexing on
> Windows since the recent (April'17) Miktex 2.9 release: Lyx 2.0/1/2 used to
> work flawlessly for years before the new miktex release.
Hi Mitch,
I’d like