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

Am 02.11.2015 um 16:44 schrieb Enrico Forestieri : > 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

Re: [patch] Finding the generated latex file

Am 03.11.2015 um 04:58 schrieb Guillaume Munch : > 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

Re: [patch] Finding the generated latex file

On 11/02/2015 10:58 PM, Guillaume Munch wrote: Pushed at f441590c. Windows/OSX users, please report if it does not work. Hey Guillaume, Bad news, it didn't work on Windows. Qt 4.8, VS2010, WinXP/VirtualBox This was the error message: lyx\src\frontends\qt4\GuiLog.cpp (207): Unable to open QUrl

Re: [LyX/master] Add "Open Containing Directory" button to the log dialog (#9211, #9834)

Le 03/11/2015 04:57, Guillaume Munch a écrit : commit f441590c8e0b5e970fbdd656198ec4993dfecb43 Author: Guillaume Munch Date: Mon Nov 2 18:19:40 2015 + Add "Open Containing Directory" button to the log dialog (#9211, #9834) It takes the place of the "Copy to

Test LyX 2.2.0 with Retina display

Hey, i would like to test LyX 2.2.0 with Retina display on MBP Retina 13 running OS X 10.10 or 10.11. If possible, please let me know when you have installation files for the development version of 2.2.0 available. Thanks, Sven Goedeke

Re: Unit testing

Le 02/11/2015 21:36, Vincent van Ravesteijn a écrit : 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). Hi

shortcut clash with German locale

Dear LyXers, when I open a fresh compiled LyX here (German locale), I get the error frontends/qt4/Menus.cpp (735): Menu warning: menu entries "Logos|L" and "Sichtbares Leerzeichen|L" share the same shortcut. Günter

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

On 2015-11-02, Scott Kostyshak wrote: > On Mon, Nov 02, 2015 at 10:40:27PM +, Guenter Milde wrote: Dear Scott, >> > thanks for the patch. >> I modified it to use UTF8 with XeTeX without the >> \inputencoding commands. ... > I would say go ahead and commit if you are satisfied with it.

Re: Unit testing

>> Any comments ? Shall I proceed to push this to master ? >> >> Vincent >> > > Having a unit test framework integrated is a very good idea! > > Why have you chosen gtest and not QTest? Does gtest has interesting > features which QTest does not have? I'm not very experienced with unit testing, so

Re: Unit testing

Am 02.11.2015 um 21:36 schrieb Vincent van Ravesteijn: 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

Re: [LyX/master] Add "Open Containing Directory" button to the log dialog (#9211, #9834)

Le 03/11/2015 08:32, Jean-Marc Lasgouttes a écrit : Le 03/11/2015 04:57, Guillaume Munch a écrit : commit f441590c8e0b5e970fbdd656198ec4993dfecb43 Author: Guillaume Munch Date: Mon Nov 2 18:19:40 2015 + Add "Open Containing Directory" button to the log dialog (#9211,

Re: [LyX/master] Add "Open Containing Directory" button to the log dialog (#9211, #9834)

Le 03/11/2015 07:35, Kornel Benko a écrit : Am Dienstag, 3. November 2015 um 04:57:45, schrieb Guillaume Munch commit f441590c8e0b5e970fbdd656198ec4993dfecb43 Author: Guillaume Munch Date: Mon Nov 2 18:19:40 2015 + Add "Open Containing Directory"

Re: [patch] Finding the generated latex file

Le 03/11/2015 08:27, PhilipPirrip a écrit : On 11/02/2015 10:58 PM, Guillaume Munch wrote: Pushed at f441590c. Windows/OSX users, please report if it does not work. Hey Guillaume, Bad news, it didn't work on Windows. Qt 4.8, VS2010, WinXP/VirtualBox This was the error message:

Re: [patch] Finding the generated latex file

Le 03/11/2015 08:59, Stephan Witt a écrit : Am 03.11.2015 um 04:58 schrieb Guillaume Munch >: 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

Re: [patch] Finding the generated latex file

Am 03.11.2015 um 17:39 schrieb Guillaume Munch : > Le 03/11/2015 16:16, Stephan Witt a écrit : >> Am 03.11.2015 um 16:36 schrieb Guillaume Munch : >>> >>> Do you mean that the patch now causes this error message? Under which >>> circumstances precisely? Is it that if

Make master-buffer-update (and -view) compile current document when there is no master

Hi, I was wondering if it would be possible to make master-buffer-update (and -view) compile the current document when there is no master defined. It will reduce the psychological overhead involved with remembering to press two different shortcuts to achieve the same goal (compile the whole

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

On Tue, Nov 03, 2015 at 02:29:32AM -0500, PhilipPirrip wrote: > 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

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

On Tue, Nov 03, 2015 at 08:24:49PM +0100, Enrico Forestieri wrote: > On Tue, Nov 03, 2015 at 02:29:32AM -0500, PhilipPirrip wrote: > > 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

Re: [LyX/master] Add "Open Containing Directory" button to the log dialog (#9211, #9834)

On Tue, Nov 03, 2015 at 04:14:55PM +, Guillaume Munch wrote: > Le 03/11/2015 16:10, Kornel Benko a écrit : > > > >It is the same, opens with gvim. But in the mean time I learned a new gvim > >command ':Ex[plore]', which > >shows the content of this directory. And one can select files (e.g.

Re: [patch] Finding the generated latex file

On Tue, Nov 03, 2015 at 06:03:36PM +0100, Stephan Witt wrote: > Am 03.11.2015 um 17:39 schrieb Guillaume Munch : > > > So the error message is valid. The solution would be to make it clearer. > > Maybe one could show a better message depending on the failure. If it's > > "resource

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

On Tue, Nov 03, 2015 at 06:49:01AM -0800, Kornel Benko wrote: > Am Dienstag, 3. November 2015 um 12:40:22, schrieb Guenter Milde > > > On 2015-11-02, Scott Kostyshak wrote: > > > On Mon, Nov 02, 2015 at 10:40:27PM +, Guenter Milde wrote: > > > > Dear Scott, > > > > >> >

Re: [patch] Finding the generated latex file

On Tue, Nov 03, 2015 at 03:45:03PM +, Guillaume Munch wrote: > Le 03/11/2015 08:27, PhilipPirrip a écrit : > >On 11/02/2015 10:58 PM, Guillaume Munch wrote: > >>Pushed at f441590c. Windows/OSX users, please report if it does not work. > > > >Hey Guillaume, > >Bad news, it didn't work on

RE: Make master-buffer-update (and -view) compile current document when there is no master

> This makes sense IMHO. Please file an enhancement request at > http://www.lyx.org/trac/wiki/BugTrackerHome so that it does not get > forgotten. Done (#9842). Thank you. Best,JoonFrom: joon...@outlook.com To: lyx-devel@lists.lyx.org Subject: Make master-buffer-update (and -view) compile

Re: [LyX/master] Fix algorithm that computes horizontal scroll offset

On Mon, Nov 02, 2015 at 11:18:42AM +0100, Jean-Marc Lasgouttes wrote: > commit 1f0d210ab56057f35960a3b86f5fa1e03ef8ecd0 > Author: Jean-Marc Lasgouttes > Date: Tue Oct 27 16:11:01 2015 +0100 > > Fix algorithm that computes horizontal scroll offset > > Rewrite

Re: Unit testing

Vincent van Ravesteijn wrote: > On Tue, Nov 3, 2015 at 2:28 PM, Jean-Marc Lasgouttes > wrote: >> >> Hi Vincent, >> >> What is the difference with the tests we current use (I mean the "make >> check" sort). The same but with better interface? The overhead to add a test with

Re: shortcut clash with German locale

Guenter Milde wrote: > Dear LyXers, > > when I open a fresh compiled LyX here (German locale), I get the error > > frontends/qt4/Menus.cpp (735): Menu warning: menu entries "Logos|L" and > "Sichtbares Leerzeichen|L" share the same shortcut. Thanks, this is fixed now. It might happen for

Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file

Guillaume Munch wrote: > > > I am bringing this to the list due to the timing, due to the fact that > it is a file format change, and due to the fact that it looks severe in > the above context. > > I suggest moving these settings to the user preferences. >

Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file

Le 03/11/2015 19:49, LyX Ticket Tracker a écrit : #9841: Preferences specific to the user and not to the file should not be recorded in the file -+ Reporter: gadmm| Owner: lasgouttes Type: defect | Status: new Priority:

Re: Make master-buffer-update (and -view) compile current document when there is no master

Joon Ro wrote: > Hi, > I was wondering if it would be possible to make master-buffer-update (and > -view) compile the current document when there is no master defined. It > will reduce the psychological overhead involved with remembering to press > two different shortcuts to achieve the same goal

Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file

Le 03/11/2015 21:16, Georg Baum a écrit : Guillaume Munch wrote: I am bringing this to the list due to the timing, due to the fact that it is a file format change, and due to the fact that it looks severe in the above context. I suggest moving these

Re: [LyX/master] Add warning message if we do no conversion.

On 11/01/2015 08:26 PM, Scott Kostyshak wrote: On Sun, Nov 01, 2015 at 08:04:28PM -0500, Richard Heck wrote: So it would only happen from the command line in which case the warning can be ignored easily enough. I don't know if I like this asymmetry between GUI and command line. All I meant

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

On 11/03/2015 06:38 PM, PhilipPirrip wrote: Just curious: what and when executes the code in os_win32.cpp (os_.cpp in general). Whatever I did to test the patch, these functions were not called. The one Enrico modified is called when you try to view or edit a file that is referenced from

Re: [patch] Finding the generated latex file

On 4/11/2015 11:07 a.m., Scott Kostyshak wrote: On Tue, Nov 03, 2015 at 06:03:36PM +0100, Stephan Witt wrote: Am 03.11.2015 um 17:39 schrieb Guillaume Munch : So the error message is valid. The solution would be to make it clearer. Maybe one could show a better message

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

On Tue, Nov 03, 2015 at 08:30:53PM -0500, Richard Heck wrote: > On 11/03/2015 06:38 PM, PhilipPirrip wrote: > >Just curious: what and when executes the code in os_win32.cpp (os_.cpp > >in general). Whatever I did to test the patch, these functions were not > >called. > > The one Enrico

Re: lyx2lyx bugs from export tests

On Sun, Nov 01, 2015 at 07:43:57PM -0500, Scott Kostyshak wrote: > On Sun, Nov 01, 2015 at 04:30:31PM -0500, Richard Heck wrote: > > > The problem is that EmbeddedObjects.lyx was already format 498, and lyx2lyx > > seems to do the wrong thing when asked to convert it to the format it > > already

Re: lyx2lyx bugs from export tests

On Tue, Nov 03, 2015 at 06:22:11PM -0500, Scott Kostyshak wrote: > On Sun, Nov 01, 2015 at 07:43:57PM -0500, Scott Kostyshak wrote: > > On Sun, Nov 01, 2015 at 04:30:31PM -0500, Richard Heck wrote: > > > > > The problem is that EmbeddedObjects.lyx was already format 498, and > > > lyx2lyx > > >

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

Just curious: what and when executes the code in os_win32.cpp (os_.cpp in general). Whatever I did to test the patch, these functions were not called.

Re: Many tex2lyx failing now on master

Am 26.10.2015 um 21:36 schrieb Vincent van Ravesteijn: Well yes, there is no "env" command on Windows. Thanks to Kornel this is now fixed. Besides that, running is a nightmare: - Somehow tex2lyx often deadlocks when outputting errors, Indeed. When I re-run, it works. - I need to have

Re: lyx2lyx bugs from export tests

Am 04.11.2015 um 00:23 schrieb Scott Kostyshak: Uwe, can you take a look at this bug? I think it has to do with the 491 and 492 format changes. Thanks for the pointer. In lyx2lyx I forgot to add the xcolor package to the preamble. This is now fixed:

Re: lyx2lyx bugs from export tests

On Wed, Nov 04, 2015 at 01:38:37AM +0100, Uwe Stöhr wrote: > Am 04.11.2015 um 00:23 schrieb Scott Kostyshak: > > >>Uwe, can you take a look at this bug? I think it has to do with the 491 > >>and 492 format changes. > > Thanks for the pointer. > > In lyx2lyx I forgot to add the xcolor package to

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

Hi Vincent, On Sun, Oct 11, 2015 at 10:54:15PM +0200, Vincent Viguié wrote: > Dear developer(s) > I am writing you after reading this thread: > http://latex-community.org/forum/viewtopic.php?f=19=24987 > First, thank you very much for developing Lyx, a great software which I use > on a daily

Re: [LyX/master] Add warning message if we do no conversion.

On Tue, Nov 03, 2015 at 08:14:30PM -0500, Richard Heck wrote: > On 11/01/2015 08:26 PM, Scott Kostyshak wrote: > >On Sun, Nov 01, 2015 at 08:04:28PM -0500, Richard Heck wrote: > >>So it would only happen from the command line in which case the warning > >>can be ignored easily enough. > >I don't

Re: [patch] Finding the generated latex file

On 11/03/2015 10:45 AM, Guillaume Munch wrote: Bad news, it didn't work on Windows. Qt 4.8, VS2010, WinXP/VirtualBox On Linux, it worked with two AND three slashes: both Qt 4.8 and Qt 5.5; Gnome 3.18, Fedora 23. Thanks for the report and the extra step in testing. Please try again with latest

Re: Test LyX 2.2.0 with Retina display

On Tue, Nov 03, 2015 at 01:52:31PM +0100, Sven Goedeke wrote: > Hey, > > i would like to test LyX 2.2.0 with Retina display on MBP Retina 13 running > OS X 10.10 or 10.11. If possible, please let me know when you have > installation files for the development version of 2.2.0 available. Hi

Re: #9841: Preferences specific to the user and not to the file should not be recorded in the file

Guillaume Munch wrote: > For \track_changes, I do not understand your rationale for making it a > setting of the document. It is not locked on, so the user who edits the > documentations has to know in any case that he should track changes (if I > had not been told to, then I'd have turned it

Re: Plan for the current testing situation

On Mon, Nov 02, 2015 at 09:26:07PM +0100, Kornel Benko wrote: > > It seems to me that the underlying causes of the XeTeX + TeX fonts tests > > will > > not be fixed anytime soon (and that this is OK) so we have two options if we > > want to clean up the test output. We can either invert the

Re: status update on the export tests

On Mon, Nov 02, 2015 at 09:36:02PM +0100, Kornel Benko wrote: > 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

Re: Plan for the current testing situation

On Mon, Nov 02, 2015 at 09:21:23PM +0100, Georg Baum wrote: > 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

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

Am Dienstag, 3. November 2015 um 12:40:22, schrieb Guenter Milde > On 2015-11-02, Scott Kostyshak wrote: > > On Mon, Nov 02, 2015 at 10:40:27PM +, Guenter Milde wrote: > > Dear Scott, > > >> > thanks for the patch. > > >> I modified it to use UTF8 with XeTeX without

Re: Unit testing

On Tue, Nov 3, 2015 at 2:28 PM, Jean-Marc Lasgouttes wrote: > Le 02/11/2015 21:36, Vincent van Ravesteijn a écrit : >> >> Dear all, >> >> I have prepared a unit test framework based on google-test (gtest). You >> can see the commits at >> >>

Re: [patch] Finding the generated latex file

Am 03.11.2015 um 16:36 schrieb Guillaume Munch : > Le 03/11/2015 08:59, Stephan Witt a écrit : >> Am 03.11.2015 um 04:58 schrieb Guillaume Munch > >: >> >>> Le 02/11/2015 18:38, Guillaume Munch a écrit : Le 28/10/2015 16:39, Ilan a écrit :

Re: [LyX/master] Add "Open Containing Directory" button to the log dialog (#9211, #9834)

Am Dienstag, 3. November 2015 um 15:32:34, schrieb Guillaume Munch > Le 03/11/2015 07:35, Kornel Benko a écrit : > > Am Dienstag, 3. November 2015 um 04:57:45, schrieb Guillaume Munch > > > >> commit f441590c8e0b5e970fbdd656198ec4993dfecb43 > >> Author: Guillaume

Re: [LyX/master] Add "Open Containing Directory" button to the log dialog (#9211, #9834)

Le 03/11/2015 16:10, Kornel Benko a écrit : It is the same, opens with gvim. But in the mean time I learned a new gvim command ':Ex[plore]', which shows the content of this directory. And one can select files (e.g. click on filenames) and open them. For me it is OK ... OK. Only thing is

Re: [LyX/master] Add "Open Containing Directory" button to the log dialog (#9211, #9834)

Am Dienstag, 3. November 2015 um 16:14:55, schrieb Guillaume Munch > Le 03/11/2015 16:10, Kornel Benko a écrit : > > > > It is the same, opens with gvim. But in the mean time I learned a new gvim > > command ':Ex[plore]', which > > shows the content of this directory. And one can

Re: [patch] Finding the generated latex file

Le 03/11/2015 16:16, Stephan Witt a écrit : Am 03.11.2015 um 16:36 schrieb Guillaume Munch : Do you mean that the patch now causes this error message? Under which circumstances precisely? Is it that if the directory is open in the finder, then LyX cannot remove the directory?

Re: [patch] Finding the generated latex file

Le 03/11/2015 16:39, Guillaume Munch a écrit : Le 03/11/2015 16:16, Stephan Witt a écrit : Am 03.11.2015 um 16:36 schrieb Guillaume Munch : Do you mean that the patch now causes this error message? Under which circumstances precisely? Is it that if the directory is open in the