X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-3.8 required=5.0 tests=AWL,BAYES_00,KHOP_SPAMHAUS_DROP,KHOP_THREADED,RCVD_IN_HOSTKARMA_NO,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org X-CornellRouted: This message has been Routed already. Message-ID: <51260347.4010501@cornell.edu> Date: Thu, 21 Feb 2013 06:21:43 -0500 From: Ken Brown User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: [ANNOUNCEMENT] Updated: emacs*-24.2.93-2 (TEST) References: <5124C565 DOT 7000206 AT cornell DOT edu> <5125DFAA DOT 6040104 AT gmail DOT com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 2/21/2013 4:42 AM, Achim Gratz wrote: > Arthur Tu 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. Ken -- 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