On Tue, Mar 18, 2008 at 7:32 AM, Mark Ludwig <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
I can't seem to get Emacs 22 to sit up and perform the same way, and I
don't want all the command switching that I seem to be forced into if I
take EmacsW32. I just want "Edit with Emacs" and file associations to
work again. My Emacs 19/20 environment used gnuserv if I recall
correctly (the disk was dying after I got my user data off it).
I can get emacsclient/emacsserver to work for "Edit with Emacs" once
Emacs is running, but can't get it to start the first time. How do I do
this? Can EmacsW32 be configured to leave the keyboard alone? I know
it's confusing -- and even occasionally find myself scrolling forward
when I want to paste -- but I use Emacs on UNIX for work, too, so my
fingers mostly know the original key bindings.
EmacsW32+Emacs is a distrio built to make it easy to install and use
Emacs. There is absolutely no problem using the original Emacs key
bindings with that package. From the menus select
Options
Customize EmacsW32
With one click you switch it from original Emacs key bindings to those
are supposed to be more easy for people used to modern GUI applications.
And you do not have to fiddle with the registry to get Emacs client
working. Basic Emacs should work just out of the box after installing
EmacsW32+Emacs. (It comes with grep, find etc too, things you probably
will need after a while with Emacs.)
Actually there is one little thing to do after installation: Move the
file name e.cmd to somewhere in your path if you want to make it easy to
use Emacs/Emacs client from the command line.
(The solution to starting Emacs the first time using
emacsclient/emacsserver on UNIX leverages the ALTERNATE_EDITOR
environmental variable, a concept that does not exist on Windows, as far
as I know.)
Thanks!
Mark Ludwig
--
"I didn't care where Hemingway drank
or Alice B. Toklas had her moustache trimmed."
-- David Sedaris, touring Paris
