David Reitter replied to my post griping about Aquamacs.
Re 1.3: these are Emacs limitations; we’re working on them.
Perhaps it wasn’t such a good idea to put out a press release for a major feature if there are serious known limitations. It’s a cool feature, but it’s not release quality.
Re 1.4: Other modes do NOT use Command-{/} because Command (mapped to A- in Aquamacs) is not a traditional Emacs modifier key. If you do something unwise like mapping it manually to Meta, then of course you’re on your own…
I take issue with the characterization that using command as meta is “unwise.” I am, after all, using the mechanism you yourself put in place (M-x customize-variable RET mac-command-modifier RET), which contains no mention of it being “unwise” or otherwise problematic. But I grant that this is more of a problem with my setup. I learned early on that Meta is the key to the left of space, whatever the label on it happens to be, and I find that much more palatable then stretching for the smaller Option/Alt key.
Re 3: You need a Lisp interpreter installed if you want to use common lisp. The correct way to run Emacs Lisp stuff is M-x lisp-interaction-mode or M-x emacs-lisp-mode.
Emacs is a lisp interpreter. I don’t want to use CL, I want to write, tweak, and eval Emacs lisp in a buffer. This may be my inner curmudgeon at work; lisp-mode used to do this, but perhaps that has changed to emacs-lisp-mode.
Re 4: Have you reported the bug? It won’t get fixed if it isn’t reported, and this is a problem in GNU Emacs (and not just Aquamacs specifically).
I sent a near-identical list of issues directly to David. I’m unable to participate in the Aquamacs mailing lists (including aquamacs-bugs) because any email is bounced due to my email domain lacking a “postmaster” address. I have no control over how my email is run, so this isn’t something I can fix. David said that “bugs should be non-restrictive… I’m looking into it.” Thus far, it has not been changed.
Discussion