From: Sharon Kimble <boudiccas@skimble.plus.com>
To: Rusi <rustompmody@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: starting the emacs daemon using init.org?
Date: Mon, 20 Jul 2015 20:23:02 +0100 [thread overview]
Message-ID: <874mky3a7d.fsf@skimble.plus.com> (raw)
In-Reply-To: <ff3dddc6-6dac-4777-89ac-fc7d42cbebf3@googlegroups.com> (Rusi's message of "Mon, 20 Jul 2015 05:57:16 -0700 (PDT)")
[-- Attachment #1: Type: text/plain, Size: 1161 bytes --]
Rusi <rustompmody@gmail.com> writes:
> On Monday, July 20, 2015 at 6:12:31 PM UTC+5:30, Barry Fishman wrote:
>> On 2015-07-20 12:28:26 +0100, Sharon Kimble wrote:
>> > Emanuel Berg writes:
>> >> Sharon Kimble writes:
>> >>
>> >>> I've been thinking about running emacs as a daemon
>> >>> to quicken my loadup times and also able to recover
>> >>> quickly when emacs crashes and restarts. But how?
>> >> 1. Does your Emacs really take that long to start?
>> >
>> > 'fraid so! I've never actually timed it, but I am sitting waiting for it
>> > to be in a useable state.
>> >>
>> >> 2. In which situations does it crash?
>> >
>> > Usually when I'm writing in latex, and suddenly, in the blink of an eye,
>> > its gone! So far I haven't lost any data on restarting. but it is an
>> > annoyance.
>
> I suggest (as a debugging device) to give up on server daemon etc,
> just start emacs normally from a shell until it 'crashes'.
> When it does is there any shell message?
Will do.
Thanks
Sharon.
--
A taste of linux = http://www.sharons.org.uk
TGmeds = http://www.tgmeds.org.uk
Debian 8.0, fluxbox 1.3.7, emacs 24.5.50.3
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2015-07-20 19:23 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-19 20:19 starting the emacs daemon using init.org? Sharon Kimble
2015-07-19 23:20 ` Emanuel Berg
2015-07-20 11:28 ` Sharon Kimble
2015-07-20 13:41 ` Marcin Borkowski
2015-07-20 14:20 ` Subhan Michael Tindall
2015-07-20 17:29 ` Sharon Kimble
2015-07-20 17:36 ` Paul Smith
2015-07-20 17:46 ` John Mastro
2015-07-20 18:41 ` Marcin Borkowski
2015-07-23 7:40 ` Eric S Fraga
2015-07-23 13:40 ` Grant Rettke
[not found] ` <mailman.7294.1437640616.904.help-gnu-emacs@gnu.org>
2015-07-23 9:00 ` Rusi
[not found] ` <mailman.7190.1437414422.904.help-gnu-emacs@gnu.org>
2015-07-23 1:46 ` Rusi
2015-07-20 19:19 ` Sharon Kimble
2015-07-21 15:08 ` Startup time [Was: starting the emacs daemon using init.org?] Ian Zimmerman
[not found] ` <mailman.7228.1437491341.904.help-gnu-emacs@gnu.org>
2015-07-21 15:28 ` Pascal J. Bourguignon
2015-07-21 19:05 ` Marcin Borkowski
2015-07-21 21:10 ` Emanuel Berg
2015-07-21 18:19 ` Robert Marshall
2015-07-20 23:45 ` starting the emacs daemon using init.org? Emanuel Berg
2015-07-20 23:35 ` Emanuel Berg
[not found] ` <mailman.7173.1437391698.904.help-gnu-emacs@gnu.org>
2015-07-20 12:42 ` Barry Fishman
2015-07-20 12:57 ` Rusi
2015-07-20 19:23 ` Sharon Kimble [this message]
2015-07-21 13:17 ` Robert Thorpe
2015-07-20 13:40 ` Marcin Borkowski
2015-07-20 3:03 ` Ian Zimmerman
2015-07-20 11:25 ` Sharon Kimble
2015-07-20 14:30 ` Ian Zimmerman
2015-07-20 14:54 ` Paul Smith
2015-07-20 15:43 ` Óscar Fuentes
2015-07-20 16:39 ` Paul Smith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874mky3a7d.fsf@skimble.plus.com \
--to=boudiccas@skimble.plus.com \
--cc=help-gnu-emacs@gnu.org \
--cc=rustompmody@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).