X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.4 required=5.0	tests=AWL,BAYES_50,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_HELO_PASS
X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Achim Gratz <Stromeko AT nexgo DOT de>
Subject: Re: Updated: emacs*-24.2.90-1 (TEST)
Date: Thu, 06 Dec 2012 19:47:43 +0100
Lines: 53
Message-ID: <87ip8f10hc.fsf@Rainer.invalid>
References: <announce DOT 50BB4D0D DOT 7010204 AT cornell DOT edu>	<loom DOT 20121203T102613-270 AT post DOT gmane DOT org>	<loom DOT 20121206T085349-191 AT post DOT gmane DOT org>	<50C08983 DOT 8000806 AT cornell DOT edu>
Mime-Version: 1.0
Content-Type: text/plain
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2.90 (gnu/linux)
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

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).

>> 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).

> If it turns out to be necessary, which I doubt, you can simply put the
> following in your .bashrc (assuming you use bash as your shell):
>
> if [ -z "$DBUS_SESSION_BUS_ADDRESS" ] ; then
>     eval `dbus-launch --sh-syntax`
> fi

I don't normally, and the real problem will be shortcuts that so far
fired up a mintty with emacs-nox in it.  I was hoping they could simply
start emacs-w32, but I'll have to figure out how not to start a new dbus
session for each of them when it turns out that this is necessary (I
still hope it's not).

One other thing: how to tell this emacs apart from the Gtk build so that
I can switch the default font for each?


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada


--
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