Am 20.09.2007 um 15:55 schrieb Adrian Robert:

> In addition, this release is not as heavily tested as rc2, but
> hopefully the bug-fix emphasis means it will be more stable.

I've found another bug: ⇧⌥8, or, as Peter Maurer's Key Code 1.0  
sees it, ⇧⌥( produces ``~´´ (126, #o176, #x7e, TILDE) instead of  
``˜´´ (732, #o1334, #x2dc, SMALL TILDE). German PowerBook G4  
keyboard. ~ is usually ⌥N + SPC following, i.e. a dead key that can  
compose accented characters.

A bit more from Key Code:

Unicode:        732 / 0x2dc
Keys:           ⇧⌥(
Key Code:       28 / 0x1c
Modifiers:      655650 / 0xa0122


One more information on fringes protrusion: it also happens when I  
launch Emacs.app and the cursor is from the start in *Calendar* on  
today's date. When I then change to another window (*temp* window  
with date and solar data), then echo-area/mini-buffer grows as if  
another font in it gets temporarily active (as during Emacs.app  
initialisation) and *Calendar*'s /left/ fringe only protrudes into  
the tabbar area. Mini-buffer shrinks in height back when I input  
anything, which also can create a *Backtrace* buffer with a  
protruding left fringe.

I never watched the right fringe, but applying the tests again and  
watching the right one now, I can see that it fits always. The  
misbehaviour *can be* due to computations to indicate empty space in  
the buffer ...

Doing one more comparison I can see that a self-contained Emacs.app  
bundle shows during its initialisation phase a mini-buffer/echo-area  
of normal height with a left fringe that protrudes tabbar. So it  
behaves differently than my usual "lean" app. When both are launched  
with -Q and no fringe gets "decorated" then no fringe protrudes  
anything. Using just -q my lean app shows, when entering the first  
command, a too high mini-buffer. The complete bundle shows for a  
short period a protruding left finge in an echo-area of normal  
height. Then the fringe's length is corrected. This behaviour is  
similar to that of the X client when launched with -q: its echo-area  
is initially too high. (GNU Emacs 23.0.50 seems to behave  
differently, while version 22.1.50 is closer to 23.0.0 – I should  
make some more tests while compiling X11R7.2 so see things in slow- 
motion!) I'll prepare some more tests some time later, today or this  
week with loading some Elisp code to "decorate" the fringes, load and  
invoke tabbar, set and load calendar ...


The new NS-Elisp code makes Emacs.app RC1 crash ...

--
Greetings

   Pete

Wasting time is an important part of living.



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Emacs-app-dev- mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emacs-app-dev-

Reply via email to