On 10 Sep 2001, Lars Gullik [iso-8859-1] Bjønnes wrote:
> Michael Schmitt <[EMAIL PROTECTED]> writes:
>
> | - Text in an ERT should be handled verbatim, i.e. double spaces should not
> | be removed automatically
>
> I'd hate to special case this. I'd like to have a InsetVerbatim for
> this instead.
I can imagine that it is relevant whether a latex command includes
some additional spaces or not. But Jean Marc has requested this. Maybe he
can motivate it a bit more?
> | - Minibuffer message is duplicated:
> |
> | "LaTeX run number 2 (message LaTeX run number 2)"
>
> Is it _really_ a problem?
Well, I would like to work with a tool that has a nice GUI! From a
developer's point of view this is neglectable, of course, but from a
user's point of view LyX definitely needs some polishing (don't kill me
but sometimes it looks a little bit "self-made").
> | - Two memory leaks (among others)
> |
> | MLK: 6568 bytes leaked in 20 blocks
> | This memory was allocated from:
> | malloc [rtlib.o]
> | vector<char,allocator<char>>::operator =(const
> | vector<char,allocator<char>>&) [stl_alloc.h:157]
>
> so this leak seems to be in the vector really...
> does this happen for all vectors or just this?
I send you just the bigger memory leaks (>1Kb). Whether
_all_ vectors leak is a question that I cannot answer.
> | MLK: 512 bytes leaked at 0xa1ab50
> | This memory was allocated from:
> | malloc [rtlib.o]
> | vector<char,allocator<char>>::_M_insert_aux(char*,const char&)
>[stl_alloc.h:157]
>
> Hmm, when are you notified of these leaks? During program run, or when
> you exit lyx?
Normally, I look for memory leaks _before_ I exit LyX (_real_ mem leaks).
I would expect this also for the problem above but I cannot guarantee it.
> | Then move the cursor in front of the note, press CursorDown (you are now
> | scrolling past the note), press CursorUp (you are back in front of the note),
> | and press CursorLeft -> you enter the note but again the document is scrolled,
> | this time totally unnecessarily. Too much scrolling is really confusing!
>
> Not exactly what note was intended for...
> this is more a general problem with large insets.
Yes, the problem can be generalized. Large insets are problematic.
> | - Characters with Sans Serif font are bigger (on screen) than characters
> | with Roman font (even though their actual size is equal)
>
> what "actual size", this depend upon how the font creator created
> them. (so really this is "not-our-bug")
Very well. It is so good that we have spoken about this problem :-) Gone
to trash folder...!
Michael
--
======================================================================
Michael Schmitt phone: +49 451 500 3725
Institute for Telematics secretary: +49 451 500 3721
Medical University of Luebeck fax: +49 451 500 3722
Ratzeburger Allee 160 eMail: [EMAIL PROTECTED]
D-23538 Luebeck, Germany WWW: http://www.itm.mu-luebeck.de
======================================================================
