X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-3.8 required=5.0	tests=AWL,BAYES_00,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 22:51:11 +0100
Lines: 41
Message-ID: <8738zi97e8.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> <87ip8f10hc DOT fsf AT Rainer DOT invalid>	<50C1076F DOT 3000107 AT cornell DOT edu> <50C10D43 DOT 2070804 AT dancol DOT org>
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

Daniel Colascione writes:
>>> Open another mintty and try to kill the hanging emacs process from it.
>
> Works fine for me, albeit using kill -9, not regular kill. What
> exactly do you see?

The kill command (with -KILL or any other signal) never returns until I
terminate emacs from task manager.  I then often see some error message
about "broken pipe" in the mintty that issued the kill, presumably from
a failed attempt to connect to a dbus session via pipes.

> According to a message upthread, Emacs hangs hard
> any time you try to open a dialog box. Can you please attach gdb to
> Emacs when it's in this state and get a backtrace?

Will try later, I can't promise when I get to it.

Here's one other thing I forgot to mention: this emacs shows up in the
task pane with a generic icon, not as Emacs.

> If these problems persist, my first instinct would be to not support
> dbus in cygw32 builds of Emacs. People mostly use dbus to integrate
> components of a Unixish desktop environment, and I imagine users of
> cygw32 want to use Cygwin Emacs as part of a Windowsish desktop
> environment, which uses USER32 facilities to do what other
> environments do with dbus.

Turning the tables: what is dbus integration useful for in that build?
If it isn't something really compelling, then I'd think it should be
left out since this emacs will be most useful when no X session has been
started (and hence most likely no dbus either).  At least that is what I
am going to do.


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

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
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