From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?utf-8?Q?=C3=93scar_Fuentes?= Newsgroups: gmane.emacs.help Subject: Re: starting the emacs daemon using init.org? Date: Mon, 20 Jul 2015 17:43:56 +0200 Message-ID: <87mvyqkf5v.fsf@wanadoo.es> References: <87twszc33d.fsf@skimble.plus.com> <20150720030113.26599.064FD903@ahiker.mooo.com> <87si8j9ilu.fsf@skimble.plus.com> <20150720141949.29127.22A5CE72@ahiker.mooo.com> <1437404084.2071.224.camel@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1437407078 15996 80.91.229.3 (20 Jul 2015 15:44:38 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 20 Jul 2015 15:44:38 +0000 (UTC) Cc: Paul Smith To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon Jul 20 17:44:29 2015 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZHDEy-0005Am-OP for geh-help-gnu-emacs@m.gmane.org; Mon, 20 Jul 2015 17:44:28 +0200 Original-Received: from localhost ([::1]:55946 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZHDEx-0003Jt-U3 for geh-help-gnu-emacs@m.gmane.org; Mon, 20 Jul 2015 11:44:27 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45657) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZHDEj-0003Jn-TC for help-gnu-emacs@gnu.org; Mon, 20 Jul 2015 11:44:17 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZHDEf-00066L-Rr for help-gnu-emacs@gnu.org; Mon, 20 Jul 2015 11:44:13 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:55745) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZHDEf-00063j-Lj for help-gnu-emacs@gnu.org; Mon, 20 Jul 2015 11:44:09 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1ZHDEc-0004zQ-Kv for help-gnu-emacs@gnu.org; Mon, 20 Jul 2015 17:44:06 +0200 Original-Received: from 254.red-83-46-124.dynamicip.rima-tde.net ([83.46.124.254]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 20 Jul 2015 17:44:06 +0200 Original-Received: from ofv by 254.red-83-46-124.dynamicip.rima-tde.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 20 Jul 2015 17:44:06 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 42 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 254.red-83-46-124.dynamicip.rima-tde.net User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) Cancel-Lock: sha1:ujs1JEMvsripjoOLq0dmqTPAODo= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:105877 Archived-At: Paul Smith writes: > On Mon, 2015-07-20 at 07:30 -0700, Ian Zimmerman wrote: >> But really, I can honestly say I have _never_ seen Emacs crash. A few >> times it went into an infinite spin because a package did something >> dirty, mostly involving an external process. But crash, never. > > It crashes on me sometimes. Maybe once every month or two, I'll find it > disappeared and a core file sitting in my home directory. Also > sometimes Emacs gets into weird states with font-lock and indentation in > my code (mostly C++) and I need to restart it to clear it up. Other > than that I never restart it unless I need to reboot my system. > > But I have an interesting use-case: > > * I run emacs --daemon as part of my login process. > * I run a GNOME desktop and use the GTK-enabled Emacs. > * At work I create X window frames using emacsclient. > * When at home I ssh to my work system in a (big) xterm and use > emacsclient to attach to the daemon and create text frames, > rather than sending X remotely (our VPN is not super-speedy and > I type pretty fast :)). > > I have a feeling that using both X and non-X frames in the same Emacs is > not as well-tested and may have corner-case issues. Most likely your setup triggers a well-known bug. It is mentioned on a message on the terminal when emacs --daemon is started and in PROBLEMS (`Help' menu -> `Emacs Known Problems'): ** When Emacs is compiled with Gtk+, closing a display kills Emacs. There is a long-standing bug in GTK that prevents it from recovering from disconnects: http://bugzilla.gnome.org/show_bug.cgi?id=85715. Thus, for instance, when Emacs is run as a server on a text terminal, and an X frame is created, and the X server for that frame crashes or exits unexpectedly, Emacs must exit to prevent a GTK error that would result in an endless loop. If you need Emacs to be able to recover from closing displays, compile it with the Lucid toolkit instead of GTK.