Re: macron below vs. minus sign below (was tex2lyx tests failing on master)

2015-10-11 Thread Scott Kostyshak
On Mon, Sep 14, 2015 at 09:45:05AM +, Guenter Milde wrote: > Dear Georg, > > thank you for looking into this. > > On 2015-09-13, Georg Baum wrote: > > Guenter Milde wrote: > > ... > > > ... One thing I have learned during many years of software development > > is that source code and unit t

Re: Some buttons on Maths palette don't work!

2015-10-11 Thread Scott Kostyshak
On Mon, Oct 12, 2015 at 04:49:07AM +0200, Stephan Witt wrote: > Am 12.10.2015 um 04:15 schrieb Scott Kostyshak : > > > On Sun, Oct 11, 2015 at 10:51:17AM +0200, Stephan Witt wrote: > >> Am 11.10.2015 um 00:01 schrieb Scott Kostyshak : > >> > >>> On Sat, Oct 10, 2015 at 09:26:34PM +0200, Stephan W

Pixmap cache is broken for master

2015-10-11 Thread Stephan Witt
If Q_WS_X11 and QPA_XCB are undefined it's possible to use Qt's pixmap cache to speed up the drawing. ATM, this seems to be broken (for HiDPI and Qt5 only?). The placement of the text isn't correct while pixmap cache is enabled. Does it make sense to have this feature anymore on recent systems? I

Re: Some buttons on Maths palette don't work!

2015-10-11 Thread Stephan Witt
Am 12.10.2015 um 04:15 schrieb Scott Kostyshak : > On Sun, Oct 11, 2015 at 10:51:17AM +0200, Stephan Witt wrote: >> Am 11.10.2015 um 00:01 schrieb Scott Kostyshak : >> >>> On Sat, Oct 10, 2015 at 09:26:34PM +0200, Stephan Witt wrote: Am 10.10.2015 um 20:40 schrieb Scott Kostyshak : >>>

Re: [LyX/master] Comply with rule-of-three

2015-10-11 Thread Scott Kostyshak
On Sun, Oct 11, 2015 at 11:20:15AM +0200, Georg Baum wrote: > commit cea2d71e641e6a4023128a367d1cd5a593ed1706 > Author: Georg Baum > Date: Sun Oct 11 11:16:09 2015 +0200 > > Comply with rule-of-three > > The rule-of-three says that if any of virtual destructor, copy constructor >

Re: Some buttons on Maths palette don't work!

2015-10-11 Thread Scott Kostyshak
On Sun, Oct 11, 2015 at 10:51:17AM +0200, Stephan Witt wrote: > Am 11.10.2015 um 00:01 schrieb Scott Kostyshak : > > > On Sat, Oct 10, 2015 at 09:26:34PM +0200, Stephan Witt wrote: > >> Am 10.10.2015 um 20:40 schrieb Scott Kostyshak : > >> > >>> On Sat, Oct 10, 2015 at 01:16:42PM -0500, jken...@s

Re: Moving towards a 2.2 release

2015-10-11 Thread Scott Kostyshak
On Sun, Oct 11, 2015 at 12:52:06AM +0100, Guillaume Munch wrote: > Le 10/10/2015 23:25, Scott Kostyshak a écrit : > >On Sat, Oct 10, 2015 at 07:50:59PM +0100, Guillaume Munch wrote: > >>http://www.lyx.org/trac/ticket/9362 : the problem has been quite precisely > >>identified, a decision has to be t

Re: Form is function

2015-10-11 Thread Pavel Sanda
Guillaume Munch wrote: > IMO we shouldn't be shy marking enhancements as high or highest. We should > stop marking them low just because they are enhancements. The "enhancement" > tag is already there to indicate that. To clarify - the coloring scheme currently used dates back to time when I had

Re: Removing 2.2.0 milestone (as opposed to changing to 2.3.0)

2015-10-11 Thread Pavel Sanda
Scott Kostyshak wrote: > I am going to start removing many 2.2.0 milestones if it seems unlikely > the bugs will be fixed for 2.2.0 (i.e. no one has said they are working > on them). If I remember correctly, there was some discussion on this and > most LyX developers prefer this (I think I remember

getting a test version of lyx 2.2.0 for Mac with Retina display

2015-10-11 Thread Vincent Viguié
Dear developer(s) I am writing you after reading this thread: http://latex-community.org/forum/viewtopic.php?f=19&t=24987 First, thank you very much for developing Lyx, a great software which I use on a daily basis when writing scientific papers ! Many people in my lab are also using it, you're

Re: Form is function

2015-10-11 Thread Liviu Andronic
On Sun, Oct 11, 2015 at 4:27 PM, Guillaume Munch wrote: > Le 11/10/2015 12:19, Liviu Andronic a écrit : >> >> This way .x targets are indicative of the relative recent nature of >> the bug, which is still useful info. > > > It is useful to know if a bug is recent, but we already have the bug # and

Re: [LyX/master] Fix cursor movement for large logos (#9628)

2015-10-11 Thread Georg Baum
Guillaume Munch wrote: > Thanks. Can this be easily adapted for > ? I don't think so. Cursor movement in math is a quite separate implementation. Georg

Re: Form is function (was: Removing 2.2.0 milestone (as opposed to changing to 2.3.0))

2015-10-11 Thread Georg Baum
Liviu Andronic wrote: > ALL other bugs fall into two categories: somewhat important if a devel > is interested in the bug, not important if no one will be bothered to > address it. This is why I find Guillaume's proposal unworkable, if I > understood it correctly, in the sense that: How do we defi

Re: Form is function

2015-10-11 Thread Guillaume Munch
Le 11/10/2015 15:27, Guillaume Munch a écrit : I can apply my proposal to the Trac page right now for you to judge, and we can revert it if you are not convinced. ...essentially adding at the end of the page: [[BR]] == High priority defects == [[TicketQuery(order=id,desc=1,format=table,status

Re: Form is function

2015-10-11 Thread Guillaume Munch
Le 11/10/2015 12:19, Liviu Andronic a écrit : This way .x targets are indicative of the relative recent nature of the bug, which is still useful info. It is useful to know if a bug is recent, but we already have the bug # and often the version, no? I think that Guillaumes proposal to use

Re: [LyX/master] Fix cursor movement for large logos (#9628)

2015-10-11 Thread Guillaume Munch
Le 11/10/2015 13:26, Georg Baum a écrit : commit 359aef92f87169ce2683e287bb24bc3d5f46a190 Author: Georg Baum Date: Sun Oct 11 14:21:45 2015 +0200 Fix cursor movement for large logos (#9628) Previously, if one clicked onto a large non-editable inset like the new LyX logo inset,

Re: Form is function (was: Removing 2.2.0 milestone (as opposed to changing to 2.3.0))

2015-10-11 Thread Liviu Andronic
On Sun, Oct 11, 2015 at 11:50 AM, Georg Baum wrote: > Liviu Andronic wrote: > >> While I understand when people want to remove milestones since "if no >> one is working on them they're meaningless", I also agree with >> Guillaume's arguments here: a milestone usually contains some >> information a

Re: IBus compatibility

2015-10-11 Thread Guillaume Munch
Le 11/10/2015 10:32, Georg Baum a écrit : Guillaume Munch wrote: Decision has to be taken about the keyboard issues and deadlock in under Linux with IBus. The issue is going to be solved by Qt5, but unfortunately due to

Re: Polyglossia for LuaTeX in 2.2.0

2015-10-11 Thread Jürgen Spitzmüller
Scott Kostyshak wrote: > Jürgen has improved the situation at b1c68dcc. However, I think he does > not have any time to fix the remaining issues of #9633 before the 2.2.0 > release. That's true, unfortunately. I am swallowed by my new job currently, so do not count on me for the time being (I am

Re: Form is function (was: Removing 2.2.0 milestone (as opposed to changing to 2.3.0))

2015-10-11 Thread Georg Baum
Liviu Andronic wrote: > While I understand when people want to remove milestones since "if no > one is working on them they're meaningless", I also agree with > Guillaume's arguments here: a milestone usually contains some > information about the bug, its intended scope and its importance. The > m

Re: IBus compatibility

2015-10-11 Thread Georg Baum
Guillaume Munch wrote: > Decision has to be taken about the keyboard issues and deadlock in > under Linux with IBus. > > The issue is going to be solved by Qt5, but unfortunately due to > (related to event compression as

Re: Some buttons on Maths palette don't work!

2015-10-11 Thread Stephan Witt
Am 11.10.2015 um 00:01 schrieb Scott Kostyshak : > On Sat, Oct 10, 2015 at 09:26:34PM +0200, Stephan Witt wrote: >> Am 10.10.2015 um 20:40 schrieb Scott Kostyshak : >> >>> On Sat, Oct 10, 2015 at 01:16:42PM -0500, jken...@ssc.wisc.edu wrote: > On Sat, Oct 10, 2015 at 08:40:28AM -0500, jken...

Re: Form is function (was: Removing 2.2.0 milestone (as opposed to changing to 2.3.0))

2015-10-11 Thread Liviu Andronic
On Sun, Oct 11, 2015 at 1:27 AM, Guillaume Munch wrote: > Le 10/10/2015 22:51, Scott Kostyshak a écrit : >> >> I am going to start removing many 2.2.0 milestones if it seems unlikely >> the bugs will be fixed for 2.2.0 (i.e. no one has said they are working >> on them). If I remember correctly, th