On Sat, Nov 6, 2010 at 11:27 PM, BH bewih...@gmail.com wrote:
On Sat, Nov 6, 2010 at 5:22 PM, Abdelrazak Younes you...@lyx.org wrote:
Hi there,
My employer just got me a brand new MacBook Pro. I am not impressed so
far
by MacOS so called legendary user friendlyness but I am trying to get
On Sun, Nov 7, 2010 at 10:11 AM, Abdelrazak Younes you...@lyx.org wrote:
On Sat, Nov 6, 2010 at 11:27 PM, BH bewih...@gmail.com wrote:
On Sat, Nov 6, 2010 at 5:22 PM, Abdelrazak Younes you...@lyx.org wrote:
Hi there,
My employer just got me a brand new MacBook Pro. I am not impressed so
On Sun, Nov 7, 2010 at 10:21 AM, Abdelrazak Younes you...@lyx.org wrote:
Mac user friendliness is an acquired taste.
Just as Windows or any other desktop then :-)
But it seems that MacOS wants to impose me a way of working and I really
don't like it. I find it particularly irritating that I
Am 06.11.2010 um 23:27 schrieb BH:
On Sat, Nov 6, 2010 at 5:22 PM, Abdelrazak Younes you...@lyx.org wrote:
Hi there,
My employer just got me a brand new MacBook Pro. I am not impressed so far
by MacOS so called legendary user friendlyness but I am trying to get used
to it right now.
The
Am 07.11.2010 um 10:58 schrieb Liviu Andronic:
On Sun, Nov 7, 2010 at 10:21 AM, Abdelrazak Younes you...@lyx.org wrote:
Mac user friendliness is an acquired taste.
Just as Windows or any other desktop then :-)
But it seems that MacOS wants to impose me a way of working and I really
don't
Le 7 nov. 10 à 10:21, Abdelrazak Younes a écrit :
But it seems that MacOS wants to impose me a way of working and I
really don't like it.
I find it particularly irritating that I cannot maximize all windows
the same way.
Safari for example only maximizes vertically. I hope LyX is not
doing
On 07/11/2010 10:58, Liviu Andronic wrote:
On Sun, Nov 7, 2010 at 10:21 AM, Abdelrazak Younesyou...@lyx.org wrote:
Mac user friendliness is an acquired taste.
Just as Windows or any other desktop then :-)
But it seems that MacOS wants to impose me a way of working and I really
The attached seems to work for that bug, but I haven't tested extensively as
I don't use Bibitems myself. Still, the approach seems right, and possible,
since the updateBuffer() call is now from one place.
As I mention in the bug report, though, there are some other issues that
remain.
I
Log:
From what I read Qt 4.2 is dead because of new threads code
===
--- lyx-devel/trunk/INSTALL Sat Nov 6 19:42:19 2010 (r36166)
+++ lyx-devel/trunk/INSTALL Sat Nov 6 23:53:12 2010 (r36167)
-LyX has been tested with all Qt
Vincent van Ravesteijn wrote:
===
--- lyx-devel/trunk/INSTALL Sat Nov 6 19:42:19 2010 (r36166)
+++ lyx-devel/trunk/INSTALL Sat Nov 6 23:53:12 2010 (r36167)
-LyX has been tested with all Qt versions since Qt 4.2.2. For
Stephan Witt wrote:
I'm using
* self compiled Qt 4.6.3 library (because of #6706 is fixed then)
into INSTALL.MacOSX?
p
Am Samstag, 6. November 2010 schrieb Pavel Sanda:
fans of cmake,
could you please check that the file INSTALL.cmake is up-to-date?
thanks,
pavel
Is there something specific we have to check? Most of the data to install is
done with globbing,
so we adapt new files (and discard non existant
Am 07.11.2010 um 19:52 schrieb Pavel Sanda:
Stephan Witt wrote:
I'm using
* self compiled Qt 4.6.3 library (because of #6706 is fixed then)
into INSTALL.MacOSX?
What exactly?
It's described there already how to make a self compiled Qt library.
Regarding the patch - the link is in
Stephan Witt wrote:
I'm using
* self compiled Qt 4.6.3 library (because of #6706 is fixed then)
into INSTALL.MacOSX?
What exactly?
we suggest to use lyx with qt 4.6.2?
p
Am 07.11.2010 um 21:54 schrieb Pavel Sanda:
Stephan Witt wrote:
I'm using
* self compiled Qt 4.6.3 library (because of #6706 is fixed then)
into INSTALL.MacOSX?
What exactly?
we suggest to use lyx with qt 4.6.2?
Ah ok, it doesn't make a difference AFAICS.
4.6.2 is working well too
Am 07.11.2010 um 22:02 schrieb Stephan Witt:
Am 07.11.2010 um 21:54 schrieb Pavel Sanda:
Stephan Witt wrote:
I'm using
* self compiled Qt 4.6.3 library (because of #6706 is fixed then)
into INSTALL.MacOSX?
What exactly?
we suggest to use lyx with qt 4.6.2?
Ah ok, it doesn't
To be clear: the bug is in 4.6.3 present too.
That's why the patch is needed...
Stephan
Which bug are we talking about here ?
Vincent
Le 7 nov. 10 à 16:31, uwesto...@lyx.org a écrit :
Log:
stdinsets.inc, InsetERT.cpp: change ERT to TeX to be consistent -
the documentation and all other menus use consequently since LyX
1.6.0 TeX-code
because it turned out that ERT is a meaningless abbreviation for new
users
Err, did we
Le 7 nov. 10 à 22:08, sw...@lyx.org a écrit :
Author: switt
Date: Sun Nov 7 22:08:23 2010
New Revision: 36200
URL: http://www.lyx.org/trac/changeset/36200
Log:
we now require gettext version 0.18 at least
Why is that? Shall we do the same for all of LyX? We could use
this version as
Op 7-11-2010 22:19, Jean-Marc Lasgouttes schreef:
Le 7 nov. 10 à 16:31, uwesto...@lyx.org a écrit :
Log:
stdinsets.inc, InsetERT.cpp: change ERT to TeX to be consistent -
the documentation and all other menus use consequently since LyX
1.6.0 TeX-code
because it turned out that ERT is a
Jean-Marc Lasgouttes wrote:
Err, did we ever discuss this?
I am personally for keeping ERT.
* it has been named like that for ages and is part of LyX identity
i have very similar feelings here.
pavel
On 11/06/2010 07:24 PM, sa...@lyx.org wrote:
Author: sanda
Date: Sun Nov 7 00:24:50 2010
New Revision: 36170
URL: http://www.lyx.org/trac/changeset/36170
Log:
Update docs
Modified:
lyx-devel/trunk/INSTALL
lyx-devel/trunk/README
Modified: lyx-devel/trunk/INSTALL
Richard Heck wrote:
that can be taken out now. However, my sense is that whatever is stopping
compilation with 4.2.x could have been wrapped in #ifs. The
EXPORT_IN_THREAD code requires 4.4.x, yes, but you should be able to set
EXPORT_in_THREAD to 0 and skip that stuff.
i'm all for
Le 7 nov. 10 à 22:15, rgh...@lyx.org a écrit :
Author: rgheck
Date: Sun Nov 7 22:15:01 2010
New Revision: 36201
URL: http://www.lyx.org/trac/changeset/36201
Log:
Missing format info for 406. Also, add revision information to
recent changes.
Thanks.
JMarc
On 11/07/2010 11:53 AM, Vincent van Ravesteijn wrote:
The attached seems to work for that bug, but I haven't tested extensively as
I don't use Bibitems myself. Still, the approach seems right, and possible,
since the updateBuffer() call is now from one place.
As I mention in the bug report,
Le 7 nov. 10 à 22:30, Vincent van Ravesteijn a écrit :
Yes.
Users thought we were being unrespectful to (La)TeX by calling it
evil.
Look back in the archives ;).
Would you have a link? (or at least a time window)?
This is very interesting. The church of TeX?
JMarc
Use the editor to create a new keybinding. Now try to modify it. Error:
Have to delete old one before adding new one.
Richard
hello,
all planned features for lyx 2.0 are in. starting from now
the main aim is to fix up the important bugs and regressions.
this also means freezing any refactorization work which is not
tightly connected with fixing bug(s).
if we are able to shrink the list of bugs to some reasonable
So I had a look at the lyx2lyx for this and have a general question.
Both in revert_multirowOffset and revert_multirow, we do not really do a
proper reversion. The rowspan is set to two and the width to 2cm,
because the information required to set both properly is not readily
available. So I
On Sun, Nov 07, 2010 at 10:43:40PM +0100, Pavel Sanda wrote:
Jean-Marc Lasgouttes wrote:
Err, did we ever discuss this?
I am personally for keeping ERT.
* it has been named like that for ages and is part of LyX identity
i have very similar feelings here.
+1
--
Enrico
On Sun, Nov 07, 2010 at 10:56:01PM +0100, Pavel Sanda wrote:
Richard Heck wrote:
that can be taken out now. However, my sense is that whatever is stopping
compilation with 4.2.x could have been wrapped in #ifs. The
EXPORT_IN_THREAD code requires 4.4.x, yes, but you should be able to set
On Sun, Nov 7, 2010 at 10:19 PM, Jean-Marc Lasgouttes
lasgout...@lyx.org wrote:
Personally, I would appreciate to see that removed. And we should probably
do
an ffort to explain why this is named ERT and why using it is not some kind
of
silver bullet. And yes, I do use some ERT in my
On 08.11.2010 00:34, Enrico Forestieri wrote:
On Sun, Nov 07, 2010 at 10:56:01PM +0100, Pavel Sanda wrote:
Richard Heck wrote:
that can be taken out now. However, my sense is that whatever is stopping
compilation with 4.2.x could have been wrapped in #ifs. The
EXPORT_IN_THREAD code
On Sun, Nov 7, 2010 at 3:45 PM, Stephan Witt st.w...@gmx.net wrote:
Am 07.11.2010 um 19:52 schrieb Pavel Sanda:
Stephan Witt wrote:
I'm using
* self compiled Qt 4.6.3 library (because of #6706 is fixed then)
into INSTALL.MacOSX?
What exactly?
It's described there already how to make a
Enrico Forestieri wrote:
#ifdefs where placed without care. My feeling is that it would not be
at all difficult resolving this.
can you try please?
pavel
On Mon, Nov 08, 2010 at 12:40:52AM +0100, Peter Kümmel wrote:
On 08.11.2010 00:34, Enrico Forestieri wrote:
On Sun, Nov 07, 2010 at 10:56:01PM +0100, Pavel Sanda wrote:
Richard Heck wrote:
that can be taken out now. However, my sense is that whatever is stopping
compilation with
On Mon, Nov 08, 2010 at 12:41:28AM +0100, Pavel Sanda wrote:
Enrico Forestieri wrote:
#ifdefs where placed without care. My feeling is that it would not be
at all difficult resolving this.
can you try please?
The link fails because the xxxAndDestroy() methods are #ifdef'd out.
However,
On 08.11.2010 01:15, Enrico Forestieri wrote:
On Mon, Nov 08, 2010 at 12:41:28AM +0100, Pavel Sanda wrote:
Enrico Forestieri wrote:
#ifdefs where placed without care. My feeling is that it would not be
at all difficult resolving this.
can you try please?
The link fails because the
On Mon, Nov 08, 2010 at 01:42:35AM +0100, Peter Kümmel wrote:
On 08.11.2010 01:15, Enrico Forestieri wrote:
On Mon, Nov 08, 2010 at 12:41:28AM +0100, Pavel Sanda wrote:
Enrico Forestieri wrote:
#ifdefs where placed without care. My feeling is that it would not be
at all difficult
Jean-Marc Lasgouttes wrote:
Err, did we ever discuss this?
I am personally for keeping ERT.
+1.
* this is not used only for TeX (works in docbook AFAIK)
And it's not even TeX in the most cases (but LaTeX).
Jürgen
On Sat, Nov 6, 2010 at 11:27 PM, BH wrote:
> On Sat, Nov 6, 2010 at 5:22 PM, Abdelrazak Younes wrote:
> > Hi there,
> > My employer just got me a brand new MacBook Pro. I am not impressed so
> far
> > by MacOS so called legendary user friendlyness but I am
On Sun, Nov 7, 2010 at 10:11 AM, Abdelrazak Younes wrote:
> On Sat, Nov 6, 2010 at 11:27 PM, BH wrote:
>
>> On Sat, Nov 6, 2010 at 5:22 PM, Abdelrazak Younes wrote:
>> > Hi there,
>> > My employer just got me a brand new MacBook Pro. I am not
On Sun, Nov 7, 2010 at 10:21 AM, Abdelrazak Younes wrote:
>> Mac user friendliness is an acquired taste.
>
> Just as Windows or any other desktop then :-)
> But it seems that MacOS wants to impose me a way of working and I really
> don't like it. I find it particularly irritating
Am 06.11.2010 um 23:27 schrieb BH:
> On Sat, Nov 6, 2010 at 5:22 PM, Abdelrazak Younes wrote:
>> Hi there,
>> My employer just got me a brand new MacBook Pro. I am not impressed so far
>> by MacOS so called legendary user friendlyness but I am trying to get used
>> to it right
Am 07.11.2010 um 10:58 schrieb Liviu Andronic:
> On Sun, Nov 7, 2010 at 10:21 AM, Abdelrazak Younes wrote:
>>> Mac user friendliness is an acquired taste.
>>
>> Just as Windows or any other desktop then :-)
>> But it seems that MacOS wants to impose me a way of working and I
Le 7 nov. 10 à 10:21, Abdelrazak Younes a écrit :
But it seems that MacOS wants to impose me a way of working and I
really don't like it.
I find it particularly irritating that I cannot maximize all windows
the same way.
Safari for example only maximizes vertically. I hope LyX is not
doing
On 07/11/2010 10:58, Liviu Andronic wrote:
On Sun, Nov 7, 2010 at 10:21 AM, Abdelrazak Younes wrote:
Mac user friendliness is an acquired taste.
Just as Windows or any other desktop then :-)
But it seems that MacOS wants to impose me a way of working and I really
> The attached seems to work for that bug, but I haven't tested extensively as
> I don't use Bibitems myself. Still, the approach seems right, and possible,
> since the updateBuffer() call is now from one place.
>
> As I mention in the bug report, though, there are some other issues that
> remain.
> Log:
> From what I read Qt 4.2 is dead because of new threads code
===
> --- lyx-devel/trunk/INSTALL Sat Nov 6 19:42:19 2010 (r36166)
> +++ lyx-devel/trunk/INSTALL Sat Nov 6 23:53:12 2010 (r36167)
> -LyX has been tested with
Vincent van Ravesteijn wrote:
> ===
> > --- lyx-devel/trunk/INSTALL Sat Nov 6 19:42:19 2010 (r36166)
> > +++ lyx-devel/trunk/INSTALL Sat Nov 6 23:53:12 2010 (r36167)
> > -LyX has been tested with all Qt versions since Qt 4.2.2.
Stephan Witt wrote:
> I'm using
> * self compiled Qt 4.6.3 library (because of #6706 is fixed then)
into INSTALL.MacOSX?
p
Am Samstag, 6. November 2010 schrieb Pavel Sanda:
> fans of cmake,
> could you please check that the file INSTALL.cmake is up-to-date?
> thanks,
> pavel
Is there something specific we have to check? Most of the data to install is
done with globbing,
so we adapt new files (and discard non
Am 07.11.2010 um 19:52 schrieb Pavel Sanda:
> Stephan Witt wrote:
>> I'm using
>> * self compiled Qt 4.6.3 library (because of #6706 is fixed then)
>
> into INSTALL.MacOSX?
What exactly?
It's described there already how to make a self compiled Qt library.
Regarding the patch - the link is
Stephan Witt wrote:
> >> I'm using
> >> * self compiled Qt 4.6.3 library (because of #6706 is fixed then)
> >
> > into INSTALL.MacOSX?
>
> What exactly?
we suggest to use lyx with qt 4.6.2?
p
Am 07.11.2010 um 21:54 schrieb Pavel Sanda:
> Stephan Witt wrote:
I'm using
* self compiled Qt 4.6.3 library (because of #6706 is fixed then)
>>>
>>> into INSTALL.MacOSX?
>>
>> What exactly?
>
> we suggest to use lyx with qt 4.6.2?
Ah ok, it doesn't make a difference AFAICS.
4.6.2
Am 07.11.2010 um 22:02 schrieb Stephan Witt:
> Am 07.11.2010 um 21:54 schrieb Pavel Sanda:
>
>> Stephan Witt wrote:
> I'm using
> * self compiled Qt 4.6.3 library (because of #6706 is fixed then)
into INSTALL.MacOSX?
>>>
>>> What exactly?
>>
>> we suggest to use lyx with qt
> To be clear: the bug is in 4.6.3 present too.
> That's why the patch is needed...
>
> Stephan
>
Which bug are we talking about here ?
Vincent
Le 7 nov. 10 à 16:31, uwesto...@lyx.org a écrit :
Log:
stdinsets.inc, InsetERT.cpp: change "ERT" to "TeX" to be consistent -
the documentation and all other menus use consequently since LyX
1.6.0 "TeX-code"
because it turned out that ERT is a meaningless abbreviation for new
users
Err,
Le 7 nov. 10 à 22:08, sw...@lyx.org a écrit :
Author: switt
Date: Sun Nov 7 22:08:23 2010
New Revision: 36200
URL: http://www.lyx.org/trac/changeset/36200
Log:
we now require gettext version 0.18 at least
Why is that? Shall we do the same for all of LyX? We could use
this version as
Op 7-11-2010 22:19, Jean-Marc Lasgouttes schreef:
Le 7 nov. 10 à 16:31, uwesto...@lyx.org a écrit :
Log:
stdinsets.inc, InsetERT.cpp: change "ERT" to "TeX" to be consistent -
the documentation and all other menus use consequently since LyX
1.6.0 "TeX-code"
because it turned out that ERT is a
Jean-Marc Lasgouttes wrote:
>
> Err, did we ever discuss this?
>
> I am personally for keeping ERT.
>
> * it has been named like that for ages and is part of LyX identity
i have very similar feelings here.
pavel
On 11/06/2010 07:24 PM, sa...@lyx.org wrote:
Author: sanda
Date: Sun Nov 7 00:24:50 2010
New Revision: 36170
URL: http://www.lyx.org/trac/changeset/36170
Log:
Update docs
Modified:
lyx-devel/trunk/INSTALL
lyx-devel/trunk/README
Modified: lyx-devel/trunk/INSTALL
Richard Heck wrote:
> that can be taken out now. However, my sense is that whatever is stopping
> compilation with 4.2.x could have been wrapped in #ifs. The
> EXPORT_IN_THREAD code requires 4.4.x, yes, but you should be able to set
> EXPORT_in_THREAD to 0 and skip that stuff.
i'm all for
Le 7 nov. 10 à 22:15, rgh...@lyx.org a écrit :
Author: rgheck
Date: Sun Nov 7 22:15:01 2010
New Revision: 36201
URL: http://www.lyx.org/trac/changeset/36201
Log:
Missing format info for 406. Also, add revision information to
recent changes.
Thanks.
JMarc
On 11/07/2010 11:53 AM, Vincent van Ravesteijn wrote:
The attached seems to work for that bug, but I haven't tested extensively as
I don't use Bibitems myself. Still, the approach seems right, and possible,
since the updateBuffer() call is now from one place.
As I mention in the bug report,
Le 7 nov. 10 à 22:30, Vincent van Ravesteijn a écrit :
Yes.
Users thought we were being unrespectful to (La)TeX by calling it
evil.
Look back in the archives ;).
Would you have a link? (or at least a time window)?
This is very interesting. The church of TeX?
JMarc
Use the editor to create a new keybinding. Now try to modify it. Error:
Have to delete old one before adding new one.
Richard
hello,
all planned features for lyx 2.0 are in. starting from now
the main aim is to fix up the important bugs and regressions.
this also means freezing any refactorization work which is not
tightly connected with fixing bug(s).
if we are able to shrink the list of bugs to some reasonable
So I had a look at the lyx2lyx for this and have a general question.
Both in revert_multirowOffset and revert_multirow, we do not really do a
proper reversion. The rowspan is set to two and the width to 2cm,
because the information required to set both properly is not readily
available. So I
On Sun, Nov 07, 2010 at 10:43:40PM +0100, Pavel Sanda wrote:
> Jean-Marc Lasgouttes wrote:
> >
> > Err, did we ever discuss this?
> >
> > I am personally for keeping ERT.
> >
> > * it has been named like that for ages and is part of LyX identity
>
> i have very similar feelings here.
+1
--
On Sun, Nov 07, 2010 at 10:56:01PM +0100, Pavel Sanda wrote:
> Richard Heck wrote:
> > that can be taken out now. However, my sense is that whatever is stopping
> > compilation with 4.2.x could have been wrapped in #ifs. The
> > EXPORT_IN_THREAD code requires 4.4.x, yes, but you should be able
On Sun, Nov 7, 2010 at 10:19 PM, Jean-Marc Lasgouttes
wrote:
> Personally, I would appreciate to see that removed. And we should probably
> do
> an ffort to explain why this is named ERT and why using it is not some kind
> of
> silver bullet. And yes, I do use some ERT in my
On 08.11.2010 00:34, Enrico Forestieri wrote:
> On Sun, Nov 07, 2010 at 10:56:01PM +0100, Pavel Sanda wrote:
>
>> Richard Heck wrote:
>>> that can be taken out now. However, my sense is that whatever is stopping
>>> compilation with 4.2.x could have been wrapped in #ifs. The
>>>
On Sun, Nov 7, 2010 at 3:45 PM, Stephan Witt wrote:
>
> Am 07.11.2010 um 19:52 schrieb Pavel Sanda:
>
>> Stephan Witt wrote:
>>> I'm using
>>> * self compiled Qt 4.6.3 library (because of #6706 is fixed then)
>>
>> into INSTALL.MacOSX?
>
> What exactly?
>
> It's described there
Enrico Forestieri wrote:
> #ifdefs where placed without care. My feeling is that it would not be
> at all difficult resolving this.
can you try please?
pavel
On Mon, Nov 08, 2010 at 12:40:52AM +0100, Peter Kümmel wrote:
> On 08.11.2010 00:34, Enrico Forestieri wrote:
> > On Sun, Nov 07, 2010 at 10:56:01PM +0100, Pavel Sanda wrote:
> >
> >> Richard Heck wrote:
> >>> that can be taken out now. However, my sense is that whatever is stopping
> >>>
On Mon, Nov 08, 2010 at 12:41:28AM +0100, Pavel Sanda wrote:
> Enrico Forestieri wrote:
> > #ifdefs where placed without care. My feeling is that it would not be
> > at all difficult resolving this.
>
> can you try please?
The link fails because the xxxAndDestroy() methods are #ifdef'd out.
On 08.11.2010 01:15, Enrico Forestieri wrote:
> On Mon, Nov 08, 2010 at 12:41:28AM +0100, Pavel Sanda wrote:
>
>> Enrico Forestieri wrote:
>>> #ifdefs where placed without care. My feeling is that it would not be
>>> at all difficult resolving this.
>>
>> can you try please?
>
> The link fails
On Mon, Nov 08, 2010 at 01:42:35AM +0100, Peter Kümmel wrote:
> On 08.11.2010 01:15, Enrico Forestieri wrote:
> > On Mon, Nov 08, 2010 at 12:41:28AM +0100, Pavel Sanda wrote:
> >
> >> Enrico Forestieri wrote:
> >>> #ifdefs where placed without care. My feeling is that it would not be
> >>> at
Jean-Marc Lasgouttes wrote:
> Err, did we ever discuss this?
>
> I am personally for keeping ERT.
+1.
> * this is not used only for TeX (works in docbook AFAIK)
And it's not even TeX in the most cases (but LaTeX).
Jürgen
80 matches
Mail list logo