[Aquamacs-devel] Aquamacs 2.0: slow start, Japanese fonts, Kotoeri, visual line

[Jose Figueroa-O'Farrill]

Hi,

I have started using Aquamacs 2.0 and I find the following main problems.  All this is without customizations.

1) it takes an inordinate amount of time to start up.  If I simply launch it from the Dock then no windows appear (at least for 1 minute) until I click on the dock icon  again (but not before waiting for about 30 seconds) and then I get a number of windows: the scratch buffer and N windows where N is the number of times I click on the dock icon.  [This is on a relatively new Unibody MacBook Pro 17" with 4Gb of RAM running 10.5.8.  I will be upgrading to 10.6 as soon as my wife returns from Edinburgh with the DVD :) ]

I have isolated the problem to my Preferences.el file and I suppose I could try to narrow it down further by taking chunks of it at a time.  I'll do that later if I have the time.  However, if I hide the Preferences.el file so that it is not found at start up then it starts up reasonably quickly; although not as quickly as Aquamacs 1.8.  If I then load the hidden Preference.el file, it loads immediately and without any appreciable delay.  So I don't know what the problem is.

2) There is a problem with Japanese fonts -- this has been remarked by Jean-Christophe previously.  The kana characters are nice and antialiased, but the kanji characters are scraggly and almost unreadable.  How was this problem sorted (if it was) in the end?

3) Aquamacs seems to trap the standard Kotoeri keyboard shortcuts.  I switch input system between latin and japanese by Control-Shift-J and Control-Shift-; but these no longer work because Aquamacs does not distinguish between Ctrl-Shift-J and Ctrl-J.  Neither does Ctrl-Shift-; work with Aquamacs claiming that "^: is undefined."

4) C-p and C-n are now bound to aquamacs-*-nonvisual-line.  Is this intentional?  It seems that it's the arrow keys which now behave visually.  However this is not consistent with the bindings for C-a and C-e which just like Option-arrows behave visually.
Anyway, I would think that if is a lot more ergonomic to to set the C-a,C-e,C-p,C-n according to the value of visual-line-mode.  If someone bothers to set visual-line-mode to 't' is because one wants to work with visual lines, in which case the the usual emacs keys for operating on lines should behave visually as well, right?  Anyway, that's easy enough to take care of via the Preferences/Customisations.  I just point it out in case it was not intentional.    And at any rate, I think that the default keybindings are inconsistent as they stand.

More later,

José


-- 
Professor José Miguel Figueroa-O'Farrill 
Institute for the Physics and Mathematics of the Universe
University of Tokyo, Kashiwa, Chiba, Japan
Phone: +81-4-7136-4958 and Skype: josemiguelfigueroa
Web: http://www.maths.ed.ac.uk/~jmf
Blog: http://empg.maths.ed.ac.uk/blog