Re: test-export errors

On Mon, Mar 17, 2025 at 06:32:09PM +0100, Jürgen Spitzmüller wrote: > Am Montag, dem 17.03.2025 um 17:53 +0100 schrieb Jürgen Spitzmüller: > > I reported this here: > > https://github.com/latex3/xcolor/issues/42 > > Turned out it was my fault. Fixed. Thanks, I confirm the relevant tests look good

Re: test-export errors

Am Montag, dem 17.03.2025 um 17:53 +0100 schrieb Jürgen Spitzmüller: > I reported this here: > https://github.com/latex3/xcolor/issues/42 Turned out it was my fault. Fixed. -- Jürgen signature.asc Description: This is a digitally signed message part -- lyx-devel mailing list lyx-devel@lists.l

Re: test-export errors

Am Sonntag, dem 16.03.2025 um 22:11 +0100 schrieb Scott Kostyshak: > On Sun, Mar 16, 2025 at 03:49:25PM +0100, Kornel Benko wrote: > > I see these errors (with TL25): > > export/doc/EmbeddedObjects_pdf > > export/doc/de/EmbeddedObjects_pdf > > These also fail for me on TL25. Seems to be a bug wit

Re: test-export errors

On Mon, Mar 17, 2025 at 08:26:26AM +0100, Kornel Benko wrote: > Am Sun, 16 Mar 2025 22:11:41 +0100 > schrieb Scott Kostyshak : > > > > INVERTED.DOCBOOK_export/examples/ja/Modules/LilyPond_Book_docbook5 > > > > Passes here. > > Hm, this is the tail of my logfile. Everything is OK, therefore the

Re: test-export errors

Am Sun, 16 Mar 2025 22:11:41 +0100 schrieb Scott Kostyshak : > > INVERTED.DOCBOOK_export/examples/ja/Modules/LilyPond_Book_docbook5 > > Passes here. Hm, this is the tail of my logfile. Everything is OK, therefore the inverted test does not pass. The only thing not OK is missing lyx-converter

Re: test-export errors

On Sun, Mar 16, 2025 at 03:49:25PM +0100, Kornel Benko wrote: > I see these errors (with TL25): > export/doc/EmbeddedObjects_pdf > export/doc/de/EmbeddedObjects_pdf These also fail for me on TL25. > export/examples/Articles/Springer_Nature_Journals_docbook5 Also fails here, but I don't know if I

Re: Test failure after tlmgr update (not a LyX issue)

On Mon, May 06, 2024 at 01:59:50PM GMT, Kornel Benko wrote: > Am Sun, 5 May 2024 13:12:48 +0200 > schrieb Kornel Benko : > > > > > > > > > See: https://tug.org/pipermail/tex-live/2024-May/050511.html > > > > > > > > Udi > > > > > > Thanks, Kornel and Udi. Indeed, after a new tlmgr update th

Re: Test failure after tlmgr update (not a LyX issue)

Am Sun, 5 May 2024 13:12:48 +0200 schrieb Kornel Benko : > > > > > > See: https://tug.org/pipermail/tex-live/2024-May/050511.html > > > > > > Udi > > > > Thanks, Kornel and Udi. Indeed, after a new tlmgr update these tests > > pass. Now the following tests fail for me: > > > > export/exa

Re: Test failure after tlmgr update (not a LyX issue)

Am Sat, 4 May 2024 23:18:51 -0400 schrieb Scott Kostyshak : > On Sat, May 04, 2024 at 09:57:22PM GMT, Udicoudco wrote: > > On Sat, May 4, 2024, 9:46 PM Kornel Benko wrote: > > > > > Am Fri, 3 May 2024 10:31:42 -0400 > > > schrieb Scott Kostyshak : > > > > > > > This is likely not a LyX issue

Re: Test failure after tlmgr update (not a LyX issue)

On Sat, May 04, 2024 at 09:57:22PM GMT, Udicoudco wrote: > On Sat, May 4, 2024, 9:46 PM Kornel Benko wrote: > > > Am Fri, 3 May 2024 10:31:42 -0400 > > schrieb Scott Kostyshak : > > > > > This is likely not a LyX issue so feel free to ignore. > > > > > > After a tlmgr update, the following tests

Re: Test failure after tlmgr update (not a LyX issue)

On Sat, May 4, 2024, 9:46 PM Kornel Benko wrote: > Am Fri, 3 May 2024 10:31:42 -0400 > schrieb Scott Kostyshak : > > > This is likely not a LyX issue so feel free to ignore. > > > > After a tlmgr update, the following tests now fail: > > > > export/export/latex/languages/en-ja_platex_dvi3_syste

Re: Test failure after tlmgr update (not a LyX issue)

Am Fri, 3 May 2024 10:31:42 -0400 schrieb Scott Kostyshak : > This is likely not a LyX issue so feel free to ignore. > > After a tlmgr update, the following tests now fail: > > export/export/latex/languages/en-ja_platex_dvi3_systemF (Failed) > export/export/latex/languages/en-ja_platex_pdf4_

Re: Test

I received your test, and it was signed. By the way, that's cool you can add an alias, i.e., I see: gpg: Good signature from "Kornel Benko " [full] gpg: aka "Kornel Benko " [full] I did not know you could do that. That's helpful to know. Note that I did not see any text content t

Re: Test Email

On 8/26/20 7:27 PM, Doug Martin wrote: > I just got subscribed to this list, thanks to the kind help of Riki Heck. > And I just wanted to check that indeed I can send an email to the list. And it seems to have come through. Riki -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.ly

Re: Test entering an endless loop in latex processing

On Mon, Aug 24, 2020 at 01:44:33AM +0200, Kornel Benko wrote: > Am Sun, 23 Aug 2020 14:36:52 -0400 > schrieb Scott Kostyshak : > > > On Sun, Aug 23, 2020 at 01:35:54PM +0200, Kornel Benko wrote: > > > Am Sun, 23 Aug 2020 11:53:25 +0200 > > > schrieb Kornel Benko : > > > > > > > Am Sun, 23 Aug 2

Re: Test entering an endless loop in latex processing

Am Sun, 23 Aug 2020 14:36:52 -0400 schrieb Scott Kostyshak : > On Sun, Aug 23, 2020 at 01:35:54PM +0200, Kornel Benko wrote: > > Am Sun, 23 Aug 2020 11:53:25 +0200 > > schrieb Kornel Benko : > > > > > Am Sun, 23 Aug 2020 10:09:24 +0200 > > > schrieb Jürgen Spitzmüller : > > > > > > > Am Sams

Re: Test entering an endless loop in latex processing

On Sun, Aug 23, 2020 at 01:35:54PM +0200, Kornel Benko wrote: > Am Sun, 23 Aug 2020 11:53:25 +0200 > schrieb Kornel Benko : > > > Am Sun, 23 Aug 2020 10:09:24 +0200 > > schrieb Jürgen Spitzmüller : > > > > > Am Samstag, den 22.08.2020, 14:34 +0200 schrieb Kornel Benko: > > > > OK. In the mean t

Re: Test entering an endless loop in latex processing

Am Sun, 23 Aug 2020 11:53:25 +0200 schrieb Kornel Benko : > Am Sun, 23 Aug 2020 10:09:24 +0200 > schrieb Jürgen Spitzmüller : > > > Am Samstag, den 22.08.2020, 14:34 +0200 schrieb Kornel Benko: > > > OK. In the mean time, (I don't expect a solution in the near future) > > > we should use your p

Re: Test entering an endless loop in latex processing

Am Sun, 23 Aug 2020 10:09:24 +0200 schrieb Jürgen Spitzmüller : > Am Samstag, den 22.08.2020, 14:34 +0200 schrieb Kornel Benko: > > OK. In the mean time, (I don't expect a solution in the near future) > > we should use your patch. Just my 2c. > > I went for alphabetic ordering now. > > Jürgen

Re: Test entering an endless loop in latex processing

Am Samstag, den 22.08.2020, 14:34 +0200 schrieb Kornel Benko: > OK. In the mean time, (I don't expect a solution in the near future) > we should use your patch. Just my 2c. I went for alphabetic ordering now. Jürgen signature.asc Description: This is a digitally signed message part -- lyx-deve

Re: Test entering an endless loop in latex processing

Am Sat, 22 Aug 2020 14:25:53 +0200 schrieb Jürgen Spitzmüller : > Am Samstag, den 22.08.2020, 14:04 +0200 schrieb Kornel Benko: > > The other thing is the unspecified sequence of documentclass options. > > We have to expect different outcome depending on the phase of moon. > > The order really

Re: Test entering an endless loop in latex processing

Am Samstag, den 22.08.2020, 14:04 +0200 schrieb Kornel Benko: > The other thing is the unspecified sequence of documentclass options. > We have to expect different outcome depending on the phase of moon. The order really should not matter. And as you demonstrated, the sequence also differs for pre

Re: Test entering an endless loop in latex processing

Am Sat, 22 Aug 2020 13:39:28 +0200 schrieb Jürgen Spitzmüller : > Am Samstag, den 22.08.2020, 11:39 +0200 schrieb Kornel Benko: > > Looks good. The endless loop is gone :) > > Thanks. I first try to get it fixed upstream. If this doesn't work, we > can still commit this ugly workaround. > > Jü

Re: Test entering an endless loop in latex processing

Am Samstag, den 22.08.2020, 11:39 +0200 schrieb Kornel Benko: > Looks good. The endless loop is gone :) Thanks. I first try to get it fixed upstream. If this doesn't work, we can still commit this ugly workaround. Jürgen signature.asc Description: This is a digitally signed message part -- lyx

Re: Test entering an endless loop in latex processing

Am Sat, 22 Aug 2020 11:18:58 +0200 schrieb Jürgen Spitzmüller : > Am Samstag, den 22.08.2020, 10:28 +0200 schrieb Jürgen Spitzmüller: > > What we can do is to assure that hebrew is always output after arabic > > and farsi. But this of course only works if Arabic or Farsi are not > > the main langu

Re: Test entering an endless loop in latex processing

Am Samstag, den 22.08.2020, 10:28 +0200 schrieb Jürgen Spitzmüller: > What we can do is to assure that hebrew is always output after arabic > and farsi. But this of course only works if Arabic or Farsi are not > the main language. This would be something like the attached. Kornel, Scott, does this

Re: Test entering an endless loop in latex processing

Am Samstag, den 22.08.2020, 10:28 +0200 schrieb Jürgen Spitzmüller: > My guess is that arabicore.sty (use by Farsi and Arabic) and > lhbabel.def (used by Hebrew) redefine \everypar in incompatible ways. > > What we can do is to assure that hebrew is always output after arabic > and farsi. But this

Re: Test entering an endless loop in latex processing

Am Freitag, den 21.08.2020, 19:06 +0200 schrieb Kornel Benko: > This version does hang. Switch the commented documentclass, and now > the compilation does not hang. It boils down to the order of hebrew and farsi (or arabic): \documentclass[ hebrew,% breaks farsi,% or: arabic

Re: Test entering an endless loop in latex processing

Am Freitag, den 21.08.2020, 13:33 -0400 schrieb Scott Kostyshak: > Thanks to you two for looking into this annoying problem. I don't > have > much time to contribute or test. > > The following ML thread is relevant. I'm not sure it contains any > additional information but I put it nonetheless at

Re: Test entering an endless loop in latex processing

On Fri, Aug 21, 2020 at 07:51:43PM +0200, Kornel Benko wrote: > Am Fri, 21 Aug 2020 13:33:58 -0400 > schrieb Scott Kostyshak : > > > > > Thanks. Could you send also the other file, for comparison? > > > > > > It is too edited (the documentclass line) > > > > Thanks to you two for looking int

Re: Test entering an endless loop in latex processing

Am Fri, 21 Aug 2020 13:33:58 -0400 schrieb Scott Kostyshak : > > > Thanks. Could you send also the other file, for comparison? > > > > It is too edited (the documentclass line) > > Thanks to you two for looking into this annoying problem. I don't have > much time to contribute or test. > >

Re: Test entering an endless loop in latex processing

On Fri, Aug 21, 2020 at 07:21:13PM +0200, Kornel Benko wrote: > Am Fri, 21 Aug 2020 19:13:32 +0200 > schrieb Jürgen Spitzmüller : > > > Am Freitag, den 21.08.2020, 19:06 +0200 schrieb Kornel Benko: > > > > Are these the only differences in the tex file? > > > > > > No, but others are only the s

Re: Test entering an endless loop in latex processing

Am Fri, 21 Aug 2020 19:13:32 +0200 schrieb Jürgen Spitzmüller : > Am Freitag, den 21.08.2020, 19:06 +0200 schrieb Kornel Benko: > > > Are these the only differences in the tex file? > > > > No, but others are only the sequence of defining some latex commands. > > But this should also not dif

Re: Test entering an endless loop in latex processing

Am Freitag, den 21.08.2020, 19:06 +0200 schrieb Kornel Benko: > > Are these the only differences in the tex file? > > No, but others are only the sequence of defining some latex commands. But this should also not differ. > > > And does the first tex file also hang if you run pdflatex directly?

Re: Test entering an endless loop in latex processing

Am Fri, 21 Aug 2020 18:50:37 +0200 schrieb Jürgen Spitzmüller : > Am Freitag, den 21.08.2020, 18:18 +0200 schrieb Kornel Benko: > > $ egrep cache Testing/.lyx/preferences > > \converter_cache_maxage 15552000 > > \use_converter_cache false > > > > But I suspect now differences in

Re: Test entering an endless loop in latex processing

Am Freitag, den 21.08.2020, 18:18 +0200 schrieb Kornel Benko: > $ egrep cache Testing/.lyx/preferences > \converter_cache_maxage 15552000 > \use_converter_cache false > > But I suspect now differences in the used tex-files. > The main difference (as I see it) is the definition of

Re: Test entering an endless loop in latex processing

Am Fri, 21 Aug 2020 17:48:47 +0200 schrieb Jürgen Spitzmüller : > Kornel Benko schrieb am Fr., 21. Aug. 2020, 17:13: > > > Sure? > > > > Sure. The execution time of pdflatex is constantly increasing. > > I meant: sure cache is disabled? > > > Mark, that this is only a single export (no oth

Re: Test entering an endless loop in latex processing

Kornel Benko schrieb am Fr., 21. Aug. 2020, 17:13: > > Sure? > > Sure. The execution time of pdflatex is constantly increasing. I meant: sure cache is disabled? > Mark, that this is only a single export (no other lyx instance is > involved) Still there might be different threats trying to acce

Re: Test entering an endless loop in latex processing

Am Fri, 21 Aug 2020 17:00:34 +0200 schrieb Jürgen Spitzmüller : > Am Fr., 21. Aug. 2020 um 16:41 Uhr schrieb Kornel Benko : > > > There is a problem. Endless loop in pdflatex if disabled cache > > > > Sure? Sure. The execution time of pdflatex is constantly increasing. What I can do is post th

Re: Test entering an endless loop in latex processing

Am Fr., 21. Aug. 2020 um 16:41 Uhr schrieb Kornel Benko : > There is a problem. Endless loop in pdflatex if disabled cache > Sure? > > Also it strongly depends on the actual environment of LYX_DEBUG_LATEX (1 > or 0) > > The test runs lyx with '-dbg latex' if LYX_DEBUG_LATEX=1 (no hang) > else i

Re: Test entering an endless loop in latex processing

Am Fri, 21 Aug 2020 15:56:01 +0200 schrieb Jürgen Spitzmüller : > Am Fr., 21. Aug. 2020 um 14:19 Uhr schrieb Kornel Benko : > > > Correction. If I disable the conversion cache, I can export again. > > > > Also if you manually delete the contents of the cache? > > Do you get any helpful clue if

Re: Test entering an endless loop in latex processing

Am Fr., 21. Aug. 2020 um 14:19 Uhr schrieb Kornel Benko : > Correction. If I disable the conversion cache, I can export again. > Also if you manually delete the contents of the cache? Do you get any helpful clue if you run the hanging lyx run with "-dbg any"? Jürgen > (The commands above were

Re: Test entering an endless loop in latex processing

Am Fri, 21 Aug 2020 13:58:46 +0200 schrieb Kornel Benko : > Am Fri, 21 Aug 2020 13:25:31 +0200 > schrieb Jürgen Spitzmüller : > > > Am Fr., 21. Aug. 2020 um 12:21 Uhr schrieb Kornel Benko : > > > > > > Does it help if you "Clear all session information" in Prefs > Look & > > > > Feel > Documen

Re: Test entering an endless loop in latex processing

Am Fri, 21 Aug 2020 13:25:31 +0200 schrieb Jürgen Spitzmüller : > Am Fr., 21. Aug. 2020 um 12:21 Uhr schrieb Kornel Benko : > > > > Does it help if you "Clear all session information" in Prefs > Look & > > > Feel > Document Handling? > > > > ATM, it helped, yes. > > > > Can you reproduce the han

Re: Test entering an endless loop in latex processing

Am Fr., 21. Aug. 2020 um 12:21 Uhr schrieb Kornel Benko : > > Does it help if you "Clear all session information" in Prefs > Look & > > Feel > Document Handling? > > ATM, it helped, yes. > Can you reproduce the hanging when trying to compile the file manually from the GUI? If so, does this warni

Re: Test entering an endless loop in latex processing

Am Fri, 21 Aug 2020 11:34:25 +0200 schrieb Jürgen Spitzmüller : > Am Samstag, den 15.08.2020, 20:04 +0200 schrieb Kornel Benko: > > > Am Samstag, den 15.08.2020, 16:02 +0200 schrieb Kornel Benko: > > > > This one is really bad, maybe not even lyx's fault. > > > > > > > > TL2020: > > > > export/

Re: Test entering an endless loop in latex processing

Am Samstag, den 15.08.2020, 20:04 +0200 schrieb Kornel Benko: > > Am Samstag, den 15.08.2020, 16:02 +0200 schrieb Kornel Benko: > > > This one is really bad, maybe not even lyx's fault. > > > > > > TL2020: > > > export/export/latex/languages/supported-languages_babel_auto- > > > legacy_pdf2 > >

Re: Test entering an endless loop in latex processing

Am Sat, 15 Aug 2020 17:58:18 +0200 schrieb Jürgen Spitzmüller : > Am Samstag, den 15.08.2020, 16:02 +0200 schrieb Kornel Benko: > > This one is really bad, maybe not even lyx's fault. > > > > TL2020: > > export/export/latex/languages/supported-languages_babel_auto- > > legacy_pdf2 > > This com

Re: Test entering an endless loop in latex processing

Am Samstag, den 15.08.2020, 16:02 +0200 schrieb Kornel Benko: > This one is really bad, maybe not even lyx's fault. > > TL2020: > export/export/latex/languages/supported-languages_babel_auto- > legacy_pdf2 This compiles for me (at 3c5c41ddc2d4a4). Jürgen signature.asc Description: This is a d

Re: Test

On 3/08/2019 10:46 PM, Jean-Marc Lasgouttes wrote: Le 3 août 2019 05:19:51 GMT+02:00, Richard Kimberly Heck a écrit : Just making sure the lists are still functional Riki Looks like we are all in vacation ;) JMarc I deduce that there are no southern hemisphere developers.

Re: Test

Le 3 août 2019 05:19:51 GMT+02:00, Richard Kimberly Heck a écrit : >Just making sure the lists are still functional > >Riki Looks like we are all in vacation ;) JMarc

Re: Test

Le 17 février 2019 19:35:09 Richard Kimberly Heck a écrit : Are the lists alive? Sure. -- Jean-Pierre

Re: Test

Am Sonntag, 17. Februar 2019 13:34:33 CET schrieb Richard Kimberly Heck : > Are the lists alive? > > Sure. But boring. Kornel signature.asc Description: This is a digitally signed message part.

Re: Test ru-accent-ascii_pdf2 now fails

On 2019-01-13, Scott Kostyshak wrote: > [-- Type: text/plain, Encoding: quoted-printable --] > On Sun, Jan 13, 2019 at 11:27:29AM +0100, Jürgen Spitzmüller wrote: >> Am Samstag, den 12.01.2019, 19:14 -0500 schrieb Scott Kostyshak: >> > A recent commit caused the following test to fail: >> > >> >

Re: Test ru-accent-ascii_pdf2 now fails

On Sun, Jan 13, 2019 at 11:27:29AM +0100, Jürgen Spitzmüller wrote: > Am Samstag, den 12.01.2019, 19:14 -0500 schrieb Scott Kostyshak: > > A recent commit caused the following test to fail: > > > > export/latex/ru-accent-ascii_pdf2 > > Fixed. Thanks, the test passes now. > This file won't com

Re: Test ru-accent-ascii_pdf2 now fails

Am Samstag, den 12.01.2019, 19:14 -0500 schrieb Scott Kostyshak: > A recent commit caused the following test to fail: > > export/latex/ru-accent-ascii_pdf2 Fixed. This file won't compile with XeTeX/LuaTeX and TeX fonts. I don't think this can be fixed (but this setting is also not something any

Re: Test

Am Samstag, 12. Mai 2018 11:19:18 CEST schrieb Kornel Benko : > Am Samstag, 12. Mai 2018 10:05:03 CEST schrieb José Abílio Matos > : > > On Saturday, 12 May 2018 09.50.56 WEST Kornel Benko > > wrote: > > > I seem to be unable to send mails containing a signature. > > > > > > Kornel > > > > We

Re: Test

Am Samstag, 12. Mai 2018 10:05:03 CEST schrieb José Abílio Matos : > On Saturday, 12 May 2018 09.50.56 WEST Kornel Benko > wrote: > > I seem to be unable to send mails containing a signature. > > > > Kornel > > We did _not_ receive this email. ;-) > OK then. Probably the error may be sen

Re: Test

On Saturday, 12 May 2018 09.50.56 WEST Kornel Benko wrote: > I seem to be unable to send mails containing a signature. > > Kornel We did _not_ receive this email. ;-) -- José Abílio

Re: Test wish for a new lfunc

On Mon, Jan 15, 2018 at 07:47:50PM +, Kornel Benko wrote: > Hm, I don't think it depends on TL. Using system fonts is slow here. > In fact, installing "fonts-farsiweb" and "ttf-freefarsi" improved the > compilation dramatically. > > 1/1 Test #4880: INVERTED.TODO_export/examples/fa/splash_pdf

Re: Test wish for a new lfunc

Am Montag, 15. Januar 2018 um 14:01:25, schrieb Scott Kostyshak > On Mon, Jan 15, 2018 at 06:42:31PM +, Kornel Benko wrote: > > Am Montag, 15. Januar 2018 um 13:03:26, schrieb Scott Kostyshak > > > > > On Mon, Jan 15, 2018 at 01:21:57PM +, Kornel Benko wrote: > > > > > > > There are te

Re: Test wish for a new lfunc

On Mon, Jan 15, 2018 at 06:42:31PM +, Kornel Benko wrote: > Am Montag, 15. Januar 2018 um 13:03:26, schrieb Scott Kostyshak > > > On Mon, Jan 15, 2018 at 01:21:57PM +, Kornel Benko wrote: > > > > > There are tests running about 10 minutes (like export farsi files). > > > > Does fa/splas

Re: Test wish for a new lfunc

Am Montag, 15. Januar 2018 um 13:03:26, schrieb Scott Kostyshak > On Mon, Jan 15, 2018 at 01:21:57PM +, Kornel Benko wrote: > > > There are tests running about 10 minutes (like export farsi files). > > Does fa/splash.lyx take about 10 minutes for you? Actually, no PDF > export for Farsi is

Re: Test wish for a new lfunc

On Mon, Jan 15, 2018 at 01:34:45PM +, Pavel Sanda wrote: > Jean-Marc Lasgouttes wrote: > > BTW, what is the difference between buffer-export and buffer-export-as ? > > I believe the second opens the dialog for you. Yes, and also buffer-export takes a second (optional) argument, which is the

Re: Test wish for a new lfunc

On Mon, Jan 15, 2018 at 01:21:57PM +, Kornel Benko wrote: > There are tests running about 10 minutes (like export farsi files). Does fa/splash.lyx take about 10 minutes for you? Actually, no PDF export for Farsi is uninverted for me. Does the export take 10 minutes to fail for you? I get the

Re: Test wish for a new lfunc

Am Montag, 15. Januar 2018 um 15:04:55, schrieb Jean-Marc Lasgouttes > Le 15/01/2018 à 14:21, Kornel Benko a écrit : > > This is not desirable due to parallel run of tests which use the same lyxrc. > > There are tests running about 10 minutes (like export farsi files). > > And possible waiting fo

Re: Test wish for a new lfunc

Le 15/01/2018 à 14:21, Kornel Benko a écrit : This is not desirable due to parallel run of tests which use the same lyxrc. There are tests running about 10 minutes (like export farsi files). And possible waiting for 10 minutes for a test which should complete in 10 seconds is definitely not desi

Re: Test wish for a new lfunc

Jean-Marc Lasgouttes wrote: > Ah, yes there is this async thing. I thought that we wanted to disable it > when running in batch mode or in command-sequence, right? I do not know batch-mode well, but I do not think you can use it for useful command sequences, you need gui for that (e.g. even buffe

Re: Test wish for a new lfunc

Le 15/01/2018 à 14:10, Pavel Sanda a écrit : Jean-Marc Lasgouttes wrote: What about making os::timeout_min() be configurable by LyXRC (maybe in seconds instead of minutes if you prefer)? Then you could set the rc variable to some value before doing the export. But you still need some wait func

Re: Test wish for a new lfunc

Am Montag, 15. Januar 2018 um 14:10:10, schrieb Pavel Sanda > Jean-Marc Lasgouttes wrote: > > What about making os::timeout_min() be configurable by LyXRC (maybe in > > seconds instead of minutes if you prefer)? Then you could set the rc > > variable to some value before doing the export. This

Re: Test wish for a new lfunc

Jean-Marc Lasgouttes wrote: > What about making os::timeout_min() be configurable by LyXRC (maybe in > seconds instead of minutes if you prefer)? Then you could set the rc > variable to some value before doing the export. But you still need some wait function, which hangs until export(cancel) is

Re: Test wish for a new lfunc

Le 15/01/2018 à 13:02, Kornel Benko a écrit : Am Montag, 15. Januar 2018 um 12:55:00, schrieb Pavel Sanda Kornel Benko wrote: Could we please get a new function, say export-wait maxtime to wait for an export to finish for at maximal max-time seconds? If time exceeds max-time, then use

Re: Test wish for a new lfunc

Am Montag, 15. Januar 2018 um 12:55:00, schrieb Pavel Sanda > Kornel Benko wrote: > > Could we please get a new function, say > > export-wait maxtime > > to wait for an export to finish for at maximal max-time seconds? > > If time exceeds max-time, then use 'export-cancel'. > > if no backgroun

Re: Test wish for a new lfunc

Kornel Benko wrote: > Could we please get a new function, say > export-wait maxtime > to wait for an export to finish for at maximal max-time seconds? > If time exceeds max-time, then use 'export-cancel'. > if no background export in work, then it should be noop. I'd say export-wait [maxtime

Re: Test

Am Montag, 13. Februar 2017 um 11:20:48, schrieb Richard Heck > This is a test. Are we alive again? Looks good. Kornel signature.asc Description: This is a digitally signed message part.

Re: Test email #5

FYI, this was an e-mail from the CI server (which runs the software called "Jenkins") which I sent to verify that the CI server is now able to mail the lyx-devel-list. /Christian PS. I'll now configure one of the CI jobs to mail the devel-list when the jobs fails, and I'll also make the job fail t

Re: Test results for 2.2.0dev on Mac

Stephan Witt wrote: > After applying the patches I get: > > $ (cd lyx-build/cmake/2.2.0dev;ctest -C debug -R tex2lyx) > Test project /Users/stephan/git/lyx-build/cmake/2.2.0dev > > … > > 86% tests passed, 4 tests failed out of 28 > > Label Time Summary: > cmplyx = 21.45 sec (14 tests) >

Re: Test results for 2.2.0dev on Mac

Am 29.01.2016 um 22:15 schrieb Georg Baum : > > Stephan Witt wrote: > >> Am 24.01.2016 um 19:08 schrieb Georg Baum >> : >>> >>> This is the idea, yes, but before implementing it I'd like to know >>> whether it works in principle. This would require a two step approach for >>> the case that no co

Re: Test results for 2.2.0dev on Mac

Stephan Witt wrote: > Am 24.01.2016 um 19:08 schrieb Georg Baum > : >> >> This is the idea, yes, but before implementing it I'd like to know >> whether it works in principle. This would require a two step approach for >> the case that no command line option is given: Parse in latin1 encoding >> u

Re: Test results for 2.2.0dev on Mac

Am 24.01.2016 um 19:08 schrieb Georg Baum : > > Stephan Witt wrote: > >> Am 24.01.2016 um 18:17 schrieb Georg Baum >> : >>> >>> Stephan, does the algo2e.tex test succeed if you apply the attached patch >>> on a clean tree? >> >> No, it doesn’t work. With the patch I get: > > It turned out that

Re: Test results for 2.2.0dev on Mac

On Sun, Jan 24, 2016 at 06:17:18PM +0100, Georg Baum wrote: > Scott Kostyshak wrote: > > > Do I understand correctly that this issue is no longer a beta blocker or > > is there still something that needs to be done here before beta? > > The original reason why I viewed it as beta blocker (general

Re: Test results for 2.2.0dev on Mac

Stephan Witt wrote: > Am 24.01.2016 um 18:17 schrieb Georg Baum > : >> >> Stephan, does the algo2e.tex test succeed if you apply the attached patch >> on a clean tree? > > No, it doesn’t work. With the patch I get: It turned out that we used two different names for the latin1 encoding: "ISO885

Re: Test results for 2.2.0dev on Mac

Am 24.01.2016 um 18:17 schrieb Georg Baum : > > Scott Kostyshak wrote: > >> Do I understand correctly that this issue is no longer a beta blocker or >> is there still something that needs to be done here before beta? > > The original reason why I viewed it as beta blocker (general user or sytem

Re: Test results for 2.2.0dev on Mac

Scott Kostyshak wrote: > Do I understand correctly that this issue is no longer a beta blocker or > is there still something that needs to be done here before beta? The original reason why I viewed it as beta blocker (general user or sytem directory problems) turned out to be wrong. I would not

Re: Test results for 2.2.0dev on Mac

On Sun, Jan 24, 2016 at 03:36:09PM +0100, Georg Baum wrote: > OK, but I don't think it is too important to know whether the old compiler > did handle that. There is a FIXME near the imbue call anyway, since we do > not know whether it is standard conforming what we do there. > > I'll have a loo

Re: Test results for 2.2.0dev on Mac

Stephan Witt wrote: > For latin1 documents (e.g. algo2e.tex) it works better. The test now > passed. > > For CJK.lex it’s obviously a problem: > $ /Users/stephan/git/lyx-build/cmake/2.2.0dev/bin/Debug/tex2lyx -f > -roundtrip /Users/stephan/git/lyx/src/tex2lyx/test/CJK.tex > /Users/stephan/git/lyx

Re: Test results for 2.2.0dev on Mac

Am 24.01.2016 um 15:07 schrieb Georg Baum : > > Stephan Witt wrote: > >> Yes, we shouldn’t change that on the fly. If we change it we have to >> provide a migration path to copy the current contents to the new location. >> Not very difficult but a change in configure.py would be required. >> >>

Re: Test results for 2.2.0dev on Mac

Am 24.01.2016 um 14:50 schrieb Georg Baum : > > Stephan Witt wrote: > >> Am 24.01.2016 um 13:00 schrieb Stephan Witt : >> I’ve tried to follow the tokenizing and parsing program flow. >> >> While processing the „latin1“ option of „inputenc“ the encoding of >> the idocstream is changed. (Line 395

Re: Test results for 2.2.0dev on Mac

Stephan Witt wrote: > Yes, we shouldn’t change that on the fly. If we change it we have to > provide a migration path to copy the current contents to the new location. > Not very difficult but a change in configure.py would be required. > > Since we don’t want to use different settings for Lyx, t

Re: Test results for 2.2.0dev on Mac

Stephan Witt wrote: > Am 24.01.2016 um 13:00 schrieb Stephan Witt : > I’ve tried to follow the tokenizing and parsing program flow. > > While processing the „latin1“ option of „inputenc“ the encoding of > the idocstream is changed. (Line 395 of support/docstream.cpp is called) > > Perhaps this i

Re: Test results for 2.2.0dev on Mac

Am 24.01.2016 um 13:00 schrieb Stephan Witt : > > Am 24.01.2016 um 12:12 schrieb Georg Baum : >> >> Stephan Witt wrote: >> >>> You are asking for running tex2lyx in the debugger? Yes, I’m able to do >>> so. What should I try exactly? >>> >>> I started tex2lyx in debugger with these options: >>>

Re: Test results for 2.2.0dev on Mac

Am 24.01.2016 um 12:12 schrieb Georg Baum : > > Stephan Witt wrote: > >> You are asking for running tex2lyx in the debugger? Yes, I’m able to do >> so. What should I try exactly? >> >> I started tex2lyx in debugger with these options: >> -f >> -roundtrip >> /Users/stephan/git/lyx/src/tex2lyx/tes

Re: Test results for 2.2.0dev on Mac

Am 24.01.2016 um 12:02 schrieb Georg Baum : > > Stephan Witt wrote: > >> ATM, the directory LyX is using is "$HOME/Library/Application >> Support/PACKAGE“ >> >> PACKAGE is LyX-2.2 on Mac when version suffix „-2.2“ is used. > > Looks like QtApplication does something different here than > QtCor

Re: Test results for 2.2.0dev on Mac

Stephan Witt wrote: > You are asking for running tex2lyx in the debugger? Yes, I’m able to do > so. What should I try exactly? > > I started tex2lyx in debugger with these options: > -f > -roundtrip > /Users/stephan/git/lyx/src/tex2lyx/test/algo2e.tex > /Users/stephan/git/lyx-build/algo2e.lyx >

Re: Test results for 2.2.0dev on Mac

Stephan Witt wrote: > ATM, the directory LyX is using is "$HOME/Library/Application > Support/PACKAGE“ > > PACKAGE is LyX-2.2 on Mac when version suffix „-2.2“ is used. Looks like QtApplication does something different here than QtCoreApplication. >> Stephan, does it work? Note that this is not

Re: Test results for 2.2.0dev on Mac

Am 22.01.2016 um 22:32 schrieb Georg Baum : > > Stephan Witt wrote: > >> No. It’s not wrong. You’re right with the use of the _own_ userdir >> for tests. But the real life matters too. It’s the wrong userdir >> for standard orpeation. And this is Georg message, IMO. > > Yes. Also, depending on t

Re: Test results for 2.2.0dev on Mac

> Am 22.01.2016 um 21:54 schrieb Georg Baum : > > Stephan Witt wrote: > >> $ lyx-build/cmake/2.2.0dev/bin/Debug/tex2lyx >> tex2lyx: Not enough arguments. >> Usage: tex2lyx [options] infile.tex [outfile.lyx] >> … >> -sysdir SYSDIR Set system directory to SYSDIR. >> Default: /Users/stephan/git

Re: Test results for 2.2.0dev on Mac

Stephan Witt wrote: > No. It’s not wrong. You’re right with the use of the _own_ userdir > for tests. But the real life matters too. It’s the wrong userdir > for standard orpeation. And this is Georg message, IMO. Yes. Also, depending on the reaason for the wrong default user dir, also the speci

Re: Test results for 2.2.0dev on Mac

Stephan Witt wrote: > Am 22.01.2016 um 21:01 schrieb Georg Baum > : >> >> Stephan Witt wrote: >> >>> There is some change required because tex2lyx has the same problem >>> itself. I’ve changed this for the lyx binary here: >>> >>> http://www.lyx.org/trac/changeset/6e9bd23/lyxgit >>> >>> Attach

Re: Test results for 2.2.0dev on Mac

Stephan Witt wrote: > $ lyx-build/cmake/2.2.0dev/bin/Debug/tex2lyx > tex2lyx: Not enough arguments. > Usage: tex2lyx [options] infile.tex [outfile.lyx] > … > -sysdir SYSDIR Set system directory to SYSDIR. > Default: /Users/stephan/git/lyx/lib/ > -userdir USERDIR Set user directory to USERDIR

  1   2   3   >