[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [h-e-w] EMACSW32 and Windows 7 Win+Arrow Shortcuts

From: Gary Oberbrunner
Subject: Re: [h-e-w] EMACSW32 and Windows 7 Win+Arrow Shortcuts
Date: Tue, 08 May 2012 12:34:00 -0400 (EDT)

----- Original Message -----
> From: "Drew Adams" <address@hidden>
> > I admit the shortcut thing should not irk me as
> > much as it does, but there are too many options for me to
> > always remember, and at least in the old days, it was hard to
> > get exactly right and -a didn't work so you had to write a
> > little .bat file and use that.  ...
> I understand.  But you probably only have to learn _once_ what it is
> that you
> want, and then just repeat that each time afterward.  If you always
> use the same
> thing then there is only one thing to remember.
> And if you always use the same thing then you can just update your
> existing shortcut to point to the new binary location.
> And if the location does not change (e.g. you need only one build)
> then you need
> not do ANYTHING more than unzip the new zip file to the same location
> - your shortcut need not change at all.

Yeah, I should just get over it -- as long as newish builds actually work, 
which it sounds like they do (-a is said to work properly now, and probably the 
exit status thing is fine).

So, emacs Windows wizards, is the best Emacs shortcut for Windows now just 
"emacsclient -na emacs"?  Or is it "emacsclientw -na runemacs"?

BTW, the Emacs wiki still suggests 
writing a bat file containing "emacsclientw -na runemacs.exe %1" -- from this 
discussion, I presume that level of indirection is no longer needed.  That 
discussion is also scarily confusing even to me, a seasoned Windows and Linux 

Note that if you like to associate file types with emacs, like .txt and so on, 
each of those is a separate registry command, so if you move your emacs, you 
have to adjust all of them.  Or write a bat script and use that.  At least I 
think this is true.  I always keep my emacs in the same place: c:\Program Files 
(x86)\Emacs\Emacs.  Old versions go in C:\Program Files 
(x86)\Emacs\Emacs-24.0.91 and so on.  That way they all automatically read my 
site-lisp which I keep in c:\Program Files (x86)\Emacs\site-lisp.

> > I admit that although I've been using Emacs since 1982,
> > submitted patches, and written thousands of lines of elisp,
> > I'm at the point now where I just want it to work without
> > fuss on a new machine - my focus is elsewhere.  Guess I'm
> > getting lazy. :-)
> Again, I'm with you.  But you might have fewer surprises by sticking
> with a vanilla GNU Emacs build.  Just a suggestion.

You're right -- and I have been running vanilla builds for the last year or so, 
since I switched away from W32Emacs.  But I admit I'm still running the special 
W32-patched emacsclient as my main way of starting emacs.  I should wean myself 
away from that and start fresh.

> ... Or maybe addpm.exe could create it.
> Use `M-x report-emacs-bug' to offer such suggestions to the Emacs
> developers.
> That command is for enhancement requests in addition to bug reports.

Good point.  Of course I know how much the Emacs community *loves* to work on 
Windows features. :-) But you're right, if I don't ask then it certainly won't 

Gary Oberbrunner

reply via email to

[Prev in Thread] Current Thread [Next in Thread]