On Thu, 21 Oct 1999, Martin Vermeer wrote:
[...]
> It really works! I even tried it for Theorem + enumerate in AMS article.
> Works too. (Is this in the users guide???)
>
> This combination (red {}) is needed/useful in many other circumstances also.
> What about making it an inset / special cha
> 2) It isn't possible to embed an environment as the first element in
> another environment.
This IS actually possible; I have advised this some time earlier to someone.
As follows (using here enumerate on two levels as an example):
1 {}
a The text of 1a
b The text of 1b
2 a The text of 2a
Hiya...
I'm using LyX quite heavily at the moment (for mathematical notes), and
I think there are some weaknesses with its support of nested
environment:
1) The display is often counter-intuitive:
When, for example, embedding a 'Note' inside a 'Proof' (I assume this is
a reasonable thing to do)
Hello. I'd like to report a bug found in LyX version 1.0.4.
When the language is Spanish, any [protected_blank] followed by a [n]
is interpreted as [\~n], and gives a [ñ] in the dvi output (a spanish
character made as a combination of [~] and [n]).
As a workaround, I write [{}] in Tex Mode betwe
Greetings to all:
First, many thanks for a wonderful program which I use
daily. I rarely encounter any problems with it, but here is
a small one.
When entering a multi-line equation, and the beginning of
the second (or following) line begins with a "[" character,
LaTeX sometimes gets confused. F
On 19 Oct 1999 17:40:35 +0200, Lars Gullik Bj°nnes wrote:
>NO!! You have to check the standard before doing _ANY_ changes to
>lyxstring.
>
>|
>| I'll fix this now and if you don't like it then you (you is general not JMarc;)
>| can refix this and also all instances in the code where we allocate
On 19 Oct 1999 23:09:24 +0900, [EMAIL PROTECTED] wrote:
>In an ideal world where you have plenty of time and diligence to maintain
>any macro set (Imake, autoconf, tmake, ... whatever) actively for wide
>portability, it might be desirable. In the real world, although you may
>see quite noticeabl
Hi!
I had a look at figinset.C, which segfaults with xforms 0.89. Here we
don't have the same problem as in the tabular stuff (hide and callbacks),
but the fl_free_form() call is segfaulting. I removed that calls and
now it does not segfault anymore, but we obviously have a memory leak
(not very
OK, I made some progress with the handling of streams, but now I am
blocked by
cxx: Error: ../../../lyx-devel/src/mathed/../support/lyxstring.h, line 155:
function "lyxstring::lyxstring()" was referenced but not defined
inline lyxstring();
---^
cxx: Error: ../../..
> "Guillermo" == Guillermo Rodriguez Garcia <[EMAIL PROTECTED]> writes:
Guillermo> Hello, I am a spanish user of Lyx 1.0.3. I am having the
Guillermo> following problem:
Guillermo> When using the Lyx-Code environment or the typewriter font,
Guillermo> all words starting with 'n' are converte
Hello,
I am a spanish user of Lyx 1.0.3. I am having the following problem:
When using the Lyx-Code environment or the typewriter font, all
words starting with 'n' are converted to 'ñ' (ntilde) in the PS
or DVI output. For example, the following line:
test = new Object();
will get automatica
Juergen Vigna <[EMAIL PROTECTED]> writes:
| It still aborts and the STL library does not so what, maybe it's time
| you send this pretty bad developers a mail to remember them to follow
| the standard #:O)
the STL library? what STL library?
Lgb
On 20-Oct-99 Lars Gullik Bjønnes wrote:
> Juergen Vigna <[EMAIL PROTECTED]> writes:
>
>| So the fix was not that wrong :), why not have the Assert only in
>| development versions?
>
> Yes it was that wrong! "shall not" under a requirements heading is
> pretty adamant.
* smile *
It still abor
On 20-Oct-99 Lars Gullik Bjønnes wrote:
> Juergen Vigna <[EMAIL PROTECTED]> writes:
>
>| Just to be curious, someone does compile lyx-devel with STL so that
>| lyxstring is not used? Could that person try to insert a lable in the
>| code from the menu Insert->Label and see what happens?
>
> You
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
|
| Lars> | cxx: Error: ../../../lyx-devel/src/support/lyxstring.h, line
| Lars> 539: | class "lyxstring::Srep" is inaccessible | return new
| Lars> Srep(sz, s);
|
| Lars> This one
Juergen Vigna <[EMAIL PROTECTED]> writes:
| Just to be curious, someone does compile lyx-devel with STL so that
| lyxstring is not used? Could that person try to insert a lable in the
| code from the menu Insert->Label and see what happens?
You mean if it should crash or not :-)
The standard us
On 20-Oct-99 Lars Gullik Bjønnes wrote:
> Juergen Vigna <[EMAIL PROTECTED]> writes:
>
>| Why, so only people knowing all C++ standards should touch the
>| lyx-code?
>
> No, only the part of the code that is written to follow a standard.
>
Just to be curious, someone does compile lyx-devel w
Juergen Vigna <[EMAIL PROTECTED]> writes:
| Why, so only people knowing all C++ standards should touch the
| lyx-code?
No, only the part of the code that is written to follow a standard.
Lgb
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> | cxx: Error: ../../../lyx-devel/src/support/lyxstring.h, line
Lars> 539: | class "lyxstring::Srep" is inaccessible | return new
Lars> Srep(sz, s);
Lars> This one I am not sure about, could you try with return new
Lars> lyxstr
On 20-Oct-99 Lars Gullik Bjønnes wrote:
>| If I would have know what means correctly for you, then yes, but I'm
>| no mindreader yet...
>
> A standard is a standard is a standard.
> (You dont change them you see...)
Why, so only people knowing all C++ standards should touch the lyx-code?
So I'
Juergen Vigna <[EMAIL PROTECTED]> writes:
| On 20-Oct-99 Lars Gullik Bjønnes wrote:
| >
| > If it was obvious I would. I got the impression that the bug was in
| > vspace.C, but a quick scan did not reveal it to me.
| > But you should have fixed the bug correctly...
| >
|
| If I would have kno
On 20-Oct-99 Lars Gullik Bjønnes wrote:
>
> If it was obvious I would. I got the impression that the bug was in
> vspace.C, but a quick scan did not reveal it to me.
> But you should have fixed the bug correctly...
>
If I would have know what means correctly for you, then yes, but I'm
no mindr
Juergen Vigna <[EMAIL PROTECTED]> writes:
| >>
| >> Lars> Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: |
| >> Lars> Juergen> if (s && *s) | | Juergen> I already did this so, ... ;)
| >> Lars> | | OK, it looks reasonable.
| >>
|
| It's ok to revert changes which are not optimal, but IMVO th
>>
>> Lars> Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: |
>> Lars> Juergen> if (s && *s) | | Juergen> I already did this so, ... ;)
>> Lars> | | OK, it looks reasonable.
>>
It's ok to revert changes which are not optimal, but IMVO that if you
revert changes which fix a bug then you should
On 19-Oct-99 Jean-Marc Lasgouttes wrote:
>> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
>
> Lars> Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: |
> Lars> Juergen> if (s && *s) | | Juergen> I already did this so, ... ;)
> Lars> | | OK, it looks reasonable.
>
> Lars> No, it d
25 matches
Mail list logo