On Tue, Nov 3, 2009 at 10:49 AM, Jean-Marc Lasgouttes
wrote:
> Jürgen Spitzmüller writes:
>
>> BH wrote:
>>> I can build and post a binary, but since I don't have Snow Leopard I'm
>>> unable to test.
>>
>> That would be great.
>>
>>> Shall I use the patches first posted in this thread against cur
Dear LyX Developers,
I was trying to edit the LyX wiki so that I could add a reference to the
NIH document class/layouts I created:
http://www.oak-tree.us/blog/index.php/2009/11/02/custom-lyx-nih
The wiki kept asking for a password. Would someone be able to send me
this password, or add www.oak
> Uwe, I think you mixed up something.
thanks and regards Uwe
Uwe Stöhr schrieb:
We shouldn't guess anything. There might be package clashes, it is not
possible to exclude this possibility. While think about this issue I
still think that we need, additionally to your patch, to handle mhchem
the same was as esint and amsmath.
Take for example the attached
rgheck wrote:
On 11/03/2009 10:38 AM, Sebastian Guttenberg wrote:
Hi all
The following bug has the potential to destroy a lot of cross-references
of a document if one is not aware that lyx shows something different
than it does. My Bug-description has three parts. If you don't consider
the first
Uwe, I think you mixed up something.
JMarc
On 11/03/2009 10:38 AM, Sebastian Guttenberg wrote:
Hi all
The following bug has the potential to destroy a lot of cross-references
of a document if one is not aware that lyx shows something different
than it does. My Bug-description has three parts. If you don't consider
the first as bug, then l
Jürgen Spitzmüller writes:
> BH wrote:
>> I can build and post a binary, but since I don't have Snow Leopard I'm
>> unable to test.
>
> That would be great.
>
>> Shall I use the patches first posted in this thread against current branch?
>
> I think only the nofork patch is relevant (for 1.6.4.2)
BH wrote:
> I can build and post a binary, but since I don't have Snow Leopard I'm
> unable to test.
That would be great.
> Shall I use the patches first posted in this thread against current branch?
I think only the nofork patch is relevant (for 1.6.4.2).
Jürgen
Hi all
The following bug has the potential to destroy a lot of cross-references
of a document if one is not aware that lyx shows something different
than it does. My Bug-description has three parts. If you don't consider
the first as bug, then look also at the second which is more apparently
a bug
On Tue, Nov 3, 2009 at 9:56 AM, Jürgen Spitzmüller wrote:
> Jean-Marc Lasgouttes wrote:
>> > I am reluctant to push a mac-related change when nobody wants to test it.
>>
>> OTOH, I am confident about the patches.
>
> If we get someone to build the binary, I'm sure we find some people on lyx-
> use
Jean-Marc Lasgouttes wrote:
> > I am reluctant to push a mac-related change when nobody wants to test it.
>
> OTOH, I am confident about the patches.
If we get someone to build the binary, I'm sure we find some people on lyx-
users to test that.
Jürgen
Jean-Marc Lasgouttes writes:
> I am reluctant to push a mac-related change when nobody wants to test it.
OTOH, I am confident about the patches.
JMarc
Jean-Marc Lasgouttes wrote:
> I am reluctant to push a mac-related change when nobody wants to test it.
I can understand that.
Jürgen
Lars Gullik Bjønnes writes:
> I am quite sure that a downtime is to be expected.
> Not quite sure the exact time. The best I have is "mid-week".
>
> I'll see if I can get some more info so that we can at least put out a
> notification on this list.
Thanks!
JMarc
Jürgen Spitzmüller writes:
> If the fork() disabling proves to be unproblematic, I'd propose to do
> that change in branch as well. What is the status of the autosave
> speedup patch you posted? If it works and if you're confident about
> it, it can be backported as well.
Either these patches wor
Jean-Marc Lasgouttes wrote:
> > Time to proceeed?
>
> Yes. What do you want me to do?
If the fork() disabling proves to be unproblematic, I'd propose to do that
change in branch as well. What is the status of the autosave speedup patch you
posted? If it works and if you're confident about it, i
Jürgen Spitzmüller writes:
> Jean-Marc Lasgouttes wrote:
>> > The patch that disables fork() seems obvious enough to me, but an extra
>> > pair of eyes (and testers) would help.
>>
>> This part is in trunk now. It will maybe make some people test it. This
>> is all I can do unfortunately.
>
> Ti
I am quite sure that a downtime is to be expected.
Not quite sure the exact time. The best I have is "mid-week".
I'll see if I can get some more info so that we can at least put out a
notification on this list.
On Tue, Nov 3, 2009 at 01:39, Jean-Marc Lasgouttes wrote:
> Lars Gullik Bjønnes writ
Uwe Stöhr wrote:
> > Can we set a "Provide hyperref 1" in the layout file (and handle that
> > correctly in source)?
>
> This doesn't help. You can still enable hyperref in the document style
> dialog. When you do this LyX wouldn't load hyperref in the preamble with
> \usepackage{hyperref} bu
Dear all
It happened to me a couple of times that my lyx freezed when I marked
bigger parts of my text, like a whole section, containing plenty of
equations. As I don't know how to exactly reproduce the freeze, I
started lyx in gdb and waited for the next occurrence, which was now.
Below are the la
Jean-Marc Lasgouttes wrote:
> > The patch that disables fork() seems obvious enough to me, but an extra
> > pair of eyes (and testers) would help.
>
> This part is in trunk now. It will maybe make some people test it. This
> is all I can do unfortunately.
Time to proceeed?
Jürgen
The problem is that GuiBox::setSpecial doesn't refill the width unit combo box
correctly (i.e., the data part of it).
In trunk, the bug was fixed due to a more extensive rewrite of the LengthCombo
handling (r28152).
I apply to branch if there are no objections.
Jürgen
Index: src/frontends/qt4/
23 matches
Mail list logo
