CVS lyx math crash slightly better

C-N (new document) C-M (insert math inset) 6 ^ (at the "^", lyx crashes). -- Kayvan A. Sylvan | Proud husband of | Father to my kids: Sylvan Associates, Inc. | Laura Isabella Sylvan | Katherine Yelena (8/8/89) http://sylvan.com/~kayvan | "crown of her husband" | Robin Gregory (2

Re: Your LaTeX/Digitization/XML Partner

On Wednesday 28 January 2004 12:48 pm, Kuba Ober wrote: > > Amr Aboelmagd > > Content-TeK Incorporation > > http://www.content-tek.com > > That's preposterous. As in one would think people using LaTeX are up to higher standards. I needed to elaborate :) Cheers, Kuba

Re: Your LaTeX/Digitization/XML Partner

> Amr Aboelmagd > Content-TeK Incorporation > http://www.content-tek.com That's preposterous. Hopefully all readers of this list can abstain from doing any business with those people. Cheers, Kuba

booktabs/tableaux support in 1.3.x ?

Hi, Since some time I'm contemplating implementing booktabs a.k.a. tableaux support for 1.3.x. Would that have a chance to go in, if properly done? I.e. are any new features allowed into 1.3.x? I might have asked that before, but have forgotten the answer since :) * I'm thinking of adding a pe

Your LaTeX/Digitization/XML Partner

Title: [LaTeX][OCR/Indexing][DjVu][XML/SGML/HTML][FrameMaker][QuarkXpress][InDesign][PDF&PS] LaTeXTypesetting Multilingual Desktop Publishing    XML/SGML Solutions .   Get Published ... Print ... On-line ... Media   Your Partner þ High quality LaTeX typesetti

Re: Compile error

Angus Leeming <[EMAIL PROTECTED]> writes: | Lars Gullik Bjønnes wrote: >>> It compiles if I change line 838 of src/Cursor.C from >>> if (t.operator->() != anchor_[depth()].inset()) > | I wonder what has been smoked here to think this is a nice | construct... >>> >> | Agreed.

Re: Compile error

Lars Gullik Bjønnes wrote: >> It compiles if I change line 838 of src/Cursor.C from >> if (t.operator->() != anchor_[depth()].inset()) >>> | I wonder what has been smoked here to think this is a nice >>> | construct... >> > | Agreed. What I'm confused about is why operator->() behaves

Re: Compile error

Angus Leeming <[EMAIL PROTECTED]> writes: | Lars Gullik Bjønnes wrote: > It compiles if I change line 838 of src/Cursor.C from > if (t.operator->() != anchor_[depth()].inset()) >>> >> | I wonder what has been smoked here to think this is a nice >> | construct... > | Agreed. What I'm confus

Re: Compile error

Lars Gullik Bjønnes wrote: It compiles if I change line 838 of src/Cursor.C from if (t.operator->() != anchor_[depth()].inset()) >> > | I wonder what has been smoked here to think this is a nice > | construct... Agreed. What I'm confused about is why operator->() behaves differently. Ca

Re: Compile error

[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes: | Angus Leeming <[EMAIL PROTECTED]> writes: > | | Georg Baum wrote: >>> It compiles if I change line 838 of src/Cursor.C from >>> >>> if (t.operator->() != anchor_[depth()].inset()) > | I wonder what has been smoked here to think this is a nice | co

Re: Compile error

Angus Leeming <[EMAIL PROTECTED]> writes: | Georg Baum wrote: >> It compiles if I change line 838 of src/Cursor.C from >> >> if (t.operator->() != anchor_[depth()].inset()) I wonder what has been smoked here to think this is a nice construct... -- Lgb