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
[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
| construct...
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. Can you shed
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 confused about is why
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. Can you
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 confused about is why
Title: CONTENT-TEK/
[LaTeX][OCR/Indexing][DjVu][XML/SGML/HTML][FrameMaker][QuarkXpress][InDesign][PDFPS]
LaTeXTypesetting
Multilingual
Desktop
Publishing
XML/SGML
Solutions
.
Get
Published ... Print ... On-line ... Media
Your Partner
þ
High
quality LaTeX
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
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
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
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
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
[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
|
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.
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
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
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.
Title:
[LaTeX][OCR/Indexing][DjVu][XML/SGML/HTML][FrameMaker][QuarkXpress][InDesign][PDF]
LaTeXTypesetting
Multilingual
Desktop
Publishing
XML/SGML
Solutions
.
Get
Published ... Print ... On-line ... Media
Your Partner
þ
High
quality LaTeX typesetting
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
> 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
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
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
22 matches
Mail list logo