Re: Python 3 incompatibilities still exist right?

Ok, let me be splicit. I use extensively Spyder with python 3 for my work, I use also LyX to write my articles. When I installed LyX (on windows) it uses its own bundled python2 and it works fine. The problem arises when I want to import my python graphics into LyX, which should be interpreted

Re: Thread problems with std::basic_string and GNU libstdc++

On 11/20/2014 11:53 PM, Cyrille Artho wrote: Richard Heck wrote: On 11/20/2014 07:07 PM, Cyrille Artho wrote: To those who did not think they observed the crashes: Such crashes may be rare (1 in 100,000 uses), so unless you are looking for them and force them to occur with tool support, you

Re: Python 3 incompatibilities still exist right?

On 11/21/2014 08:25 AM, Alex Vergara Gil wrote: Ok, let me be splicit. I use extensively Spyder with python 3 for my work, I use also LyX to write my articles. When I installed LyX (on windows) it uses its own bundled python2 and it works fine. The problem arises when I want to import my python

Re: Python 3 incompatibilities still exist right?

Am Freitag, 21. November 2014 um 08:55:25, schrieb Richard Heck rgh...@lyx.org On 11/21/2014 08:25 AM, Alex Vergara Gil wrote: Ok, let me be splicit. I use extensively Spyder with python 3 for my work, I use also LyX to write my articles. When I installed LyX (on windows) it uses its own

Re: Python 3 incompatibilities still exist right?

On 11/21/2014 09:23 AM, Kornel Benko wrote: Am Freitag, 21. November 2014 um 08:55:25, schrieb Richard Heck rgh...@lyx.org On 11/21/2014 08:25 AM, Alex Vergara Gil wrote: Ok, let me be splicit. I use extensively Spyder with python 3 for my work, I use also LyX to write my articles. When I

Re: Thread problems with std::basic_string and GNU libstdc++

Le 19/11/2014 22:43, Georg Baum a écrit : What do we do now? I can think of several alternatives: [...] 2) Disable EXPORT_in_THREAD if GNU libstdc++ is found. This is an easy and safe solution, with the disadvantage that it removes a feature (but I think that this is much better than risking

Re: Thread problems with std::basic_string and GNU libstdc++

On 11/21/2014 10:41 AM, Jean-Marc Lasgouttes wrote: Le 19/11/2014 22:43, Georg Baum a écrit : What do we do now? I can think of several alternatives: [...] 2) Disable EXPORT_in_THREAD if GNU libstdc++ is found. This is an easy and safe solution, with the disadvantage that it removes a

Re: [LyX/master] tex2lyx: support for the libertine fonts

Am 20.11.2014 um 02:17 schrieb Scott Kostyshak: - if (options.size() == 1) { + if (options.size() = 1) { - if (options.size() == 1) { + if (options.size() = 1) { What do these two changes have to do with adding the

Re: Clear RELEASE-NOTES on master?

Am 20.11.2014 um 09:10 schrieb Scott Kostyshak skost...@lyx.org: On Tue, Nov 18, 2014 at 3:05 AM, Jean-Marc Lasgouttes lasgout...@lyx.org wrote: Le 18/11/14 02:14, Scott Kostyshak a écrit : The RELEASE-NOTES on master is for 2.1.0. Should it be cleaned so we can add 2.2.0 stuff or is this

Re: Python 3 incompatibilities still exist right?

Richard Heck wrote: It might be possible to specify the full path to the python version you want to use in the relevant converter definition. But I am not sure. This is possible. The magic happens only for python -tt. Even specifying only python3 or python3 -tt as the interpreter for self

Re: Thread problems with std::basic_string and GNU libstdc++

Richard Heck wrote: Yes, I understand that. But it's hard to see what relevant difference there might be between the document set that is causing this crash---which Georg says in the bug report he can produce reliably---and other large documents sets that other people have used frequently

Re: Thread problems with std::basic_string and GNU libstdc++

Enrico Forestieri wrote: Cannot a deep copy be forced after cloning? What about recursing over all non-const strings and doing something like str = str.c_str() ? I would think so, but it would be a bit cumbersome to find all places (and the same problem could arise unnoticed elswhere, if

Re: Thread problems with std::basic_string and GNU libstdc++

Jean-Marc Lasgouttes wrote: AFAICS, the threaded export is interesting mostly because of the cost of running external programs. Could we do the latex export in the main thread and then just do our converter stuff in a multithreaded way? How difficult is that? Good idea. And if exporting to

Re: Thread problems with std::basic_string and GNU libstdc++

Georg Baum wrote: I see. I installed pLyX, but I fear my way of thinking is very different from the one in the pLyX system. At least I did not manage to get it to do what I want. With the help of Andrew I got pLyX to work. Unfortunately the crash is not reproducible with the anonymized

Re: Help with patch for word selection mode on double click

Btw, what you describe is similar to the behaviour of gedit (gtk), but LyX behaviour is the same as the one of kate (qt)... So it seems that there is no general consensus. There is a notable difference in what happens when you move (arrows) with a selection going on: with the current behaviour,

Re: Thread problems with std::basic_string and GNU libstdc++

Richard Heck wrote: Yes, I understand that. But it's hard to see what relevant difference there might be between the document set that is causing this crash---which Georg says in the bug report he can produce reliably---and other large documents sets that other people have used frequently

Re: Clear RELEASE-NOTES on master?

On Fri, Nov 21, 2014 at 12:28 PM, Stephan Witt st.w...@gmx.net wrote: Am 20.11.2014 um 09:10 schrieb Scott Kostyshak skost...@lyx.org: On Tue, Nov 18, 2014 at 3:05 AM, Jean-Marc Lasgouttes lasgout...@lyx.org wrote: Le 18/11/14 02:14, Scott Kostyshak a écrit : The RELEASE-NOTES on master is

Re: Help with patch for word selection mode on double click

On Fri, Nov 21, 2014 at 4:37 PM, Alfredo Braunstein abrau...@lyx.org wrote: Btw, what you describe is similar to the behaviour of gedit (gtk), but LyX behaviour is the same as the one of kate (qt)... So it seems that there is no general consensus. There is a notable difference in what happens

Re: [LyX/master] tex2lyx: support for the libertine fonts

On Fri, Nov 21, 2014 at 11:59 AM, Uwe Stöhr uwesto...@web.de wrote: Am 20.11.2014 um 02:17 schrieb Scott Kostyshak: - if (options.size() == 1) { + if (options.size() = 1) { - if (options.size() == 1) { + if

Pushing to features branch(es)?

Is there any special magic I am supposed to use to push a commit on features/biblatex upstream? [stefano@gorgias]$ git status On branch features/biblatex Your branch is ahead of 'master' by 1 commit. (use git push to publish your local commits) [stefano@gorgias]$ git push Everything

Re: Pushing to features branch(es)?

On Fri, Nov 21, 2014 at 10:55 PM, stefano franchi stefano.fran...@gmail.com wrote: Is there any special magic I am supposed to use to push a commit on features/biblatex upstream? [stefano@gorgias]$ git status On branch features/biblatex Your branch is ahead of 'master' by 1 commit. (use

Re: Python 3 incompatibilities still exist right?

Ok, let me be splicit. I use extensively Spyder with python 3 for my work, I use also LyX to write my articles. When I installed LyX (on windows) it uses its own bundled python2 and it works fine. The problem arises when I want to import my python graphics into LyX, which should be interpreted

Re: Thread problems with std::basic_string and GNU libstdc++

On 11/20/2014 11:53 PM, Cyrille Artho wrote: Richard Heck wrote: On 11/20/2014 07:07 PM, Cyrille Artho wrote: To those who did not think they observed the crashes: Such crashes may be rare (1 in 100,000 uses), so unless you are looking for them and force them to occur with tool support, you

Re: Python 3 incompatibilities still exist right?

On 11/21/2014 08:25 AM, Alex Vergara Gil wrote: Ok, let me be splicit. I use extensively Spyder with python 3 for my work, I use also LyX to write my articles. When I installed LyX (on windows) it uses its own bundled python2 and it works fine. The problem arises when I want to import my python

Re: Python 3 incompatibilities still exist right?

Am Freitag, 21. November 2014 um 08:55:25, schrieb Richard Heck > On 11/21/2014 08:25 AM, Alex Vergara Gil wrote: > > Ok, let me be splicit. I use extensively Spyder with python 3 for my > > work, I use also LyX to write my articles. When I installed LyX (on > > windows) it uses

Re: Python 3 incompatibilities still exist right?

On 11/21/2014 09:23 AM, Kornel Benko wrote: Am Freitag, 21. November 2014 um 08:55:25, schrieb Richard Heck On 11/21/2014 08:25 AM, Alex Vergara Gil wrote: Ok, let me be splicit. I use extensively Spyder with python 3 for my work, I use also LyX to write my articles. When I

Re: Thread problems with std::basic_string and GNU libstdc++

Le 19/11/2014 22:43, Georg Baum a écrit : What do we do now? I can think of several alternatives: [...] 2) Disable EXPORT_in_THREAD if GNU libstdc++ is found. This is an easy and safe solution, with the disadvantage that it removes a feature (but I think that this is much better than risking

Re: Thread problems with std::basic_string and GNU libstdc++

On 11/21/2014 10:41 AM, Jean-Marc Lasgouttes wrote: Le 19/11/2014 22:43, Georg Baum a écrit : What do we do now? I can think of several alternatives: [...] 2) Disable EXPORT_in_THREAD if GNU libstdc++ is found. This is an easy and safe solution, with the disadvantage that it removes a

Re: [LyX/master] tex2lyx: support for the libertine fonts

Am 20.11.2014 um 02:17 schrieb Scott Kostyshak: - if (options.size() == 1) { + if (options.size() >= 1) { - if (options.size() == 1) { + if (options.size() >= 1) { What do these two changes have to do with adding the

Re: Clear RELEASE-NOTES on master?

Am 20.11.2014 um 09:10 schrieb Scott Kostyshak : > On Tue, Nov 18, 2014 at 3:05 AM, Jean-Marc Lasgouttes > wrote: >> Le 18/11/14 02:14, Scott Kostyshak a écrit : >>> >>> The RELEASE-NOTES on master is for 2.1.0. Should it be cleaned so we >>> can add 2.2.0

Re: Python 3 incompatibilities still exist right?

Richard Heck wrote: > It might be possible to specify the full path to the python version you > want to use in > the relevant converter definition. But I am not sure. This is possible. The magic happens only for "python -tt". Even specifying only "python3" or "python3 -tt" as the interpreter

Re: Thread problems with std::basic_string and GNU libstdc++

Richard Heck wrote: > Yes, I understand that. But it's hard to see what relevant difference > there might be > between the document set that is causing this crash---which Georg says > in the bug > report he can produce "reliably"---and other large documents sets that > other people > have used

Re: Thread problems with std::basic_string and GNU libstdc++

Enrico Forestieri wrote: > Cannot a deep copy be forced after cloning? What about recursing over > all non-const strings and doing something like str = str.c_str() ? I would think so, but it would be a bit cumbersome to find all places (and the same problem could arise unnoticed elswhere, if

Re: Thread problems with std::basic_string and GNU libstdc++

Jean-Marc Lasgouttes wrote: > AFAICS, the threaded export is interesting mostly because of the cost of > running external programs. Could we do the latex export in the main > thread and then just do our converter stuff in a multithreaded way? How > difficult is that? Good idea. > And if

Re: Thread problems with std::basic_string and GNU libstdc++

Georg Baum wrote: > I see. I installed pLyX, but I fear my way of thinking is very different > from the one in the pLyX system. At least I did not manage to get it to do > what I want. With the help of Andrew I got pLyX to work. Unfortunately the crash is not reproducible with the anonymized

Re: Help with patch for "word selection mode" on double click

Btw, what you describe is similar to the behaviour of gedit (gtk), but LyX behaviour is the same as the one of kate (qt)... So it seems that there is no general consensus. There is a notable difference in what happens when you move (arrows) with a selection going on: with the current behaviour,

Re: Thread problems with std::basic_string and GNU libstdc++

Richard Heck wrote: > Yes, I understand that. But it's hard to see what relevant difference > there might be > between the document set that is causing this crash---which Georg says > in the bug > report he can produce "reliably"---and other large documents sets that > other people > have used

Re: Clear RELEASE-NOTES on master?

On Fri, Nov 21, 2014 at 12:28 PM, Stephan Witt wrote: > Am 20.11.2014 um 09:10 schrieb Scott Kostyshak : > >> On Tue, Nov 18, 2014 at 3:05 AM, Jean-Marc Lasgouttes >> wrote: >>> Le 18/11/14 02:14, Scott Kostyshak a écrit : The

Re: Help with patch for "word selection mode" on double click

On Fri, Nov 21, 2014 at 4:37 PM, Alfredo Braunstein wrote: > Btw, what you describe is similar to the behaviour of gedit (gtk), but > LyX behaviour is the same as the one of kate (qt)... So it seems that > there is no general consensus. There is a notable difference in what >

Re: [LyX/master] tex2lyx: support for the libertine fonts

On Fri, Nov 21, 2014 at 11:59 AM, Uwe Stöhr wrote: > Am 20.11.2014 um 02:17 schrieb Scott Kostyshak: > >>> - if (options.size() == 1) { >>> + if (options.size() >= 1) { >>> - if (options.size() == 1) { >>> +

Pushing to features branch(es)?

Is there any special magic I am supposed to use to push a commit on features/biblatex upstream? [stefano@gorgias]$ git status On branch features/biblatex Your branch is ahead of 'master' by 1 commit. (use "git push" to publish your local commits) [stefano@gorgias]$ git push Everything

Re: Pushing to features branch(es)?

On Fri, Nov 21, 2014 at 10:55 PM, stefano franchi wrote: > Is there any special magic I am supposed to use to push a commit on > features/biblatex upstream? > > [stefano@gorgias]$ git status > On branch features/biblatex > Your branch is ahead of 'master' by 1 commit. >