My quick fix to this was to
- write a bat file,
runemacsclientw.bat
much like the example on the EmacsWiki to start emacsclientw.exe, - convert the bat file to exe with a simple converter,
- choosed the above bat file as batch file,
- checked Invisible application (don't know if this matters...),
- under the Versioninformation tab picked an Emacs icon file from under the
etc/icons
path, - compiled, and exited,
- fix read/execute permissions for the users group on the new exe file,
runemacsclientw.exe
, placed in the emacsbin
directory - associate file types to be opened by Emacs with
runemacsclientw.exe
, and - add
(server-start)
to the Emacs init file,.emacs
runemacsclientw.exe
on the taskbar and defined an alias, emacs
, for runemacsclientw.exe
in my .bashrc
. I run cygwin/bash on my Windows boxes.
Why not just use emacsclientw.exe directly? What does the .bat file add?
ReplyDeleteUsing emacsclientw.exe directly does indeed solve his stated problem. On the other hand, a bat file adds something: passing some arguments automatically. The linked batch file for example adds --no-wait and --alternate-editor which you would want to pass to emacsclient most of the times. This is why also on Linux desktops, many users resort to a bash script or a desktop file that in turn calls emacsclient.
DeleteNo Use, it just start a new emacs process not client with two window frames.
ReplyDeleteIf you use emacsclientw.exe it will be:
Emacsclient ERROR
No socket or alternate editor...
This fixed it in my case (HOME not correctly defined before emacsclientw gets executed):
Deletehttp://lists.gnu.org/archive/html/help-gnu-emacs/2007-09/msg00675.html
This comment has been removed by a blog administrator.
ReplyDeleteGreat and I have a super supply: Whole House Remodel Cost kitchen remodel companies near me
ReplyDelete