X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-5.4 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RP_MATCHES_RCVD,SPF_NEUTRAL X-Spam-Check-By: sourceware.org Message-ID: <50C1076F.3000107@cornell.edu> Date: Thu, 06 Dec 2012 16:00:31 -0500 From: Ken Brown User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com CC: Daniel Colascione Subject: Re: Updated: emacs*-24.2.90-1 (TEST) References: <50C08983 DOT 8000806 AT cornell DOT edu> <87ip8f10hc DOT fsf AT Rainer DOT invalid> In-Reply-To: <87ip8f10hc.fsf@Rainer.invalid> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-CORNELL-SPAM-CHECKED: Pawpaw X-Original-Sender: kbrown AT cornell DOT edu - Thu Dec 6 16:01:13 2012 X-PMX-CORNELL-REASON: CU_White_List_Override 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 12/6/2012 1:47 PM, Achim Gratz wrote: > Ken Brown writes: >> emacs-w32 shouldn't require dbus-daemon, as far as I know. This >> sounds like a bug. Could you give me a specific recipe for >> reproducing the problem? > > Just make sure Cygwin has cleanly terminated, then open a mintty (I use > tcsh if that has a bearing on this bug) and start emacs-w32 from it. > Toggle the menu bar if it's not already on an select File->Open from it. > Open another mintty and try to kill the hanging emacs process from it. > Then use the task mamanger to really kill it and get a "broken pipe" > message in the second mintty. Now dbus-launch in the first mintty and > set the two environment variables (btw, here's another bug: if you > specify csh-style, you'll get the first one for csh alright, but the > second one is still in shell syntax). Start emacs-w32 again and observe > that you now get a functional W32 file open dialog. You can also kill > emacs from the second mintty with no ill effects (well, poor emacs dies, > but that's expected). I can reproduce this. (I use bash, so tcsh isn't the issue.) I'll see if I can debug it, but I'm copying Daniel in the hope that he gets to it first. I'm not sure about the dbus-launch issue, since I always use bash. But here's the output I get from `dbus-launch --csh-syntax': setenv DBUS_SESSION_BUS_ADDRESS 'unix:path=/tmp/dbus-wCGlBfQgo6,guid=f3e1dad82fc7ce9eff209b9300000000'; set DBUS_SESSION_BUS_PID=5020; What's the problem with that? As I understand csh syntax, the second line sets a variable but doesn't export it. Do you have some reason to think that's the wrong thing to do? If so, it's a D-bus issue and should be reported in a different thread. > >>> manager (the Gtk build will also hang up on you in a slightly different way >>> after you close the dialog box it has shown). I believe this is related to pipe >>> handling as you'll get messages about broken pipes sometimes. >> >> Again, please send a recipe for producing the problem with the Gtk build. > > Same thing as above, just with emacs-gtk, after having started > multiwindow X11 and setting DISPLAY environment in the shell. Unless > dbus is started and emacs can connect to it, emacs hangs up when you > cancel the file open dialog (obviously from Gtk). I don't see the issue here. I said in the release announcement that you need to have a D-Bus daemon running before starting emacs-X11 under X. > One other thing: how to tell this emacs apart from the Gtk build so that > I can switch the default font for each? I'm out of time right now, but I'll be able to answer this later. Just to make sure I understand, you want to be able to do this in your ~/.emacs, right? 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