On Thu, Jul 12, 2001 at 02:00:20PM +0200, Andre Poenitz wrote:
> ?? *- Mutation from inline formula to eqnarray generates a numbered eqnarray
>
> :: I can't reproduce this.
c-m m-m t e, and the result is a numbered eqnarray.
> ?? *- If I have macros \newcommand{\foo}[1]{[#1]} and \newcommand{\foox}{\foo{x}
> ?? then when an instance of \foox is drawn on screen,
> ?? there are two black frames
> ?? While this is "correct", it is annoying.
>
> :: I have removed the black frame around macros without argumments now. This
> :: should remove part of the annoyance
I actually have something like \newcommand{\foo}[1]{[#2]_{#2}} and
\newcommand{\foox}[1]{\foo{#1}{x}} so this change doesn't help.
> ?? - When creating a new macro instance (with one or more arguments),
> ?? typing a letter in the first argument, and typing backspace, the macro is
> ?? closed.
>
> :: I can't reproduce this.
Me too (with CVS of today).
> Misc:
>
> ?? *- 'ctrl-m x <escape> <left> shift+<left> x' crashes lyx.
>
> :: I can't reproduce this.
The crash occurs in MathArray::insert(int pos, byte b, MathTextCodes t)
when bf_.size() = 0 and pos = 3 (should the value of pos be 0?)
> ?? *- The height of the frame is often wrong (e.g. x^2)
>
> :: I can't reproduce this.
Try x^{2^2}
See also bug.png
> ?? *- Pressing backspace inside \sqrt{a} (when the cursor is after the a) will exit
> ?? from the root
>
> :: I can't reproduce this.
Me too.
bug.png
bug.png