X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_NUMERIC_HELO,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Achim Gratz Subject: Re: Updated: emacs*-24.2.90-1 (TEST) Date: Fri, 7 Dec 2012 07:47:13 +0000 (UTC) Lines: 31 Message-ID: References: <50C08983 DOT 8000806 AT cornell DOT edu> <87ip8f10hc DOT fsf AT Rainer DOT invalid> <50C1076F DOT 3000107 AT cornell DOT edu> <877gou980c DOT fsf AT Rainer DOT invalid> <50C14F06 DOT 8090804 AT cornell DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) 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 Ken Brown cornell.edu> writes: > Emacs will *try* to autolaunch a D-Bus session if it doesn't find one, > but this feature is broken in the emacs-24 branch (and the problem is > not Cygwin-specific). This is Emacs bug #8855. It's been fixed in the > trunk, but the fix is complicated and probably won't be backported to > the emacs-24 branch. OK, that explains why I don't see it on Linux, I'm currently using trunk there. > I didn't want to complicate the release > announcement by giving all this information; I thought it would be > enough to say, "... you should have a D-Bus session daemon running > before starting emacs under X11." Understood. s/should/must/ BTW, as noted elsewhere in the thread, the hang was apparently triggered by the attempt to use an X11 font in the W32 build via custom-set-faces (due to the fact that both builds used the same .emacs and customization), so it does not happen with emacs -Q. In fact, I've not been able to even try using that font any other way so far, both "--font" and "--eval '(set-default-font" correctly refuse to use this undefined font. Why it manages to bypass that guard when invoked via custom-set-faces I need to check again. Regards, Achim. -- 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