From: "Thomas S. Dye" <tsd@tsdye.com>
To: Xebar Saram <zeltakc@gmail.com>
Cc: org mode <emacs-orgmode@gnu.org>
Subject: Re: Using an org based init file slows down emacs startup by 50x..help needed :(
Date: Sat, 10 Dec 2016 10:24:36 -1000 [thread overview]
Message-ID: <m27f77352z.fsf@tsdye.com> (raw)
In-Reply-To: <CAOQHXPoz1KS-z9s1aHD3-xdkCZsO6hHPvV3QsJV44SozcjEgwg@mail.gmail.com>
Aloha Xebar,
Xebar Saram writes:
> Ok so i think the reason really is that i have way to many lisp code blocks
> as suggested. i found out a very interesting post that maybe of interest to
> alot of org users
>
> http://www.holgerschurig.de/en/emacs-efficiently-untangling-elisp/
>
> this creates a new function that very efficiently tangles my org file and
> the time goes from 6 minutes to 25 seconds!!
>
> this is a link to an example init file
>
> https://bitbucket.org/holgerschurig/emacsconf/src/416b2bba2d1d334b9c6ddbd56f8c7f8bd8bc4aab?at=master
Have you seen Eric Schulte's starter-kit
(http://eschulte.github.io/emacs24-starter-kit/)? Using it, I keep my
initialization functions in a few different Org mode files, which the
starter-kit tangles to .el iff the Org mode file has been changed since
it was last tangled. I'm able to keep the initialization process
reasonably organized (I'm the limiting factor), without the wait.
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2016-12-10 20:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-10 8:36 Using an org based init file slows down emacs startup by 50x..help needed :( Xebar Saram
2016-12-10 8:43 ` Nicolas Goaziou
2016-12-10 12:53 ` Xebar Saram
2016-12-10 18:33 ` Xebar Saram
2016-12-10 20:24 ` Thomas S. Dye [this message]
2016-12-12 12:24 ` Julian M. Burgos
2016-12-12 10:03 ` Rainer M Krug
2016-12-12 21:30 ` Grant Rettke
2016-12-13 7:19 ` Xebar Saram
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m27f77352z.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=zeltakc@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).