unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Robert Marshall <spam@capuchin.co.uk>
To: help-gnu-emacs@gnu.org
Subject: Re: Startup time [Was: starting the emacs daemon using init.org?]
Date: Tue, 21 Jul 2015 19:19:51 +0100	[thread overview]
Message-ID: <87d1zltltk.fsf@capuchin.co.uk> (raw)
In-Reply-To: mailman.7228.1437491341.904.help-gnu-emacs@gnu.org

On Tue, Jul 21 2015, Ian Zimmerman <itz@buug.org> wrote:

> On 2015-07-20 20:19 +0100, Sharon Kimble wrote:
>
>> I've just reloaded emacs after changing my init.org, and it took 142.3secs!
>
> Do you (and others who suffer from long startup times) use the "desktop"
> feature, reopening the files that were open when emacs last exited?  If
> yes, are all these files still needed?  Maybe you should do one (or
> both) of the following:
>
> Manually close some files (kill some buffers, in emacs speak)
>
> Set the desktop-buffers-not-to-save variable to exclude some buffers
> from the auto-reopening mechanism

I use desktop and have an init time of 3.7 sec but I do have
(setq desktop-restore-eager 50)

[and I have far too many buffers hanging around that I need to get around
to removing!]

Robert
-- 
La grenouille songe..dans son château d'eau


  parent reply	other threads:[~2015-07-21 18:19 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 [this message]
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
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=87d1zltltk.fsf@capuchin.co.uk \
    --to=spam@capuchin.co.uk \
    --cc=help-gnu-emacs@gnu.org \
    --cc=robert@capuchin.co.uk \
    /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).