Am 29.09.2007 um 09:03 schrieb Adrian Robert:
>
> Not sure about the ns-list-command-keys, but there were a lot of lisp
> changes going rc1 -> rc2 (not just in Emacs.app) so I would not expect
> rc1's lisp to work.
It seems to happen when (any ?) Emacs version is launched from its
build directory. The X client does not read the site init file
outside the usual load-path, and Emacs.app does not read from inside
its application bundle which, too, is outside the usual. The "big" or
complete/self-contained Emacs.app (bundle), when in /Applications,
works well without any comments.
>
> As far as the blue fringe, can you send a screenshot?
The protrusion of the fringes in the second (lower) window into the
tabbar area does not always happen! It was the default with RC1, but
then the marks in the fringes where black (not according to settings)
and did not behave like the ever hungry Pacman. I can provoke it when
in the lower window calendar is running and I scroll through the
year. Then this wndow's size changes because because months can be
four, five, or six lines high. In American format this year's
September and December are six lines, and when I change to a three
months view with months of four or five lines the invasion of the
fringes happens, i.e. computing the window's new size and the
fringes' new size happens differently.
It never happens with the upper (top-most) window, even when it's the
*Calendar*. When I scroll through the year and the size changes, then
again the lower window is effected.
With three windows and the top-most is *Calendar*, then only the next
window below is an invader. When I make *Calendar* the second
(middle) window and I scroll, than this window and the one below
invade the tabbar.
Something somehow related to this happens when Emacs.app initialises
itself at start-up time. The a lot of text is written into echo-area.
For some time echo-area is high enough to write the messages in the
"default font," which is not used (the font used is one from the
fontset as recorded in the preferences or such), and then the fringes
protrude the mode-line. So this could be two bugs: assumptions based
on the wrong font (height of echo-area), and the penetrating fringes.
>
> Also, are you able to compile an X client from this or does the
> recursive copy-directory bug mentioned on sourceforge still exist?
This is solved, no directory @ns_appdir@ was created.
There is a new (old ?) bug in the complete Emacs.app: it does load
the site init file! Because it's now supposed to be in the bundle and
not in the first element of load-path, /Library/Application Support/
Emacs ...
--
Greetings
Pete
There are two major products that come out of Berkeley: LSD and UNIX.
We don't believe this to be a coincidence.
- Jeremy S. Anderson
-------------------------------------------------------------------------
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-
