On 13-Jul-2000 Lars Gullik Bjønnes wrote:
> Juergen Vigna <[EMAIL PROTECTED]> writes:
>
>| The real problem was that bibitem is a subclass of insetcommand AND
>| insetcommand USES [begin|end]_inset, so I added (because otherwise it
>| gives bugs) the reading of the \end_inset in the Read() routine of
>| insetcommand, but as the subclass does not have the \end_inset this
>| gave the error, so it was just some inconsistency in 1 inset-class!
>
> Ok, so now the warning from buffer about a \end_inset without a
> \begin_inset should be enabled, and would really flag a problem?
>
No only if the inset is inside a text-inset, but how can you be sure
that this isn't the case? So our rule should be:
If there is a \begin_inset the inset HAS to read it's own \end_inset!!!
Jürgen
--
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
Dr. Jürgen Vigna E-Mail: [EMAIL PROTECTED]
Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450296
I-39100 Bozen Web: http://www.sad.it/~jug
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
How come everyone's going so slow if it's called rush hour?
