Re: Re: Re: [PATCH] Add an autotest for #8523 (but how can I get a path for a helper lyx file?)

Am Sonntag, 27. Januar 2013 um 02:10:58, schrieb Scott Kostyshak skost...@lyx.org Should be easy. Ah yes you're right. You are convincing me more and more that out-of-source builds have many advantages and no disadvantages. So all is needed is just to copy the .lyx file there.

Re: Re: Re: [PATCH] Add an autotest for #8523 (but how can I get a path for a helper lyx file?)

On Sun, Jan 27, 2013 at 3:12 AM, Kornel Benko kor...@lyx.org wrote: Am Sonntag, 27. Januar 2013 um 02:10:58, schrieb Scott Kostyshak skost...@lyx.org Should be easy. Ah yes you're right. You are convincing me more and more that out-of-source builds have many advantages and

Re: Re: Re: Re: [PATCH] Add an autotest for #8523 (but how can I get a path for a helper lyx file?)

Am Sonntag, 27. Januar 2013 um 09:12:44, schrieb Kornel Benko kor...@lyx.org I would change the file, there is also no need to remove, on next test it will be overwritten anyway and we can check the result too. TestBegin ../bug-8523.lyx lyx-log.txt 21 KK: \[Home]

Re: Re: Re: Re: [PATCH] Add an autotest for #8523 (but how can I get a path for a helper lyx file?)

Am Sonntag, 27. Januar 2013 um 03:59:49, schrieb Scott Kostyshak skost...@lyx.org ... OK, I will change this. I am in the habit of writing copies of the form cp filename folder1/folder2/ because (1) this prevents type errors such as cp filename folder1/folder2/fielname and (2) the reader of

Re: Re: Re: Re: [PATCH] Add an autotest for #8523 (but how can I get a path for a helper lyx file?)

On Sun, Jan 27, 2013 at 4:13 AM, Kornel Benko kor...@lyx.org wrote: Am Sonntag, 27. Januar 2013 um 03:59:49, schrieb Scott Kostyshak skost...@lyx.org ... OK, I will change this. I am in the habit of writing copies of the form cp filename folder1/folder2/ because (1) this prevents type

Re: Re: Re: Re: Re: [PATCH] Add an autotest for #8523 (but how can I get a path for a helper lyx file?)

Am Sonntag, 27. Januar 2013 um 10:13:59, schrieb Kornel Benko kor...@lyx.org I don't understand. First, on opening bug-8523.lyx you should immediately see a warning which must be addressed. This is where the \[Return] works if XVKBD_HACKED is not automatically set. I will check.

Re: Re: Re: Re: Re: [PATCH] Add an autotest for #8523 (but how can I get a path for a helper lyx file?)

Am Sonntag, 27. Januar 2013 um 04:42:25, schrieb Scott Kostyshak skost...@lyx.org if output is a directory, I would not count on working in later versions of cmake. That command explains it: If output names an existing directory the input file is placed in that directory with its original

Re: Re: Re: Re: Re: [PATCH] Add an autotest for #8523 (but how can I get a path for a helper lyx file?)

On Sun, Jan 27, 2013 at 4:45 AM, Kornel Benko kor...@lyx.org wrote: Am Sonntag, 27. Januar 2013 um 10:13:59, schrieb Kornel Benko kor...@lyx.org I don't understand. First, on opening bug-8523.lyx you should immediately see a warning which must be addressed. This is where the

Re: Re: Re: Re: Re: Re: [PATCH] Add an autotest for #8523 (but how can I get a path for a helper lyx file?)

Am Sonntag, 27. Januar 2013 um 04:51:53, schrieb Scott Kostyshak skost...@lyx.org I got the crash if called manually. Once. I am not able to get the crash again Maybe I should stop trying to get this test to work. I don't think that tests should be this complicated. I'm very

Re: Re: Re: Re: Re: Re: [PATCH] Add an autotest for #8523 (but how can I get a path for a helper lyx file?)

On Sun, Jan 27, 2013 at 4:56 AM, Kornel Benko kor...@lyx.org wrote: Am Sonntag, 27. Januar 2013 um 04:51:53, schrieb Scott Kostyshak skost...@lyx.org I got the crash if called manually. Once. I am not able to get the crash again Maybe I should stop trying to get this test

Modifications of English messages in the pot file

Hello, After updating fr.po for trunk, I suggest these few changes in the sources. One message is unclear IMHO : In PrefPrinterUI.ui, replace 'Setting causes printer command to print to file and then use this actually to print.' with 'Command transmitted to the system to actually print the

Re: Modifications of English messages in the pot file

Jean-Pierre Chrétien wrote: These strings differ in the text and in the tooltip: - in some of the theorems*.inc files 'Alternative Theorem String' - in the svcommon.inc file 'Longest Description Label' This is intentional. The HIG we draw on suggests Header Capitalization (all words

Re: Modifications of English messages in the pot file

Le 27/01/2013 15:56, Jürgen Spitzmüller a écrit : Jean-Pierre Chrétien wrote: These strings differ in the text and in the tooltip: - in some of the theorems*.inc files 'Alternative Theorem String' - in the svcommon.inc file 'Longest Description Label' This is intentional. The HIG we

Re: Restart layout update discussion; was: Re: [patch] final layout patches for branch

Am 26.01.2013 18:23, schrieb Jürgen Spitzmüller: I cannot reproduce the failure you get when removing the linebreak. I can reproduce the failure with a different theme. But I cannot see how the layout update fixes this. Instead, the error goes away if the address declaration in the preamble is

Re: Restart layout update discussion; was: Re: [patch] final layout patches for branch

Am 28.01.2013 03:07, schrieb Uwe Stöhr: OK. I will fix this then. This cannot be fixed, because in trunk the new default theme is used. in branch I cannot use this because the document will then become uncompilable. The linebreak is necessary to get the city in its own line. This is a

Re: make initial configure part of install (esp. Windows) ?

Am 22.01.2013 23:43, schrieb Uwe Stöhr: Isn't there the possibility to either use the miktex-sdk or to call the miktex-updater with command-line options to install the packages we need ? I guess this would go much quicker than to run the configure script to install the packages. The MiKTeX

Re: make initial configure part of install (esp. Windows) ?

On Sun, Jan 27, 2013 at 9:18 PM, Uwe Stöhr uwesto...@web.de wrote: Am 22.01.2013 23:43, schrieb Uwe Stöhr: Isn't there the possibility to either use the miktex-sdk or to call the miktex-updater with command-line options to install the packages we need ? I guess this would go much quicker

Re: Restart layout update discussion; was: Re: [patch] final layout patches for branch

Uwe Stöhr wrote: I don't know why but this does not occur with the new layout in trunk. Of course it does. See attached document. Or show me how to insert a linebreak in the address layout with the casual theme in the new layout that does _not_ trigger a error. Jürgen modernCV-trunk.lyx

Re: [LyX master] chkconfig.ltx: check for KOMA and caption

Uwe Stöhr wrote: +\TestPackage{koma-script} Hm. But you know there is no class called koma-script. Jürgen

Re: Restart layout update discussion; was: Re: [patch] final layout patches for branch

Uwe Stöhr wrote: This cannot be fixed, because in trunk the new default theme is used. in branch I cannot use this because the document will then become uncompilable. No it won't. Attached is a branch version that compiles with the casual theme. All I did here is changing the theme and

Re: Re: Re: [PATCH] Add an autotest for #8523 (but how can I get a path for a helper lyx file?)

Am Sonntag, 27. Januar 2013 um 02:10:58, schrieb Scott Kostyshak > >> > >> Should be easy. > > > > Ah yes you're right. You are convincing me more and more that > > out-of-source builds have many advantages and no disadvantages. So all > > is needed is just to copy the

Re: Re: Re: [PATCH] Add an autotest for #8523 (but how can I get a path for a helper lyx file?)

On Sun, Jan 27, 2013 at 3:12 AM, Kornel Benko wrote: > Am Sonntag, 27. Januar 2013 um 02:10:58, schrieb Scott Kostyshak > > > > >> >> > >> >> Should be easy. > >> > > >> > Ah yes you're right. You are convincing me more and more that > >> > out-of-source

Re: Re: Re: Re: [PATCH] Add an autotest for #8523 (but how can I get a path for a helper lyx file?)

Am Sonntag, 27. Januar 2013 um 09:12:44, schrieb Kornel Benko > I would change the file, there is also no need to remove, on next test it > will be overwritten anyway > and we can check the result too. > > TestBegin ../bug-8523.lyx > lyx-log.txt 2>&1 > KK:

Re: Re: Re: Re: [PATCH] Add an autotest for #8523 (but how can I get a path for a helper lyx file?)

Am Sonntag, 27. Januar 2013 um 03:59:49, schrieb Scott Kostyshak ... > OK, I will change this. I am in the habit of writing copies of the > form "cp filename folder1/folder2/" because (1) this prevents type > errors such as "cp filename folder1/folder2/fielname" and (2) the >

Re: Re: Re: Re: [PATCH] Add an autotest for #8523 (but how can I get a path for a helper lyx file?)

On Sun, Jan 27, 2013 at 4:13 AM, Kornel Benko wrote: > Am Sonntag, 27. Januar 2013 um 03:59:49, schrieb Scott Kostyshak > > > ... > > > >> OK, I will change this. I am in the habit of writing copies of the > >> form "cp filename folder1/folder2/" because (1)

Re: Re: Re: Re: Re: [PATCH] Add an autotest for #8523 (but how can I get a path for a helper lyx file?)

Am Sonntag, 27. Januar 2013 um 10:13:59, schrieb Kornel Benko > > > > I don't understand. First, on opening bug-8523.lyx you should > > immediately see a warning which must be addressed. This is where the > > \[Return] works if XVKBD_HACKED is not automatically set. > > I will

Re: Re: Re: Re: Re: [PATCH] Add an autotest for #8523 (but how can I get a path for a helper lyx file?)

Am Sonntag, 27. Januar 2013 um 04:42:25, schrieb Scott Kostyshak > > if is a directory, I would not count on working in later versions > > of cmake. > > That command explains it: "If names an existing directory the > input file is placed in that directory with its original

Re: Re: Re: Re: Re: [PATCH] Add an autotest for #8523 (but how can I get a path for a helper lyx file?)

On Sun, Jan 27, 2013 at 4:45 AM, Kornel Benko wrote: > Am Sonntag, 27. Januar 2013 um 10:13:59, schrieb Kornel Benko > > > > >> > > >> > I don't understand. First, on opening bug-8523.lyx you should > >> > immediately see a warning which must be addressed. This is

Re: Re: Re: Re: Re: Re: [PATCH] Add an autotest for #8523 (but how can I get a path for a helper lyx file?)

Am Sonntag, 27. Januar 2013 um 04:51:53, schrieb Scott Kostyshak > > > > > > I got the crash if called manually. Once. I am not able to get the crash > > again > > > > Maybe I should stop trying to get this test to work. I don't think > that tests should be this

Re: Re: Re: Re: Re: Re: [PATCH] Add an autotest for #8523 (but how can I get a path for a helper lyx file?)

On Sun, Jan 27, 2013 at 4:56 AM, Kornel Benko wrote: > Am Sonntag, 27. Januar 2013 um 04:51:53, schrieb Scott Kostyshak > > >> > > >> > > >> > I got the crash if called manually. Once. I am not able to get the crash > >> > again > >> > > >> > >> Maybe I

Modifications of English messages in the pot file

Hello, After updating fr.po for trunk, I suggest these few changes in the sources. One message is unclear IMHO : In PrefPrinterUI.ui, replace 'Setting causes printer command to print to file and then use this actually to print.' with 'Command transmitted to the system to actually print the

Re: Modifications of English messages in the pot file

Jean-Pierre Chrétien wrote: > These strings differ in the text and in the tooltip: >- in some of the theorems*.inc files > 'Alternative Theorem String' >- in the svcommon.inc file > 'Longest Description Label' This is intentional. The HIG we draw on suggests Header Capitalization (all

Re: Modifications of English messages in the pot file

Le 27/01/2013 15:56, Jürgen Spitzmüller a écrit : Jean-Pierre Chrétien wrote: These strings differ in the text and in the tooltip: - in some of the theorems*.inc files 'Alternative Theorem String' - in the svcommon.inc file 'Longest Description Label' This is intentional. The HIG we

Re: Restart layout update discussion; was: Re: [patch] final layout patches for branch

Am 26.01.2013 18:23, schrieb Jürgen Spitzmüller: I cannot reproduce the failure you get when removing the linebreak. I can reproduce the failure with a different theme. But I cannot see how the layout update fixes this. Instead, the error goes away if the address declaration in the preamble is

Re: Restart layout update discussion; was: Re: [patch] final layout patches for branch

Am 28.01.2013 03:07, schrieb Uwe Stöhr: OK. I will fix this then. This cannot be fixed, because in trunk the new default theme is used. in branch I cannot use this because the document will then become uncompilable. The linebreak is necessary to get the city in its own line. This is a

Re: make initial configure part of install (esp. Windows) ?

Am 22.01.2013 23:43, schrieb Uwe Stöhr: Isn't there the possibility to either use the miktex-sdk or to call the miktex-updater with command-line options to install the packages we need ? I guess this would go much quicker than to run the configure script to install the packages. The MiKTeX

Re: make initial configure part of install (esp. Windows) ?

On Sun, Jan 27, 2013 at 9:18 PM, Uwe Stöhr wrote: > Am 22.01.2013 23:43, schrieb Uwe Stöhr: > > >>> Isn't there the possibility to either use the miktex-sdk or to call the >>> miktex-updater with >>> command-line options to install the packages we need ? I guess this would >>>

Re: Restart layout update discussion; was: Re: [patch] final layout patches for branch

Uwe Stöhr wrote: > I don't know why but this does not occur with the new layout in trunk. Of course it does. See attached document. Or show me how to insert a linebreak in the address layout with the casual theme in the new layout that does _not_ trigger a error. Jürgen modernCV-trunk.lyx

Re: [LyX master] chkconfig.ltx: check for KOMA and caption

Uwe Stöhr wrote: > +\TestPackage{koma-script} Hm. But you know there is no class called "koma-script". Jürgen

Re: Restart layout update discussion; was: Re: [patch] final layout patches for branch

Uwe Stöhr wrote: > This cannot be fixed, because in trunk the new default theme is used. in > branch I cannot use this because the document will then become > uncompilable. No it won't. Attached is a branch version that compiles with the casual theme. All I did here is changing the theme and