Re: Compilation failure un c++11 mode with gcc 4.6

Am Donnerstag, 28. Mai 2015 um 23:23:07, schrieb pdv pdvissch...@edpnet.be On 19/05/15 11:25, Jean-Marc Lasgouttes wrote: Hi Georg, It is not possible currently to compile with gcc 4.6 in C++11 mode because lyxalgo.h declares its own next() method. This is because the code depends on

Re: configure.py questions

On 2015-05-29, Uwe Stöhr wrote: Hello LyXers, since I was forced to send many texts I wrote with LyX in the format of MS word, I spend a lot of time to get this to work. The solution is surprisingly simple: - creating a HTML file via eLyXer* and then importing it to Word or LibreOffice-

Re: Failing tex2lyx tests

Am Freitag, 29. Mai 2015 um 05:59:48, schrieb Stephan Witt st.w...@gmx.net Am 29.05.2015 um 00:47 schrieb Uwe Stöhr uwesto...@web.de: Am 26.05.2015 um 04:00 schrieb Scott Kostyshak: I did not update all references. Work was in progress. Now everything should work. My personal

Re: [LyX/master] delete test file verbatim.tex

Am Freitag, 29. Mai 2015 um 05:55:50, schrieb Guenter Milde mi...@users.sf.net On 2015-05-28, Uwe Stöhr wrote: Am 24.05.2015 um 17:55 schrieb Kornel Benko: delete test file verbatim.tex because we already check for verbatim in test-structure.tex ... I'd prefer to have

Re: configure.py questions

On 05/28/2015 08:09 PM, Uwe Stöhr wrote: Hello LyXers, since I was forced to send many texts I wrote with LyX in the format of MS word, I spend a lot of time to get this to work. The solution is surprisingly simple: - creating a HTML file via eLyXer* and then importing it to Word or

Re: LyX 2.1.4

Not on my side. JMarc Le 29 mai 2015 17:12:51 CEST, Richard Heck rgh...@lyx.org a écrit : I'd like to start the 2.1.4 release process by freezing strings, etc. Any fixes that need to go in before I do that? Richard

Re: LyX 2.1.4

Except for #8658, of course. JMarc Le 29 mai 2015 17:51:04 CEST, Jean-Marc Lasgouttes lasgout...@lyx.org a écrit : Not on my side. JMarc Le 29 mai 2015 17:12:51 CEST, Richard Heck rgh...@lyx.org a écrit : I'd like to start the 2.1.4 release process by freezing strings, etc. Any fixes that

Re: configure.py questions

On 05/28/2015 08:09 PM, Uwe Stöhr wrote: @Richard: I would like to use our LyXHTML output but there are problems with the images. In LyXHTML the images sizes (\columnwidth etc.) are not respected and therefore it looks horrible in MS Word and Libreoffice. eLyXer is in this respect better as

LyX 2.1.4

I'd like to start the 2.1.4 release process by freezing strings, etc. Any fixes that need to go in before I do that? Richard

Re: Compilation failure un c++11 mode with gcc 4.6

Le 28/05/2015 23:23, pdv a écrit : Starting with commit b596330 lyx fails to compile with cmake/xcode. This seems to be due to boost::next having been replaced by next and this generates ambiguous call to 'next' semantic issues, one of the 2 possibilities being the next in lyxalgo.h mentioned in

Re: Compilation failure un c++11 mode with gcc 4.6

Am Freitag, 29. Mai 2015 um 19:52:03, schrieb Jean-Marc Lasgouttes lasgout...@lyx.org Le 28/05/2015 23:23, pdv a écrit : Starting with commit b596330 lyx fails to compile with cmake/xcode. This seems to be due to boost::next having been replaced by next and this generates ambiguous call to

Re: LyX 2.1.4

On 05/29/2015 11:53 AM, Jean-Marc Lasgouttes wrote: Except for #8658, of course. Which is now done rh JMarc Le 29 mai 2015 17:51:04 CEST, Jean-Marc Lasgouttes lasgout...@lyx.org a écrit : Not on my side. JMarc Le 29 mai 2015 17:12:51 CEST, Richard Heck

Re: Failing tex2lyx tests

On 05/29/2015 07:17 PM, Scott Kostyshak wrote: On Thu, May 28, 2015 at 6:47 PM, Uwe Stöhr uwesto...@web.de wrote: Am 26.05.2015 um 04:00 schrieb Scott Kostyshak: Nevertheless my aim was to split the commits into small pieces that can easily be reverted if necessary. I agree that this is indeed

Re: Failing tex2lyx tests

Am 30.05.2015 um 01:17 schrieb Scott Kostyshak: I agree that this is indeed a good goal. But I find that you often have follow-up commits. Yes, that is because of the git mess. I think that I am not too stupid but git is nothing for me. Now after years it is still a mystery why e.g. often

Re: Failing tex2lyx tests

On Thu, May 28, 2015 at 6:47 PM, Uwe Stöhr uwesto...@web.de wrote: Am 26.05.2015 um 04:00 schrieb Scott Kostyshak: Nevertheless my aim was to split the commits into small pieces that can easily be reverted if necessary. I agree that this is indeed a good goal. But I find that you often have

Re: about the tex2lyx tests and proposal for a better method

Am 29.05.2015 um 23:18 schrieb Georg Baum: I did not suggest that it was impolite. The proposal to stop comparing current test results against known good references, and testing the success of LaTeX compilation instead is not in line with the accepted state of the art in software testing: I

Re: LyX 2.1.4

Am 29.05.2015 um 17:12 schrieb Richard Heck: I'd like to start the 2.1.4 release process by freezing strings, etc. Any fixes that need to go in before I do that? These: - http://www.lyx.org/trac/ticket/6211 - http://www.lyx.org/trac/ticket/7850 - http://www.lyx.org/trac/ticket/9371 regards

Re: Failing tex2lyx tests

On 05/29/2015 08:29 PM, Uwe Stöhr wrote: Am 30.05.2015 um 01:17 schrieb Scott Kostyshak: I agree that this is indeed a good goal. But I find that you often have follow-up commits. Yes, that is because of the git mess. I think that I am not too stupid but git is nothing for me. Now after

Re: Failing tex2lyx tests

Am 29.05.2015 um 05:59 schrieb Stephan Witt: I can recommend the tool SourceTree from Atlassian. It's available on Windows and Mac. (Yes, no Linux version.) Thanks. I just downloaded it and will give it a try. regards Uwe

Re: [LyX/master] delete test file verbatim.tex

Am 29.05.2015 um 07:55 schrieb Guenter Milde: What is the benefit of this file? This file oly checks one style and we already check for this style in another test file? However, if the other test file tests not only for this style but for different features, it is easier to find out the

Re: [LyX features/master] Fix test for urwclassico font (bug #9576)

Richard Heck wrote: Oh, sorry, I see. This was updating features/master. and it was me, not Jürgen. The commit-hook can sometimes be quite confusing ;-( Georg

Re: about the tex2lyx tests and proposal for a better method

On 2015-05-28, Uwe Stöhr wrote: Am 27.05.2015 um 16:53 schrieb Georg Baum: - when I import our test file test-modules.tex I get a LyX file that is uncompilable: LaTeX Error: Environment lem undefined. LaTeX Error: \begin{document} ended by \end{lem}. But the test result tells me that

Re: Compilation failure un c++11 mode with gcc 4.6

Am Freitag, 29. Mai 2015 um 21:59:16, schrieb pdv pdvissch...@edpnet.be On 29/05/15 20:10, Kornel Benko wrote: Am Freitag, 29. Mai 2015 um 19:52:03, schrieb Jean-Marc Lasgouttes lasgout...@lyx.org Le 28/05/2015 23:23, pdv a écrit : Starting with commit b596330 lyx fails to compile with

Re: about the tex2lyx tests and proposal for a better method

Uwe Stöhr wrote: Am 27.05.2015 um 16:53 schrieb Georg Baum: It is_not_ a requirement that test cases always contain sensible data. In many cases, it is more effective to design test cases with contents which would never occur in practice, for example because it is shorter. Hi Georg,

Re: about the tex2lyx tests and proposal for a better method

Guenter Milde wrote: However, whenever a reference changes (to adapt to a new file version or other changes) or a new test file + reference is added, one must also check if the new reference is really a *good* one. Yes, this is the key point. In the case of LyX, this includes checking

Re: configure.py questions

On 2015-05-29, Uwe Stöhr wrote: > Hello LyXers, > since I was forced to send many texts I wrote with LyX in the format of > MS word, I spend a lot of time to get this to work. The solution is > surprisingly simple: > - creating a HTML file via eLyXer* and then importing it to Word or >

Re: Compilation failure un c++11 mode with gcc 4.6

Am Donnerstag, 28. Mai 2015 um 23:23:07, schrieb pdv > On 19/05/15 11:25, Jean-Marc Lasgouttes wrote: > > Hi Georg, > > > > It is not possible currently to compile with gcc 4.6 in C++11 mode > > because lyxalgo.h declares its own next() method. This is because the > > code

Re: [LyX/master] delete test file verbatim.tex

Am Freitag, 29. Mai 2015 um 05:55:50, schrieb Guenter Milde > On 2015-05-28, Uwe Stöhr wrote: > > Am 24.05.2015 um 17:55 schrieb Kornel Benko: > > >>> delete test file verbatim.tex > > >>> because we already check for verbatim in test-structure.tex > > ... > > >>

Re: Failing tex2lyx tests

Am Freitag, 29. Mai 2015 um 05:59:48, schrieb Stephan Witt > Am 29.05.2015 um 00:47 schrieb Uwe Stöhr : > > > Am 26.05.2015 um 04:00 schrieb Scott Kostyshak: > > > >>> I did not update all references. Work was in progress. Now everything > >>> should > >>>

LyX 2.1.4

I'd like to start the 2.1.4 release process by freezing strings, etc. Any fixes that need to go in before I do that? Richard

Re: configure.py questions

On 05/28/2015 08:09 PM, Uwe Stöhr wrote: @Richard: I would like to use our LyXHTML output but there are problems with the images. In LyXHTML the images sizes (\columnwidth etc.) are not respected and therefore it looks horrible in MS Word and Libreoffice. eLyXer is in this respect better as

Re: configure.py questions

On 05/28/2015 08:09 PM, Uwe Stöhr wrote: Hello LyXers, since I was forced to send many texts I wrote with LyX in the format of MS word, I spend a lot of time to get this to work. The solution is surprisingly simple: - creating a HTML file via eLyXer* and then importing it to Word or

Re: LyX 2.1.4

Not on my side. JMarc Le 29 mai 2015 17:12:51 CEST, Richard Heck a écrit : > >I'd like to start the 2.1.4 release process by freezing strings, etc. >Any fixes that need to go in before I do that? > >Richard

Re: LyX 2.1.4

Except for #8658, of course. JMarc Le 29 mai 2015 17:51:04 CEST, Jean-Marc Lasgouttes a écrit : >Not on my side. > >JMarc > >Le 29 mai 2015 17:12:51 CEST, Richard Heck a écrit : >> >>I'd like to start the 2.1.4 release process by freezing strings, etc.

Re: Compilation failure un c++11 mode with gcc 4.6

Le 28/05/2015 23:23, pdv a écrit : Starting with commit b596330 lyx fails to compile with cmake/xcode. This seems to be due to "boost::next" having been replaced by "next" and this generates "ambiguous call to 'next'" semantic issues, one of the 2 possibilities being the "next" in lyxalgo.h

Re: Compilation failure un c++11 mode with gcc 4.6

Am Freitag, 29. Mai 2015 um 19:52:03, schrieb Jean-Marc Lasgouttes > Le 28/05/2015 23:23, pdv a écrit : > > Starting with commit b596330 lyx fails to compile with cmake/xcode. > > This seems to be due to "boost::next" having been replaced by "next" and > > this generates

Re: LyX 2.1.4

On 05/29/2015 11:53 AM, Jean-Marc Lasgouttes wrote: Except for #8658, of course. Which is now done rh JMarc Le 29 mai 2015 17:51:04 CEST, Jean-Marc Lasgouttes a écrit : Not on my side. JMarc Le 29 mai 2015 17:12:51 CEST, Richard Heck

Re: [LyX features/master] Fix test for urwclassico font (bug #9576)

Richard Heck wrote: > Oh, sorry, I see. This was updating features/master. and it was me, not Jürgen. The commit-hook can sometimes be quite confusing ;-( Georg

Re: about the tex2lyx tests and proposal for a better method

On 2015-05-28, Uwe Stöhr wrote: > Am 27.05.2015 um 16:53 schrieb Georg Baum: >>> - when I import our test file test-modules.tex I get a LyX file that is >>> >uncompilable: >>> >LaTeX Error: Environment lem undefined. >>> >LaTeX Error: \begin{document} ended by \end{lem}. >>> >But the test result

Re: Compilation failure un c++11 mode with gcc 4.6

Am Freitag, 29. Mai 2015 um 21:59:16, schrieb pdv > On 29/05/15 20:10, Kornel Benko wrote: > > Am Freitag, 29. Mai 2015 um 19:52:03, schrieb Jean-Marc Lasgouttes > > > >> Le 28/05/2015 23:23, pdv a écrit : > >>> Starting with commit b596330 lyx fails

Re: about the tex2lyx tests and proposal for a better method

Uwe Stöhr wrote: > Am 27.05.2015 um 16:53 schrieb Georg Baum: > >> It is_not_ a requirement that test cases always contain sensible data. >> In many cases, it is more effective to design test cases with contents >> which would never occur in practice, for example because it is shorter. > > Hi

Re: about the tex2lyx tests and proposal for a better method

Guenter Milde wrote: > However, whenever a reference changes (to adapt to a new file version or > other changes) or a new test file + reference is added, one must also > check if the new reference is really a *good* one. Yes, this is the key point. > In the case of LyX, this includes checking

Re: Failing tex2lyx tests

On Thu, May 28, 2015 at 6:47 PM, Uwe Stöhr wrote: > Am 26.05.2015 um 04:00 schrieb Scott Kostyshak: > Nevertheless my aim was to split the commits into small > pieces that can easily be reverted if necessary. I agree that this is indeed a good goal. But I find that you often

Re: about the tex2lyx tests and proposal for a better method

Am 29.05.2015 um 23:18 schrieb Georg Baum: I did not suggest that it was impolite. The proposal to stop comparing current test results against known good references, and testing the success of LaTeX compilation instead is not in line with the accepted state of the art in software testing: I

Re: Failing tex2lyx tests

Am 29.05.2015 um 05:59 schrieb Stephan Witt: I can recommend the tool SourceTree from Atlassian. It's available on Windows and Mac. (Yes, no Linux version.) Thanks. I just downloaded it and will give it a try. regards Uwe

Re: Failing tex2lyx tests

Am 30.05.2015 um 01:17 schrieb Scott Kostyshak: I agree that this is indeed a good goal. But I find that you often have follow-up commits. Yes, that is because of the git mess. I think that I am not too stupid but git is nothing for me. Now after years it is still a mystery why e.g. often

Re: LyX 2.1.4

Am 29.05.2015 um 17:12 schrieb Richard Heck: I'd like to start the 2.1.4 release process by freezing strings, etc. Any fixes that need to go in before I do that? These: - http://www.lyx.org/trac/ticket/6211 - http://www.lyx.org/trac/ticket/7850 - http://www.lyx.org/trac/ticket/9371 regards

Re: [LyX/master] delete test file verbatim.tex

Am 29.05.2015 um 07:55 schrieb Guenter Milde: What is the benefit of this file? This file oly checks one style and we already check for this style in another test file? However, if the other test file tests not only for this style but for different features, it is easier to find out the

Re: Failing tex2lyx tests

On 05/29/2015 07:17 PM, Scott Kostyshak wrote: On Thu, May 28, 2015 at 6:47 PM, Uwe Stöhr wrote: Am 26.05.2015 um 04:00 schrieb Scott Kostyshak: Nevertheless my aim was to split the commits into small pieces that can easily be reverted if necessary. I agree that this is

Re: Failing tex2lyx tests

On 05/29/2015 08:29 PM, Uwe Stöhr wrote: Am 30.05.2015 um 01:17 schrieb Scott Kostyshak: I agree that this is indeed a good goal. But I find that you often have follow-up commits. Yes, that is because of the git mess. I think that I am not too stupid but git is nothing for me. Now after