> It would certainly be nice if Emacs came with a decent set of > registry keys and start menu shortcuts so that it (client) > would _just work_ without hand-editing registry or creating > start menu shortcuts. > > If your code can be run after unpacking a standard nightly > build on a fresh machine and it finishes setting up Emacs, > I bet a lot of people would use it. For me at least, that > integration was the biggest draw of W32Emacs over stock.
FWIW, that messing with the registry etc. is a main reason that I would *not* use EmacsW32. (Note: I am not saying that anyone else should not use it. I'm very glad that Lennart has made EmacsW32 available.) I have multiple versions of Emacs on my laptop. It is trivial to create a shortcut to any of them that I want to start with just a click. And none of them takes precedence over any others (registry settings etc.). I never touch the registry for Emacs (what for?). And a shortcut need not be related to the Start menu, BTW. You can put a shortcut anywhere. What's the big deal about creating a shortcut? Why is that harder than running some "installer"? I find unzipping and (optionally) creating a shortcut sans effort and sans surprises - painless. So much so that I sometimes have more than one shortcut to the same binary, with different startup switches etc. YMMV - just one user experience.
