> Yeah, any editor that requires you to reach over to the other side of
> the keyboard just to move the cursor...well, that's just bad. And the
> keys that MS DOES choose to map to control-keys...again, not well
> thought out.
I despise the "arrow-key/notepad" mode in so many Windows apps (more so
when you cannot change it). I also hate that the ALT key is sticky. Do you
remember years ago how the function keys used to be over on the left, and
you could use them fairly easily with one hand, even with ctrl/shift/alt
modifiers? That's another thing I miss.
If you're using Emacs keystrokes, it certainly helps to map the CapsLock
key to Ctrl. I use Ctrl2Cap from www.sysinternals.com for that.
> I know what you mean about changing between editors. I can use Emacs
> keystrokes just about anywere *except* in VS.NET. It's tough to
> remember to switch modes when going back to the retarded MS editor.
Yes, no doubt about it. I regularly screw-up and start using Emacs keys in
VS.NET or vice-versa, especially when I am going back and forth one to the
other. You would think I'd make Emacs and my VS.NET keystrokes compatibile,
but honestly I don't like the Emacs keystrokes much, they don't seem to
have been for rapid typing. And changing them in Emacs seems like too much
to take on, since almost all packages assume you are using the standard
keys.
> Anyway, I'd love to know why MS dropped Epsilon/Emacs mappings, and I
> was hoping to hear they would be added in again. Yes, I could write a
> bunch of key bindings, but surely someone must have done this already.
> Right?
I can only guess as to why they dropped it. One guess might be that they
felt that if it wasn't a complete (or near-complete) emulation, it would
look bad to advertise it as such, only to have real Emacs users
disappointed. I know they are interested in having more of the Open Source
people adopt Visual Studio for their primary development tool. They also
know that issues such as the one you brought up will be a barrier for
people who have used Emacs/Emacs-compatible editors. I've discussed this
exact point with some of the Program Managers on the VC++ team.
I may play with setting up some Emacs keys in VS.NET, if I have some free
time, although as I mentioned above, I don't want to use them as my primary
editing keystroke set.

Signature
harry