Re: Windows Installers: TESTING ONLY

On 16/05/2018 3:33 p.m., Richard Kimberly Heck wrote: I have finally managed to build Windows installers for 2.3.0. They can be found here:     http://ftp.lyx.org/pub/lyx/devel/lyx-2.3/ Let me emphasize again that     THESE ARE FOR TESTING ONLY I have tested them a little bit myself,

Re: SIGSEGV when copy/pasting a child doc

On Wed, May 02, 2018 at 04:00:12PM +, Scott Kostyshak wrote: > On Wed, May 02, 2018 at 01:06:04PM +, Jean-Marc Lasgouttes wrote: > > Le 28/04/2018 à 00:06, Scott Kostyshak a écrit : > > > On Wed, Apr 25, 2018 at 06:41:36PM +, Scott Kostyshak wrote: > > > > > > > it is not 100%

Re: Lyx on Mac bug: document tabs disappearing in fullscreen mode

On Wed, May 16, 2018 at 04:03:44AM +, Zhexuan Gong wrote: > Yes, it's still there in 2.3.0 and perfectly reproducible. Thanks for checking. Scott signature.asc Description: PGP signature

Re: Lyx on Mac bug: document tabs disappearing in fullscreen mode

Yes, it's still there in 2.3.0 and perfectly reproducible. On Tue, May 15, 2018 at 8:47 PM, Scott Kostyshak wrote: > On Fri, Feb 02, 2018 at 06:25:25PM +, Scott Kostyshak wrote: > > On Sat, Oct 28, 2017 at 12:47:29AM +, Zhexuan Gong wrote: > > > Dear Lyx developers, >

Windows Installers: TESTING ONLY

I have finally managed to build Windows installers for 2.3.0. They can be found here:     http://ftp.lyx.org/pub/lyx/devel/lyx-2.3/ Let me emphasize again that     THESE ARE FOR TESTING ONLY I have tested them a little bit myself, but not a whole lot. They seem to work, basically---I

Re: Lyx on Mac bug: document tabs disappearing in fullscreen mode

On Fri, Feb 02, 2018 at 06:25:25PM +, Scott Kostyshak wrote: > On Sat, Oct 28, 2017 at 12:47:29AM +, Zhexuan Gong wrote: > > Dear Lyx developers, > > > > I'm not sure if any of you are aware of this bug. I'm using the latest > > 2.2.3 Lyx on Mac. And whenever Lyx is in macOS' native full

cmake Error

Could NOT find LYX_PY_polib (missing: LYX_PY_POLIB) Is that something I need to worry about? Riki

Re: LyX 2.3.1

On 05/15/2018 01:14 PM, Scott Kostyshak wrote: > On Tue, May 15, 2018 at 09:30:09AM +, Pavel Sanda wrote: >> Richard Kimberly Heck wrote: >>> I am working on this. I've managed to compile for Windows using mingw on >>> Linux (amazingly easy, actually) but have not dealt with the packaging >>>

Re: [LyX/master] #11142 correct list of previous version to check for user directory contents

On 05/15/2018 04:03 PM, Stephan Witt wrote: > Am 13.05.2018 um 20:16 schrieb Stephan Witt : >> commit 17c3617c49487977e5c46de20cb450952c68b03d >> Author: Stephan Witt >> Date: Sun May 13 20:15:35 2018 +0200 >> >>#11142 correct list of previous version to check

Re: [LyX/master] Removed unused private variable

Le 15/05/2018 à 21:58, Richard Kimberly Heck a écrit : Removed unused private variable Spotted by clang++ 6. Riki, I guess this is OK for branch? Sure. Done. JMarc

Re: [LyX/master] #11142 correct list of previous version to check for user directory contents

Am 13.05.2018 um 20:16 schrieb Stephan Witt : > > commit 17c3617c49487977e5c46de20cb450952c68b03d > Author: Stephan Witt > Date: Sun May 13 20:15:35 2018 +0200 > >#11142 correct list of previous version to check for user directory > contents > >LyX on

Re: [LyX/master] Removed unused private variable

On 05/15/2018 04:54 AM, Jean-Marc Lasgouttes wrote: > Le 15/05/2018 à 00:04, Jean-Marc Lasgouttes a écrit : >> commit c4075367fa6330cac075e94b61f8522fcd54f630 >> Author: Jean-Marc Lasgouttes >> Date:   Mon May 14 23:03:50 2018 +0200 >> >> Removed unused private variable

Re: LyX 2.3.0 Regression Inquiry

On 05/15/2018 03:42 AM, Jürgen Spitzmüller wrote: > Am Montag, den 14.05.2018, 13:51 -0400 schrieb Richard Kimberly Heck: >> So probably 2d6173d8103 was a mistake: We should just have said that >> you >> can't do that. But that was before the includeonly support, I >> believe, >> so maybe it made

Re: Error messages with lyx2.3

Le 15/05/2018 à 19:51, Enrico Forestieri a écrit : The problem seems to be in the calling code. This seems to happen for svgz files (compressed svg files). Actually, it seems to happen when the same image is included multiple times, irrespective of the type. See attached example. Bisect leads

Re: Error messages with lyx2.3

On Fri, May 11, 2018 at 06:13:31PM +0100, José Abílio Matos wrote: > On Thursday, 10 May 2018 18.32.00 WEST Scott Kostyshak wrote: > > Should I still do the above? I'm not sure if it would still be useful > > after reading the messages that came after this. > > > > Thanks for helping debug, > >

Re: LyX 2.3.1

On Tue, May 15, 2018 at 09:30:09AM +, Pavel Sanda wrote: > Richard Kimberly Heck wrote: > > I am working on this. I've managed to compile for Windows using mingw on > > Linux (amazingly easy, actually) but have not dealt with the packaging > > issues yet. Fortunately, someone who reported a

Re: Musings from configure

On Tuesday, 15 May 2018 11.03.01 WEST Jean-Marc Lasgouttes wrote: > This has been fixed by Enrico at 6253cc4c51e4e3, right? > > JMarc After running again autogen.sh the problem went away. So I suspect that the answer is yes to your question. :-) -- José Abílio

Re: Musings from configure

Le 08/05/2018 à 16:08, José Abílio Matos a écrit : === The following minor problems have been detected by configure. === Please check the messages below before running 'make'. === (see the section 'Problems' in the INSTALL file) == The found moc compiler is for Qt moc-qt5 5.10.1 but the Qt

Re: LyX 2.3.1

Richard Kimberly Heck wrote: > I am working on this. I've managed to compile for Windows using mingw on > Linux (amazingly easy, actually) but have not dealt with the packaging > issues yet. Fortunately, someone who reported a bug to us seems as if > they may have done so and is giving me some

Re: LyX master Work Area Disappears on Initial Save (Redraw issue?)

Le 15/05/2018 à 06:08, Richard Kimberly Heck a écrit : + // Do not trigger the painting machinery if we are not ready (see + // bug #10989). However, since macOS has turned the screen back at "black", I take it. Indeed. I pushed the patch to master. JMarc

Re: LyX 2.3.0 Regression Inquiry

Am Montag, den 14.05.2018, 13:51 -0400 schrieb Richard Kimberly Heck: > So probably 2d6173d8103 was a mistake: We should just have said that > you > can't do that. But that was before the includeonly support, I > believe, > so maybe it made sense then? I'm not sure. Note that it does not work