From: Marcin Borkowski <mbork@mbork.pl>
To: "help-gnu-emacs\@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: starting the emacs daemon using init.org?
Date: Mon, 20 Jul 2015 20:41:29 +0200 [thread overview]
Message-ID: <87r3o2smcm.fsf@mbork.pl> (raw)
In-Reply-To: <CAOj2CQTgziB=YmzkeP1_gigmp_5e9c3U+ciokOnVmZ80pXsbLA@mail.gmail.com>
On 2015-07-20, at 19:46, John Mastro <john.b.mastro@gmail.com> wrote:
>> Wow I wonder what you all are doing in your init files!!
>>
>> My init time is 1.8 seconds...!
>
> 4.3 seconds on Windows and 2.5 on Linux here. Both machines are
> reasonably spec'd (e.g. quad core i5 from a couple years ago) but
> definitely not monsters. And I have almost 100 packages installed and
> 3,600 SLOC in my init files.
>
> If you're not using `with-eval-after-load' (or `eval-after-load'), I
> highly recommend it.
I deliberately do not use any deferred loading of packages etc. - if
I end up autoloading something, I usually put a (require '...) in my
init.el so that Emacs doesn't pause when loading e.g. AUCTeX. I very
much prefer longer startup time than pauses during work.
Also, I use a few large libraries - Org, Icicles, AUCTeX...
And I have a pretty low-end (about $150 three years back) netbook, which
is more than enough for Elisp coding, email, Org and LaTeX. Also, long
startup-time doesn't bother me at all - I often have M-x emacs-uptime of
several days or even more than a week.
Best,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University
next prev parent reply other threads:[~2015-07-20 18:41 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 [this message]
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
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=87r3o2smcm.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=help-gnu-emacs@gnu.org \
/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).