Re: Regression in lyx2lyx box alignment

Le 20/10/2015 04:39, Scott Kostyshak a écrit : Many developers pop in and out. I think JMarc is the only developer who is consistent. It is a wonder how he has not gone insane yet (or maybe he is pushing his commits from the inside of an insane asylum?). Am I supposed to resent this? (don't

Re: Many tex2lyx failing now on master

Am Dienstag, 20. Oktober 2015 um 01:04:36, schrieb Uwe Stöhr > Am 19.10.2015 um 20:55 schrieb Scott Kostyshak: > > > There is some at lib/doc/Development.lyx > >> I see lots of diffs of the form > >> > >> #LyX file created by tex2lyx 2.2 > >> -\lyxformat 497 > >> +\lyxformat

Re: Many tex2lyx failing now on master

On 2015-10-19, Uwe Stöhr wrote: > Am 19.10.2015 um 20:55 schrieb Scott Kostyshak: >> There is some at lib/doc/Development.lyx >>> I see lots of diffs of the form >>> #LyX file created by tex2lyx 2.2 >>> -\lyxformat 497 >>> +\lyxformat 498 >>> and the commit ce933b1e14 has incremented the

Re: [LyX/master] Refine lang nesting fix

On Mon, Oct 19, 2015 at 07:59:59PM -0400, Scott Kostyshak wrote: > On Mon, Oct 19, 2015 at 09:24:45PM +0200, Georg Baum wrote: > > Scott Kostyshak wrote: > > > > > http://www.lyx.org/trac/ticket/9633 > > > > I am a bit confused. I thought my fix which I just submitted would address > > this? >

Re: LyX's master is now uncompilable

Guillaume Munch wrote: > I'll let Vincent decide whether he wants to make this change. Sure, our messages crossed each other, I would not have suggested that if I knew that he had time to test. The compilation error could btw easily be fixed by moving the implementation of the methods in a

Re: Regression in lyx2lyx box alignment

Scott Kostyshak wrote: > After rereading the below email I just realized I often use the term > "we" and "us". Sorry about that. I do not mean to pretend like I am > speaking on behalf of everyone (I do not forget that I am a relative > newcommer here!). Instead of taking the time to correct all

Re: Moving towards a 2.2 release

On 2015-10-20, Scott Kostyshak wrote: > On Mon, Oct 19, 2015 at 08:18:30PM +, Guenter Milde wrote: >> I realised that this not only applies to compilation with Xe/LuaTeX which >> is a good thing -- it also catches cases like small letters missing in >> most math-script fonts (To fix the

Re: LyX's master is now uncompilable

Op 19-10-2015 om 23:36 schreef Guillaume Munch: Le 19/10/2015 21:59, Vincent van Ravesteijn a écrit : Op 19 okt. 2015 22:51 schreef "Guillaume Munch" >: > > Le 19/10/2015 21:34, Georg Baum a écrit : >> >> >> The message on the list is related to commit

LyX 2.2 testing OS X 10.11 / retina display

Hi, This is in response to a post by Scott Kosty on latex-community.org. I'd be interested in testing out an OS X build of LyX 2.2 when it's reached the appropriate development stage. Drop me a line with more info when the time comes. Thanks, Ian

Re: Many tex2lyx failing now on master

Guenter Milde wrote: > I updated the lyxformat number in the src/tex2lyx/test/*.lyx.lyx files and > now all tex2lyx tests pass here. Very good. Just to avoid future errors: I assume that you did check before that a simple update of the format number is OK, and that no tex2lyx source code

Re: [LyX/master] Partial fix for #9740 "XeTeX/LuaTeX with TeX fonts problems".

On Tue, Oct 20, 2015 at 07:16:44PM +0200, Günter Milde wrote: > commit 1523fc6023440f10ca0d82a681ded5c060d8fd33 > Author: Günter Milde > Date: Tue Oct 20 19:14:39 2015 +0200 > > Partial fix for #9740 "XeTeX/LuaTeX with TeX fonts problems". > > Fixes output for 3 of

Re: Form is function

On Wed, Oct 14, 2015 at 07:50:54AM +0100, Guillaume Munch wrote: > Scott asked not long ago what could be done to make it easier for > newcomers. It is now clear to me that having a clearer bug tracker > is an aspect that can be improved. In addition, the initial question > was to know what to do

Re: Many tex2lyx failing now on master

Guenter Milde wrote: > On 2015-10-19, Uwe Stöhr wrote: > >> I don't understand what I made wrong. I only changed something in a >> module and added a fileformat change for lyx2lyx. I did not change any >> tex2lxy test file nor did I change tex2lyx code. It is all documented in Development.lyx.

Re: When to court Qt 5.6?

Uwe Stöhr wrote: > Besides this I am still using MSVC 2010. I need to update to MSVC 2012 > or newer and this is another challenge. I already tested MSVC 2012 with > Qt 5.5 with success. Let's see what Qt 5.6 supports and if I can then > still compile LyX 2.1.x with Qt 4.x and MSVC 2010 on the

Re: Change tracking output issues

Am Montag, 19. Oktober 2015 um 14:27:54, schrieb Paul A. Rubin > Hi all, > > I couldn't find an open bug report on either of these, so I thought I'd > ask for input here. The following apply to LyX 2.1.4. > > Issue #1: In the User Guide, section 6.16, the last paragraph says

Re: Change tracking output issues

On Tue, Oct 20, 2015 at 06:15:13PM +0200, Kornel Benko wrote: > Am Montag, 19. Oktober 2015 um 14:27:54, schrieb Paul A. Rubin > > Hi all, > > > > I couldn't find an open bug report on either of these, so I thought I'd > > ask for input here. The following apply to LyX 2.1.4. > >

Re: Change tracking output issues

On Tue, Oct 20, 2015 at 03:49:40PM +, Paul A. Rubin wrote: > Scott Kostyshak lyx.org> writes: > > > > > > Hi Paul, can you send a minimal example to the list so we can see if we > > see the changes in other formats? So to confirm, if you compile with > > XeTeX or LuaTeX you do not see the

Re: Update on the patches

Le 09/10/2015 22:07, Jean-Marc Lasgouttes a écrit : Le 09/10/2015 22:06, Georg Baum a écrit : Even more interesting. I always thought that LyX uses the "use tabs for logical indentation, and spaces for visual alignment" model for C++ code. This way, it does not matter at all whether you display

Re: Many tex2lyx failing now on master

On 2015-10-19, Scott Kostyshak wrote: > On Mon, Oct 19, 2015 at 07:38:12PM +0100, Guillaume Munch wrote: >> Le 19/10/2015 19:12, Scott Kostyshak a écrit : >> >Many tex2lyx tests have started to fail (before it was just 4 and we >> >knew why and I think Günter's recent commit might have fixed

Re: Change tracking output issues

Scott Kostyshak lyx.org> writes: > > Hi Paul, can you send a minimal example to the list so we can see if we > see the changes in other formats? So to confirm, if you compile with > XeTeX or LuaTeX you do not see the changes? Scott, I'm not set up to use LuaTeX (and don't know how to use

Re: Many tex2lyx failing now on master

Am Dienstag, 20. Oktober 2015 um 20:18:33, schrieb Georg Baum > Guenter Milde wrote: > > > On 2015-10-19, Uwe Stöhr wrote: > > > >> I don't understand what I made wrong. I only changed something in a > >> module and added a fileformat change for lyx2lyx. I did

Re: Regression in lyx2lyx box alignment

Am 20.10.2015 um 04:39 schrieb Scott Kostyshak: I CC'ed you on the following emails (it hides that I CC'ed you but if you search for the message in your email client it should show it): Hm, now I see them. There were automatically moved into the spam folder where also all the commit report

Re: LyX's master is now uncompilable

Op 20-10-2015 om 20:06 schreef Georg Baum: Guillaume Munch wrote: I'll let Vincent decide whether he wants to make this change. Sure, our messages crossed each other, I would not have suggested that if I knew that he had time to test. The compilation error could btw easily be fixed by moving

Re: Regression in lyx2lyx box alignment

Uwe Stöhr wrote: > ( I see now in mail-archive.com this thread. It would have been nice to > send me at least a direct mail to assure that I am informed. In the past > I could read the list via NNTP but my ISP dropped that feature. When I > am abroad I don't read mail-archive.com .) Do you mean

Re: [LyX/master] Partial fix for #9740 "XeTeX/LuaTeX with TeX fonts problems".

On 2015-10-20, Scott Kostyshak wrote: > On Tue, Oct 20, 2015 at 07:16:44PM +0200, Günter Milde wrote: >> commit 1523fc6023440f10ca0d82a681ded5c060d8fd33 >> Author: Günter Milde >> Date: Tue Oct 20 19:14:39 2015 +0200 >> Partial fix for #9740 "XeTeX/LuaTeX with TeX fonts

Re: When to court Qt 5.6?

Op 15 okt. 2015 08:37 schreef "Jean-Marc Lasgouttes" : > > Le 15/10/15 01:06, Scott Kostyshak a écrit : > >> LyX 2.2.0 and the following 2.2.x releases will still continue to work >> well with Qt 4.8.6 but will also support Qt 5.6, which brings some >> advantages most notably

Re: back to LyX and therefore questions concerning LyX 2.2

Am 19.10.2015 um 16:42 schrieb Jean-Marc Lasgouttes: Welcome back! Thanks JMarc for the info. PS: and of course my idea of replacing ugly tables with nice formal tables and remove all the spacing hacks you had to do is still waiting for your answer ;) What do you mean? Apparently I missed

Re: When to court Qt 5.6?

Op 20 okt. 2015 02:32 schreef "Uwe Stöhr" : > > Am 15.10.2015 um 01:18 schrieb Scott Kostyshak: > >> Uwe can you confirm that shipping our alpha with Qt 5.6 beta is >> feasible for you? > > > Hi Scott, > > I am open for anything. I think that i will need in any case some help

Re: When to court Qt 5.6?

Op 20 okt. 2015 20:35 schreef "Georg Baum" : > > Uwe Stöhr wrote: > > > Besides this I am still using MSVC 2010. I need to update to MSVC 2012 > > or newer and this is another challenge. I already tested MSVC 2012 with > > Qt 5.5 with success. Let's see what Qt 5.6

Re: Form is function

On Tue, Oct 20, 2015 at 8:52 PM, Scott Kostyshak wrote: > On Wed, Oct 14, 2015 at 07:50:54AM +0100, Guillaume Munch wrote: >> Scott asked not long ago what could be done to make it easier for >> newcomers. It is now clear to me that having a clearer bug tracker >> is an aspect

LyX 2.2 OSX 10.11 - retina display test

Dear all, let me start let me start by saying kudos to all of you! I is really fantastic what Lyx provides especially as an application for scholars around the world. As I quit doing development several years ago I won’t be any help in this regard. Would be more than willing though to

Re: Change tracking output issues

Scott Kostyshak lyx.org> writes: > > On Tue, Oct 20, 2015 at 06:15:13PM +0200, Kornel Benko wrote: > > > > I tried your example, all available pdf formats are displaying the change here. > > (E.g. > > PDF (ps2pdf), PDF (pdflatex), PDF (dvipdfm), PDF (XeTeX), PDF (LuaTeX) > > ) > > > >

Re: Regression in lyx2lyx box alignment

On 10/20/2015 04:07 PM, Georg Baum wrote: ...I mainly use git for LyX development like "svn + stash", and keep two separate working trees for branch and master. I do the same, just because compiling is faster this way (and disk space is cheap). Many git features are confusing for me as

Re: Translations and 2.2.alpha?

On Mon, Oct 19, 2015 at 07:30:07PM +0200, Jean-Marc Lasgouttes wrote: > Le 19/10/2015 19:14, Scott Kostyshak a écrit : > >Well we can adjust the timeframe if necessary (it is already delayed > >because of Qt 5.6 beta delay). If this is important or there is > >precedence then we can delay a couple

Re: Change tracking output issues

On Tue, Oct 20, 2015 at 10:03:27PM +, Paul A. Rubin wrote: > > I did not test (I assume I get the same result as Kornel since I have a > > similar system), but I suppose the next step is to send the .tex files. > > e.g. instead of exporting to PDF (pdflatex) export to LaTeX (pdflatex). I do

Re: LyX 2.2 testing OS X 10.11 / retina display

On Tue, Oct 20, 2015 at 02:43:39PM -0400, Ian Weiner wrote: > Hi, > > This is in response to a post by Scott Kosty on latex-community.org. > > I'd be interested in testing out an OS X build of LyX 2.2 when it's reached > the appropriate development stage. Drop me a line with more info when the >

Re: LyX 2.2 OSX 10.11 - retina display test

On Wed, Oct 21, 2015 at 12:21:11AM +0200, "Mag. Georg Kö" wrote: > Dear all, > > let me start let me start by saying kudos to all of you! I is really > fantastic what Lyx provides especially as an application for scholars around > the world. As I quit doing development several years ago I

Re: Moving towards a 2.2 release

On Tue, Oct 20, 2015 at 05:27:29PM +, Guenter Milde wrote: > On 2015-10-20, Scott Kostyshak wrote: > > On Mon, Oct 19, 2015 at 08:18:30PM +, Guenter Milde wrote: > > >> I realised that this not only applies to compilation with Xe/LuaTeX which > >> is a good thing -- it also catches cases

Exception (basic_string) when saving on OSX.

I've been experiencing several exceptions on OSX, using commit 96f64ac0. Sofar I've tracked down one of them: A (basic_string) exception occurs when saving a document with a sufficient long filename (more than about 18 characters without the extension). Take any .lyx file and add characters to