[ANNOUNCEMENT] Updated: emacs*-24.2.93-2 (TEST)

Ken Brown kbrown@cornell.edu
Thu Feb 21 11:22:00 GMT 2013

On 2/21/2013 4:42 AM, Achim Gratz wrote:
> Arthur Tu <arthur.jim.tu <at> gmail.com> writes:
>> I use only the w32 interface for frame display and I haven't install
>> emacs-x11. After a daemon is started, "emacsclient -c" invokes a w32
>> frame, while "emacsclient [-n]" gets a terminal session. I feel great
>> about this.
>> Your problem may be caused by the priority of "x11" and "w32".
> The problem is that emacsclient-w32 does simply try to call "emacs", which  (via
> /etc/alternatives) links to emacs-X11 on my system and to emacs-w32 on yours.
> Since the two emacsclients for X11 and w32 should not mix, they should probably
> call emacs-X11 and emacs-w32 directly and not use /etc/alternatives.

I think the alternatives system should work fine for most users.

The problem you've described occurs only in the following situation:

1. You install both emacs-X11 and emacs-w32.

2. You start an emacs server and connect to it via

        emacsclient-w32 -a ''

instead of

        emacsclient-w32 -a emacs-w32

It's true that I could patch emacsclient-w32 to call emacs-w32 when it's 
given the option "-a ''", but I prefer to avoid Cygwin-specific patches 
that would not be acceptable upstream.  In this case, the patch would 
mess up people who build their own emacs using --with-w32.


Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

More information about the Cygwin mailing list