3 ms·
The emacs option-as-meta experience is terrible. Luckily, it's easy to change: (setq mac-option-key-is-meta nil) (setq mac-command-key-is-meta t)
by msbarnett 14y ago
The emacs option-as-meta experience is terrible. Luckily, it's easy to change:
(setq mac-option-key-is-meta nil)
(setq mac-command-key-is-meta t)
(setq mac-command-modifier 'meta)
(setq mac-option-modifier nil)
- __david__ 14y agoActually, those are the old Carbon Emacs settings. The new Cocoa ones are like this: (setq ns-alternate-modifier 'meta) (setq ns-command-modifier 'super) (setq ns-control-modifier 'control) Better yet, use the customization interface to configure them: "M-x customize-group RET ns RET"
- msbarnett 14y agoHuh, interestingly the old Carbon settings still seem to function, although the Cocoa versions certainly look cleaner. > Better yet, use the customization interface to configure them: "M-x customize-group RET ns RET" Ugh. I can't be the only person that hates the Custom interface with the firey passion of a thousand suns, can I? Far better to just define things cleanly in your init.el than to do it all in that obtuse UI and create enormous ;DO NOT TOUCH custom-set-variable forms.
- __david__ 14y agoI actually like the customize interface. That's not to say it couldn't be better. Something about it is very..... ugly. I think native widgets would go a long way to making it look like someone other than a programmer designed it. That being said, it fits the Emacs cross platform philosophy and it's a uniform way to look at settings, change them and get help on them and save them in your .emacs. At some point I went and changed all my random "setq"s in my .emacs (built up over 10 or so years) to the equivalent customize versions and as a result was able to speed up my Emacs boot time by a significant amount (like 8ish seconds down to 2ish). The nice thing about customized variables is that you don't have to load in a mode to set it's variables (loading a bunch of modes during boot was what the slow part was).