Re: [LyX/2.3-staging] Sanitize InsetMathHull and add a check for mutability in LFUN_MATH_MUTATE

Le 17/04/2016 00:09, Richard Heck a écrit : On 04/16/2016 05:58 PM, Guillaume Munch wrote: commit 9b45121e4fbecd6c15f42d81a6d522236079760c Author: Guillaume Munch Date: Mon Dec 14 01:54:27 2015 + Sanitize InsetMathHull and add a check for mutability in

Re: [LyX/2.3-staging] Sanitize InsetMathHull and add a check for mutability in LFUN_MATH_MUTATE

On 04/16/2016 05:58 PM, Guillaume Munch wrote: > commit 9b45121e4fbecd6c15f42d81a6d522236079760c > Author: Guillaume Munch > Date: Mon Dec 14 01:54:27 2015 + > > Sanitize InsetMathHull and add a check for mutability in LFUN_MATH_MUTATE > > Remove in particular all

Re: [LyX/2.3-staging] Correct col spacing in Cases environment

On 04/16/2016 05:58 PM, Guillaume Munch wrote: > commit 112367ed4de65d1cd2456408bf8df54a3841bcf4 > Author: Guillaume Munch > Date: Fri Apr 8 20:24:12 2016 +0200 > > Correct col spacing in Cases environment Fine for 2.2.2. rh

Re: [LyX/2.3-staging] Display the correct horizontal alignment in AMS environments

On 04/16/2016 05:58 PM, Guillaume Munch wrote: > commit ada69c1f81d1f088ffdd43ac0cbfebe3031aac80 > Author: Guillaume Munch > Date: Sun Dec 13 03:32:32 2015 + > > Display the correct horizontal alignment in AMS environments > > A longstanding problem... (related:

Re: [LyX/2.3-staging] Fix the display of column spacing in AMS environments

On 04/16/2016 05:58 PM, Guillaume Munch wrote: > commit 7e59242874f6a29c1fa5818deb5cad4d9c759391 > Author: Guillaume Munch > Date: Sun Dec 20 20:56:34 2015 + > > Fix the display of column spacing in AMS environments Fine for 2.2.2. rh

Re: [LyX/2.2.2-staging] status.22x

On 04/16/2016 06:23 PM, Guillaume Munch wrote: > commit 72ce4519de0933660d246944ca2266e0d26b0d94 > Author: Guillaume Munch > Date: Sat Apr 16 23:23:03 2016 +0100 > > status.22x Thanks for creating this file. rh

Re: [PATCH] compilation fix for libc++ in C++11 mode

Le 10/01/2016 21:38, Jean-Marc Lasgouttes a écrit : Le 10/01/16 22:33, Guillaume Munch a écrit : I imagine that Toc and other classes are being forward-declared in some headers probably for the same speed reason. Toc.h is there to provide an alternative to the forward declarations without

Re: Staging Branches [REVISED]

On 04/16/2016 04:25 PM, Guillaume Munch wrote: > Le 16/04/2016 20:44, Richard Heck a écrit : >> >> We now have three staging branches. These are: >> >> 2.3-staging >> 2.2.1-staging >> 2.2.2-staging >> >> >> 2.3-staging can be treated as master usually is: It is for development >> on

Re: [RFC] Staging Branches and Trac

On 04/16/2016 04:19 PM, Guillaume Munch wrote: > Le 16/04/2016 20:49, Richard Heck a écrit : >> >> As Scott pointed out, my previous suggestions for how fixes committed to >> the staging branches should be handled in trac was silly. We can't reuse >> "fixedinmaster" for 2.3-staging. I'm also not

Re: Staging Branches [REVISED]

Le 16/04/2016 20:44, Richard Heck a écrit : We now have three staging branches. These are: 2.3-staging 2.2.1-staging 2.2.2-staging 2.3-staging can be treated as master usually is: It is for development on what will become 2.3 and is now open for commits. This branch will be

Re: [RFC] Staging Branches and Trac

Le 16/04/2016 20:49, Richard Heck a écrit : As Scott pointed out, my previous suggestions for how fixes committed to the staging branches should be handled in trac was silly. We can't reuse "fixedinmaster" for 2.3-staging. I'm also not sure that we want to introduce a new status

Re: [LyX/2.3-staging] Raise the maxlastfiles cap

On 04/16/2016 04:09 PM, Guillaume Munch wrote: > commit 3f5c2b11e543e126224181edcbb4c34289a9e342 > Author: Guillaume Munch > Date: Wed Jan 13 01:30:05 2016 + > > Raise the maxlastfiles cap > > This only changes the maximum value that the user can choose in the UI,

Re: "Splitting of consecutive environments has been reworked and enhanced"

On 04/16/2016 04:01 PM, Guillaume Munch wrote: > Le 24/01/2016 23:08, Enrico Forestieri a �crit : >> On Sun, Jan 24, 2016 at 10:41:39PM +0100, Enrico Forestieri wrote: >>> On Fri, Jan 22, 2016 at 06:36:03PM -0500, Guillaume Munch wrote: Maybe we can go with the improvements you already

Re: "Splitting of consecutive environments has been reworked and enhanced"

Le 24/01/2016 23:08, Enrico Forestieri a écrit : On Sun, Jan 24, 2016 at 10:41:39PM +0100, Enrico Forestieri wrote: On Fri, Jan 22, 2016 at 06:36:03PM -0500, Guillaume Munch wrote: Maybe we can go with the improvements you already made for beta, and commit this particular patch to master

[RFC] Staging Branches and Trac

As Scott pointed out, my previous suggestions for how fixes committed to the staging branches should be handled in trac was silly. We can't reuse "fixedinmaster" for 2.3-staging. I'm also not sure that we want to introduce a new status "fixedinstaging" for such a short time. Here, then, is a

Re: Staging Branches

On 04/16/2016 01:45 PM, Jean-Marc Lasgouttes wrote: > Le 16/04/16 19:31, Scott Kostyshak a écrit : >> On Sat, Apr 16, 2016 at 08:34:47AM -0400, Richard Heck wrote: >> >>> As usual, fixes for bugs committed to 2.2.1-staging (=2.2.x) should >>> first be >>> committed to 2.3-staging (=master). These

Staging Branches [REVISED]

We now have three staging branches. These are: 2.3-staging 2.2.1-staging 2.2.2-staging 2.3-staging can be treated as master usually is: It is for development on what will become 2.3 and is now open for commits. This branch will be merged into master after the release of 2.2.0.

Re: Staging Branches

On 04/16/2016 01:31 PM, Scott Kostyshak wrote: > On Sat, Apr 16, 2016 at 08:34:47AM -0400, Richard Heck wrote: > >> As usual, fixes for bugs committed to 2.2.1-staging (=2.2.x) should first be >> committed to 2.3-staging (=master). These should be marked "fixedinmaster" >> in trac but NOT

Re: SVG display on LyX appears corrupted on the 2.2RC1 Windows build

Le 16/04/2016 19:55, Guenter Milde a écrit : On 2016-04-16, Scott Kostyshak wrote: That would be another nice reason to do that, but I'm not sure if that is indeed true. However I suppose the conversion is so quick it doesn't make a difference since the relevant timing comparison is compiling

Re: SVG display on LyX appears corrupted on the 2.2RC1 Windows build

On 2016-04-16, Scott Kostyshak wrote: > On Sat, Apr 16, 2016 at 04:33:10PM +0100, Guillaume Munch wrote: >> It would make sense to preview using the same converter as is used to >> generate the pdf. Georg wrote "If the Qt implementation of SVG rendering >> is really that limited, then it would be

Re: Staging Branches

On Sat, Apr 16, 2016 at 07:04:01PM +0100, Guillaume Munch wrote: > Le 16/04/2016 18:55, Scott Kostyshak a écrit : > > On Sat, Apr 16, 2016 at 07:45:29PM +0200, Jean-Marc Lasgouttes wrote: > > > Le 16/04/16 19:31, Scott Kostyshak a écrit : > > > > On Sat, Apr 16, 2016 at 08:34:47AM -0400, Richard

Re: Staging Branches

Le 16/04/2016 18:55, Scott Kostyshak a écrit : On Sat, Apr 16, 2016 at 07:45:29PM +0200, Jean-Marc Lasgouttes wrote: Le 16/04/16 19:31, Scott Kostyshak a écrit : On Sat, Apr 16, 2016 at 08:34:47AM -0400, Richard Heck wrote: As usual, fixes for bugs committed to 2.2.1-staging (=2.2.x) should

Re: Staging Branches

On Sat, Apr 16, 2016 at 07:45:29PM +0200, Jean-Marc Lasgouttes wrote: > Le 16/04/16 19:31, Scott Kostyshak a écrit : > > On Sat, Apr 16, 2016 at 08:34:47AM -0400, Richard Heck wrote: > > > > > As usual, fixes for bugs committed to 2.2.1-staging (=2.2.x) should first > > > be > > > committed to

Re: Staging Branches

Le 16/04/16 19:31, Scott Kostyshak a écrit : On Sat, Apr 16, 2016 at 08:34:47AM -0400, Richard Heck wrote: As usual, fixes for bugs committed to 2.2.1-staging (=2.2.x) should first be committed to 2.3-staging (=master). These should be marked "fixedinmaster" in trac but NOT "fixedinstable" and

Re: lyx-cvs messages: show file names changed

On Sat, Apr 16, 2016 at 08:35:54AM -0400, Richard Heck wrote: > On 04/15/2016 05:45 PM, Scott Kostyshak wrote: > > On Tue, Mar 29, 2016 at 06:09:56PM -0400, Scott Kostyshak wrote: > > > On Tue, Mar 29, 2016 at 10:49:55AM +0200, Jean-Marc Lasgouttes wrote: > > > > Le 28/03/2016 00:04, Scott

Re: SVG display on LyX appears corrupted on the 2.2RC1 Windows build

On Sat, Apr 16, 2016 at 04:33:10PM +0100, Guillaume Munch wrote: > Le 15/04/2016 09:12, Scott Kostyshak a écrit : > > On Fri, Apr 15, 2016 at 01:53:03AM +0200, Shankar Giri Venkita Giri wrote: > > > I tried to incluide an SVG graphic in a LyX file and it appears > > > horribly corrupted (black

Re: Staging Branches

On Sat, Apr 16, 2016 at 08:34:47AM -0400, Richard Heck wrote: > As usual, fixes for bugs committed to 2.2.1-staging (=2.2.x) should first be > committed to 2.3-staging (=master). These should be marked "fixedinmaster" > in trac but NOT "fixedinstable" and tagged with milestone 2.2.1. So now

Re: Staging Branches

On Sat, Apr 16, 2016 at 10:33:46AM -0400, Richard Heck wrote: > On 04/16/2016 09:30 AM, Kornel Benko wrote: > > Does it mean, the master is closed? Or in other words, what happens if > > someone commits in master? > > My understanding is that master is still closed, except for absolutely >

Re: SVG display on LyX appears corrupted on the 2.2RC1 Windows build

Le 16/04/2016 16:33, Guillaume Munch a écrit : Le 15/04/2016 09:12, Scott Kostyshak a écrit : On Fri, Apr 15, 2016 at 01:53:03AM +0200, Shankar Giri Venkita Giri wrote: I tried to incluide an SVG graphic in a LyX file and it appears horribly corrupted (black triangles everywhere in the image

Re: SVG display on LyX appears corrupted on the 2.2RC1 Windows build

Le 15/04/2016 09:12, Scott Kostyshak a écrit : On Fri, Apr 15, 2016 at 01:53:03AM +0200, Shankar Giri Venkita Giri wrote: I tried to incluide an SVG graphic in a LyX file and it appears horribly corrupted (black triangles everywhere in the image boundary). PDF output is fine. LyX 2.1 did not

Re: Staging Branches

On 04/16/2016 09:30 AM, Kornel Benko wrote: > Am Samstag, 16. April 2016 um 08:34:47, schrieb Richard Heck >> I have just created two staging branches, as discussed in a previous >> thread. These are: >> >> 2.3-staging >> 2.2.1-staging >> >> The former can be treated

Re: Staging Branches

Am Samstag, 16. April 2016 um 08:34:47, schrieb Richard Heck > > I have just created two staging branches, as discussed in a previous > thread. These are: > > 2.3-staging > 2.2.1-staging > > The former can be treated as master usually is: It is for development on

Re: [PATCH] move doc changelogs out of attic

Am Samstag, 16. April 2016 um 08:37:04, schrieb Richard Heck > On 04/15/2016 05:48 PM, Scott Kostyshak wrote: > > On Fri, Apr 15, 2016 at 06:20:56PM +0200, Jean-Marc Lasgouttes wrote: > >> Le 07/04/2016 00:02, Uwe Stöhr a écrit : > >>> Am 05.04.2016 um 10:23 schrieb Jean-Marc

Re: [PATCH] move doc changelogs out of attic

On 04/15/2016 05:48 PM, Scott Kostyshak wrote: On Fri, Apr 15, 2016 at 06:20:56PM +0200, Jean-Marc Lasgouttes wrote: Le 07/04/2016 00:02, Uwe Stöhr a écrit : Am 05.04.2016 um 10:23 schrieb Jean-Marc Lasgouttes: If the translators know where to look for the files, they are not personal

Re: lyx-cvs messages: show file names changed

On 04/15/2016 05:45 PM, Scott Kostyshak wrote: On Tue, Mar 29, 2016 at 06:09:56PM -0400, Scott Kostyshak wrote: On Tue, Mar 29, 2016 at 10:49:55AM +0200, Jean-Marc Lasgouttes wrote: Le 28/03/2016 00:04, Scott Kostyshak a écrit : It seems we currently use "git show ${hash}" in our script.

Staging Branches

I have just created two staging branches, as discussed in a previous thread. These are: 2.3-staging 2.2.1-staging The former can be treated as master usually is: It is for development on what will become 2.3 and is now open for commits. This branch will be merged into master

Re: LyX2.2rc1 hidden windows bug(?) on Mac

> On 2016Apr15, at 13:20, Stephan Witt wrote: > > Am 15.04.2016 um 12:56 schrieb Anders Ekberg : >> >> In the newly released 2.2rc1 on Mac (latest OS) open two documents in two >> windows. Select the frontmost and select View > Hidden and the document in >> the

Re: Lyx-rc1 feedback

Le 16/04/2016 05:43, Stephan Witt a écrit : Am 15.04.2016 um 16:40 schrieb mn : I just noticed in the logs, that this is superfluous since TeXLive2015. Maybe this info could be included in the description of that module? Jürgen mentioned it here