DanP> The new PSGML mode has, in it's keymap, one stunningly counter-intuitive DanP> binding[1]. I agree completely. Ray> I have the same problem. I hate it. I want M-backspace (in Ray> Fortran mode at least) to kill word just like it does everywhere Ray> else! (But perhaps this is a bug created when the great Ray> Backspace vs Delete change took place and Fortran was forgotten? Ray> I know that Fortran mode used to work correctly.) Proof that different users want different things. XEmacs thinks BS is BS, whereas FSF Emacs thinks BS is DEL? Still, for any particular user preference, XEmacs should work consistently, so there is a bug here. DanH> I don't know if it's a bug or a feature - but this is all because DanH> XEmacs works differently from fsfmacs. Fortran-mode etc all define DanH> "\e\C-h" in a local keymap, which on XEmacs overrides both M-backspace DanH> and C-M-h. On fsfmacs it only overrides C-M-h (the intended DanH> behaviour). But FSF Emacs redefines Meta+Backspace if you do (global-set-key "\e\C-?" 'backward-char) so XEmacs is consistent at the _syntactic_ level. It merely disagrees on the name of the key labelled "BackSpace" (on my computer). DanH> That means that you have to re-assign backward-kill-word explicitly to DanH> M-BS if you also define C-M-h. I vote for someone working with the package maintainers to modify the key bindings for psgml-mode. They can probably be (compatibly!) changed to (define-key sgml-mode-map [(meta control h)] 'sgml-mark-current-element) Daniel, could you verify that this kind of change is safe for XEmacs and Emacs, search for other such changes (some suggested in this thread), communicate with the other package maintainers, but make the changes in XEmacs in any case? It requires a certain amount of development discipline and documentation, but I think the use of `CVS vendor branches' can allow us to safely modify upstream packages and maintain those changes with upgrades. We have to have a clear plan for how those vendor branches should work and what naming convention to use for them. The key binding code in XEmacs could use a lot of work. An interesting project for someone who has time (perhaps me, in a future life). Martin