Re: [patch] use setProcessEnvironment, not shell escape (cmd / env)

On Sun, Nov 01, 2015 at 11:47:42PM -0500, PhilipPirrip wrote: > Hi Enrico, thank you for your response. I hope the others will help us > resolve this too. Given the overwhelming amount of replies, I doubt anyone is interested in this matter. > I'd rather call this a bug in the script than in

[patch] Finding the generated latex file

Le 28/10/2015 16:39, Ilan a écrit : Thanks David and Stephan. My problem is that I'm working on a multi-file project so under the tmp directory there are several directories and the location of the Latex file depends on the file I compiled (and of course the tmp directory has a different name

Re: Any alpha blockers?

On Mon, Nov 02, 2015 at 05:57:37PM -0800, Pavel Sanda wrote: > Jean-Marc Lasgouttes wrote: > > Note that we missed LyX 20th birthday: while Lyrix was released circa July > > 1995, the first real LyX release probably happened in september 1995. The > > first long-lived version was 0.7, which got

Re: [patch] use setProcessEnvironment, not shell escape (cmd / env)

On 11/02/2015 03:16 PM, Enrico Forestieri wrote: This last observation suggests what is the minimal change to be performed, i.e., let the latex run work as if the document dir was the current directory. This means setting the relevant environment variables such that the document dir is also

Re: Any alpha blockers?

On Mon, Nov 02, 2015 at 11:37:06AM +0100, Jean-Marc Lasgouttes wrote: > Le 02/11/2015 03:42, Scott Kostyshak a écrit : > >Does anyone have an issue that they think should be considered as an > >alpha blocker? > > Not me. Let's get this alpha out! Sounds good. I should have time on Wednesday to

Re: [patch] use setProcessEnvironment, not shell escape (cmd / env)

On Mon, Nov 02, 2015 at 12:26:36PM -0500, PhilipPirrip wrote: > On 11/02/2015 10:44 AM, Enrico Forestieri wrote: > >On Sun, Nov 01, 2015 at 11:47:42PM -0500, PhilipPirrip wrote: > > > >>Hi Enrico, thank you for your response. I hope the others will help us > >>resolve this too. > > > >Given the

Re: bug 9626: new handling of "LyX" is unintuitive

Richard Heck wrote: > On 10/25/2015 07:43 AM, Kornel Benko wrote: >> Am Sonntag, 25. Oktober 2015 um 12:04:36, schrieb Georg Baum >> >>> PhilipPirrip wrote: >>> LibreOffice has it as "Special Characters". Fedora Linux has an application called "Character

Re: Plan for the current testing situation

Am Sonntag, 1. November 2015 um 22:41:39, schrieb Scott Kostyshak > Thanks to all of those participating in the discussions about tests. I have > learned a lot the last couple of weeks. Thank you also to those who have tried > to run the tests. This to me is a great step

Re: lyx2lyx bugs from export tests

Richard Heck wrote: > I think it would be a perfectly reasonable requirement from now on > ---say, starting in the 2.3.x development cycle---that every format > change be accompanied by some kind of test file that illustrates the use > of the new feature (that's what it usually is) and that can

Re: Plan for the current testing situation

Scott Kostyshak wrote: > So in summary, regarding the XeTeX + TeX fonts, I propose the above policy > to start with; and if we find that there really is such a low signal to > noise ratio then we can change our minds and ignore them. But we will > never know what the signal to noise ratio is if

Re: status update on the export tests

Am Montag, 2. November 2015 um 21:31:12, schrieb Kornel Benko > Am Montag, 2. November 2015 um 11:21:09, schrieb Kornel Benko > > Am Montag, 2. November 2015 um 08:36:05, schrieb Guenter Milde > > > > > Dear Scott and Kornel, > > > > > > On

Unit testing

Dear all, I have prepared a unit test framework based on google-test (gtest). You can see the commits at http://git.lyx.org/?p=developers/vfr/lyx.git;a=shortlog;h=refs/heads/tests. It includes gtest-1.7.0 (permitted by the license). Unit testing can be enabled by running CMake with

Re: [patch] use setProcessEnvironment, not shell escape (cmd / env)

On Mon, Nov 02, 2015 at 09:16:41PM +0100, Enrico Forestieri wrote: > On Mon, Nov 02, 2015 at 12:26:36PM -0500, PhilipPirrip wrote: > > > On 11/02/2015 10:44 AM, Enrico Forestieri wrote: > > >On Sun, Nov 01, 2015 at 11:47:42PM -0500, PhilipPirrip wrote: > > > > > >>Hi Enrico, thank you for your

Re: status update on the export tests

Am Montag, 2. November 2015 um 11:21:09, schrieb Kornel Benko > Am Montag, 2. November 2015 um 08:36:05, schrieb Guenter Milde > > > Dear Scott and Kornel, > > > > On 2015-11-02, Scott Kostyshak wrote: > > > On Sun, Nov 01, 2015 at 10:36:17PM +0100, Kornel

Re: Any alpha blockers?

Dear Scott, On 2015-11-02, Scott Kostyshak wrote: > In fact, at some point (I guess for 1.6?) the criteria for going from > beta to RC was that there is no dataloss bug. The only dataloss bug > with a 2.2.0 milestone is #9362. I don't think it is an alpha blocker, but #9830 is in fact a

Re: status update on the export tests

Dear Scott and Kornel, On 2015-11-02, Scott Kostyshak wrote: > On Sun, Nov 01, 2015 at 10:36:17PM +0100, Kornel Benko wrote: >> Am Sonntag, 1. November 2015 um 21:27:11, schrieb Guenter Milde >> >> > Could we introduce a new status "suspended" - meaning just skip the >> >

Re: status update on the export tests

On 2015-11-02, Scott Kostyshak wrote: > Good point. On the other hand, if we make regex changes then it is > harder to revert them. Problems have come up before of us > misconstructing the regexes. If possible, make separate regexp patterns for separate "fail reasons". Then, we just have to

Re: [patch] use setProcessEnvironment, not shell escape (cmd / env)

On 11/02/2015 10:44 AM, Enrico Forestieri wrote: On Sun, Nov 01, 2015 at 11:47:42PM -0500, PhilipPirrip wrote: Hi Enrico, thank you for your response. I hope the others will help us resolve this too. Given the overwhelming amount of replies, I doubt anyone is interested in this matter. Oh

Re: [patch] Finding the generated latex file

On 3/11/2015 7:38 a.m., Guillaume Munch wrote: Le 28/10/2015 16:39, Ilan a écrit : Thanks David and Stephan. My problem is that I'm working on a multi-file project so under the tmp directory there are several directories and the location of the Latex file depends on the file I compiled (and

Re: [patch] Finding the generated latex file

Le 02/11/2015 21:10, Andrew Parsloe a écrit : Your proposed button would also solve #9211 "Make the lyxpreview.log files accessible within LyX". I agree, part of this idea comes from all the times I had to debug lyx previews (but not only). For the interface, I also propose to substitute

"view XeTeX" toolbar button

On 2015-11-02, Scott Kostyshak wrote: > On Sun, Nov 01, 2015 at 10:31:32PM +, Guenter Milde wrote: >> On 2015-11-01, Scott Kostyshak wrote: ... >> >> While there is a use case for LuaTeX and TeX fonts, I can't see a >> >> reason to use XeTeX instead of pdflatex with TeX fonts! >> > The use

Re: status update on the export tests

Am Montag, 2. November 2015 um 08:36:05, schrieb Guenter Milde > Dear Scott and Kornel, > > On 2015-11-02, Scott Kostyshak wrote: > > On Sun, Nov 01, 2015 at 10:36:17PM +0100, Kornel Benko wrote: > >> Am Sonntag, 1. November 2015 um 21:27:11, schrieb Guenter Milde > >>

Re: lyx2lyx bugs from export tests

Am Sonntag, 1. November 2015 um 20:14:40, schrieb Richard Heck > On 11/01/2015 08:05 PM, Scott Kostyshak wrote: > > On Sun, Nov 01, 2015 at 09:56:55PM +0100, Georg Baum wrote: > >> Scott Kostyshak wrote: > >> > >>> On Sun, Nov 01, 2015 at 11:52:08AM -0500, Richard Heck wrote: >

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

On Mon, Nov 02, 2015 at 10:40:27PM +, Guenter Milde wrote: > On 2015-11-01, Guenter Milde wrote: > > Dear Scott, > > > thanks for the patch. > > I modified it to use UTF8 with XeTeX without the > \inputencoding commands. A short test here showed that this > helps with Umlauts or Cyrillic

Re: [patch] Finding the generated latex file

Le 02/11/2015 23:50, Scott Kostyshak a écrit : On Mon, Nov 02, 2015 at 09:49:24PM +, Guillaume Munch wrote: Le 02/11/2015 21:10, Andrew Parsloe a écrit : Your proposed button would also solve #9211 "Make the lyxpreview.log files accessible within LyX". I agree, part of this idea comes

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

On 2015-11-01, Guenter Milde wrote: > Dear Scott, > thanks for the patch. I modified it to use UTF8 with XeTeX without the \inputencoding commands. A short test here showed that this helps with Umlauts or Cyrillic charactes in the PDF Info. Give it a try. Günter Exec: git 'diff' 2>&1 Dir:

Re: [patch] Finding the generated latex file

On Mon, Nov 02, 2015 at 09:49:24PM +, Guillaume Munch wrote: > Le 02/11/2015 21:10, Andrew Parsloe a écrit : > >Your proposed button would also solve #9211 "Make the lyxpreview.log > >files accessible within LyX". > > > > > I agree, part of this idea comes from all the times I had to debug

Re: Any alpha blockers?

Le 02/11/2015 09:03, Guenter Milde a écrit : Besides this, #9830 prevents us from making documents more robust avoiding non-ASCII characters in the PDF Header Information (e.g. replacing Stöhr with St\"{o}hr) to solve some export test issues. I agree that this bug is annoying, but it is

Re: Upgrade to boost 1.59?

Am 02.11.2015 um 11:40 schrieb Jean-Marc Lasgouttes: Le 01/11/2015 16:51, Scott Kostyshak a écrit : On Sat, Oct 31, 2015 at 11:08:51PM +0100, Peter Kümmel wrote: Am 25.10.2015 um 06:19 schrieb Scott Kostyshak: On Fri, Oct 23, 2015 at 06:13:03PM +0200, Vincent van Ravesteijn wrote: I have it

Re: Upgrade to boost 1.59?

Le 01/11/2015 16:51, Scott Kostyshak a écrit : On Sat, Oct 31, 2015 at 11:08:51PM +0100, Peter Kümmel wrote: Am 25.10.2015 um 06:19 schrieb Scott Kostyshak: On Fri, Oct 23, 2015 at 06:13:03PM +0200, Vincent van Ravesteijn wrote: I have it documented somewhere. Should I put it in

Re: Any alpha blockers?

Le 02/11/2015 03:42, Scott Kostyshak a écrit : Does anyone have an issue that they think should be considered as an alpha blocker? Not me. Let's get this alpha out! Note that we missed LyX 20th birthday: while Lyrix was released circa July 1995, the first real LyX release probably happened

Re: [patch] Finding the generated latex file

On Tue, Nov 03, 2015 at 12:11:08AM +, Guillaume Munch wrote: > >The "Open directory..." could also get rid of the "Show Output Anyway" > >button for the same reasoning as (1) above. I like the "Show Output > >Anyway" button how it is, but I'm not sure if that's because I just got > >used to

Re: [patch] Finding the generated latex file

Le 03/11/2015 00:41, Scott Kostyshak a écrit : On Tue, Nov 03, 2015 at 12:11:08AM +, Guillaume Munch wrote: The "Open directory..." could also get rid of the "Show Output Anyway" button for the same reasoning as (1) above. I like the "Show Output Anyway" button how it is, but I'm not sure

Re: [patch] update modernCV layout file

Guenter Milde wrote: > > Stating more than that sounds like overkill. > > I still favour specifying a required TeXLive version based on these > considerations. > > If we take the conservative route, this would be TeXLive 2012 that ships > with the current CentOS (v. 7). Quickly skimming

Re: [patch] Finding the generated latex file

On Tue, Nov 03, 2015 at 01:05:58AM +, Guillaume Munch wrote: > >Looking at what other programs do in similar (but slightly different) > >situations: > > > >evince and firefox both have: > >Open Containing Folder > > > >fslint has: > >Open Folder > > > >filelight has: > >Open File Manager Here

RFC: better submenu for tables

If you open the submenu of tables you see many entries. In my opinion too many, at least too many for laptops with small screens. In general I think it should be less crowded. Thus a proposal: - everything is removed for which we also have toolbar button. (If users disabled the automatic show

Re: Any alpha blockers?

Jean-Marc Lasgouttes wrote: > Note that we missed LyX 20th birthday: while Lyrix was released circa July > 1995, the first real LyX release probably happened in september 1995. The > first long-lived version was 0.7, which got released at the end of > september. > > Source:

Re: [patch] Finding the generated latex file

Le 02/11/2015 18:38, Guillaume Munch a écrit : Le 28/10/2015 16:39, Ilan a écrit : Thanks David and Stephan. My problem is that I'm working on a multi-file project so under the tmp directory there are several directories and the location of the Latex file depends on the file I compiled (and of

Re: Upgrade to boost 1.59?

Le 02/11/2015 12:34, Peter Kümmel a écrit : The scripts removes all existing files and adds all found by bcp. Four files were deleted, ( git diff 04be61ea8 --name-status | grep D ) OK, thanks. But bcp is called with these headers: [...] so, when something has changed there, then we have