I don't notice those conflicts in my implementation, but then again I'm not using Apple's text view. Every "normal" text field on the Mac (which I believe at l

I don't notice those conflicts in my implementation, but then again I'm not using Apple's text view. Every "normal" text field on the Mac (which I believe at least Apple's Terminal is using) has built-in Emacs-like bindings; I think that's why you see a conflict. I do have the concept of toggling context with macros; e.g. you can define up to 12 actions at a time, mapped to almost any key combinations, and choose between as many sets of 12 as you want. I also work around potential key mapping issues by having floating keypad windows. For example, if for some reason control-A doesn't work from the keyboard, it's always possible to "click" a button that will produce a control-A. (This was very useful in the old days in programs like "pine" that had redefined control-C among other things.)