Georg Baum wrote:
>> Sounds like the inset scheme is still a bit too complex if copy &
>> paste introduces errors... Why is an inset supposed to read the
>> \end_inset token? Isn't that 'data belonging to a level above'?
>
> I would think so. But nevertheless, adding something like the
> following in InsetVSpace::read() (stolen from insettext.C)
>
> + if (lex.isOK())
> + lex.next();
> + if (lex.getString() != "\\end_inset") {
> + lex.printError("Missing \\end_inset at this point. "
> + "Read: `$$Token'");
> + }
>
> makes it work.
Cheers, Georg. Applied, although I suspect that someone will now try
and factorize all these pieces of code handling 'end_inset'...
--
Angus
