Here is a new version of my idea for how to protect static variables
from thread problems.
The first patch introduces a template based on QThreadStorage which acts
kind of like a pointer. The second patch uses the first one to protect
some static variables used in the DocBook output routine.
On 03/22/2014 09:28 PM, Uwe Stöhr wrote:
Am 22.03.2014 15:19, schrieb Stephan Witt:
This must be some misunderstanding. We are talking about user
preferences.
The preferences of your colleague are living in a complete "parallel
universe".
You shouldn't have any access to them. Nobody said the
Am 23.03.2014 02:23, schrieb Richard Heck:
You can commit it now to the 2.1.1-staging branch, if you wish.
Done now.
regards Uwe
Am 22.03.2014 15:19, schrieb Stephan Witt:
This must be some misunderstanding. We are talking about user preferences.
The preferences of your colleague are living in a complete "parallel universe".
You shouldn't have any access to them. Nobody said the administrator should
copy any user preferen
On 03/22/2014 08:50 PM, Uwe Stöhr wrote:
Am 22.03.2014 22:33, schrieb Richard Heck:
If so the tooltip should be
"Words with less than the specified number of characters will not be
completed."
and the label in the dialog should be
"Minimum characters for words that should be completed"
I
Am 22.03.2014 09:11, schrieb JeanMarc Lasgouttes:
On 22 mars 2014 00:09:36 UTC+01:00, "Uwe Stöhr" wrote:
Because on Linux you are the boss of your system while on Windows you
are often not. Even at my
university not everybody was allowed to install programs and e.g. at
work there are on almost
Am 22.03.2014 22:33, schrieb Richard Heck:
If so the tooltip should be
"Words with less than the specified number of characters will not be completed."
and the label in the dialog should be
"Minimum characters for words that should be completed"
If this formulation seems better to you, that
Please commit also to 2.1.1-staging and to 2.0.x if you think that's a
good idea.
rh
On 03/22/2014 07:25 AM, Juergen Spitzmueller wrote:
commit 299574c185d698d90548eb72118346a6d6ad1db1
Author: Juergen Spitzmueller
Date: Sat Mar 22 12:25:25 2014 +0100
ulem commands can be nested.
di
I have created a new branch, 2.1.1-staging. Anything that is committed
to 2.2-staging that would be appropriate for 2.1.1 should also go to
this branch. Mostly, that will mean anything that is also going to
2.0.8, but there may be some 2.1.x-only fixes that should go there as well.
As far as
On 03/21/2014 06:36 PM, Uwe Stöhr wrote:
Am 21.03.2014 04:13, schrieb Richard Heck:
3. "A new preference variable to adjust the minimum length of words
to be collected in the
candidate list for text input completion was provided by Richard
Heck and Stephan Witt."
This feature misses a tooltip
On 03/22/2014 10:26 AM, Stephan Witt wrote:
Am 22.03.2014 um 14:08 schrieb Benjamin Piwowarski :
Yes, and it's done on Mac OS X this way. The first configure run with an
fresh user preferences directory (no preferences present already) checks
for existing preferences from previous releases and
Stephan Witt schreef op 22-3-2014 15:55:
Shouldn't LyX/2.2-staging branch get version 2.2.0dev?
Stephan
I don't think so. When 2.1 is released, the master branch will become
2.2.0dev. The commits that are now in 2.2-staging are merely waiting to
get into master until then.
Just my opinion.
Shouldn't LyX/2.2-staging branch get version 2.2.0dev?
Stephan
Am 22.03.2014 um 14:08 schrieb Benjamin Piwowarski :
>>
>> >> Yes, and it's done on Mac OS X this way. The first configure run with an
>> >> fresh user preferences directory (no preferences present already) checks
>> >> for existing preferences from previous releases and copies them if
>> >> p
Am 22.03.2014 um 00:09 schrieb Uwe Stöhr :
> Am 21.03.2014 23:29, schrieb Stephan Witt:
>> Am 21.03.2014 um 20:56 schrieb Georg Baum :
>>
>> Exactly. I cannot understand why something working on Linux without any
>> problem - the in place upgrade of the .lyx user configuration - shouldn't
>> work
>> Yes, and it's done on Mac OS X this way. The first configure run with an
>> fresh user preferences directory (no preferences present already) checks
>> for existing preferences from previous releases and copies them if
>> present.
>
> OK, and where do you look? On network drives as well as
Uwe Stöhr wrote:
> Am 21.03.2014 23:29, schrieb Stephan Witt:
>> Am 21.03.2014 um 20:56 schrieb Georg Baum
>> :
>>
>> Exactly. I cannot understand why something working on Linux without any
>> problem - the in place upgrade of the .lyx user configuration - shouldn't
>> work on Windows or Mac OS X.
This is an old thread, but I think it was the last message on cmake.
In the 2.2-staging, with the provided patch (and provided I did not break
anything for windows, but I tried to triple check everything), OS X compilation
is (unless I am missing things) nearly feature complete. On OS X, it gene
On 22 mars 2014 00:09:36 UTC+01:00, "Uwe Stöhr" wrote:
>Because on Linux you are the boss of your system while on Windows you
>are often not. Even at my
>university not everybody was allowed to install programs and e.g. at
>work there are on almost all
>PCS several users because everybody can
19 matches
Mail list logo
