From: Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com>
To: Rasmus <rasmus@gmx.us>
Cc: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: Moving my init.el to Org
Date: Tue, 2 Sep 2014 08:52:28 -0400 [thread overview]
Message-ID: <CAEWDx5d_x3hw437ttUQdG7rG_sBZ5i2+Ax02GuMnRZP9=fHfvQ@mail.gmail.com> (raw)
In-Reply-To: <87y4u25h2r.fsf@gmx.us>
[-- Attachment #1: Type: text/plain, Size: 1747 bytes --]
Hello,
On 2 September 2014 08:42, Rasmus <rasmus@gmx.us> wrote:
> Rainer M Krug <Rainer@krugs.de> writes:
>
> > Oleh <ohwoeowho@gmail.com> writes:
> >
> >>> I know that I could use org-babel-load-file, or outshine. What are
> >>> other possibilities? What are the caveats (and advantages) of both
> >>> (other?) ways?
> >>
> >> I'm using a one .el file per mode approach, with around 4000 lines
> >> split into 40 files.
> >>
> >> This approach simplifies things a lot: for instance I haven't touched
> >> Javascript in ages, but all my customizations for it are sitting in
> >> javascript.el without getting in the way of the stuff that I'm using
> >> now. They aren't even loaded unless I open a js file.
> >
> > Interesting - is your configuration online, so that one could take a
> > look at it? I did not find them on your github page?
> >
> > Or how do you do it, that the e.g. javascript.el is only loaded when a
> > js file is opened? Because this is exactly what I would like to have.
>
> How about something like this:
>
> (with-eval-after-load 'js-mode (load "javascript.el"))
>
> Use eval-after-load if you are using an older Emacs. Note I don't
> know if there's anything called js-mode. . .
>
I've been using use-package (https://github.com/jwiegley/use-package) for
only loading the various package-specific configurations when needed.
For that example it would be:
(use-package js-mode
:mode ("\\.js\\'" . js-mode)
:config (require 'javascript) ;; or (load "javascript.el") if not provided
)
In my case it's still all in my init.el (with Outshine headings for each
mode that use-package manages), but could easily extract the portions into
their own files (especially for larger configurations like org)
Regards,
Jon
[-- Attachment #2: Type: text/html, Size: 2674 bytes --]
next prev parent reply other threads:[~2014-09-02 12:52 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-31 8:37 Moving my init.el to Org Marcin Borkowski
2014-08-31 9:20 ` Thorsten Jolitz
2014-08-31 10:05 ` Thorsten Jolitz
2014-08-31 12:45 ` Alan Schmitt
2014-08-31 14:12 ` Thorsten Jolitz
2014-09-01 20:27 ` Alan Schmitt
2014-09-01 21:24 ` Thorsten Jolitz
2014-09-02 8:20 ` Alan Schmitt
2014-09-02 9:22 ` Thorsten Jolitz
2014-08-31 10:37 ` Rasmus
2014-08-31 12:41 ` Grant Rettke
2014-09-01 1:24 ` Brady Trainor
2014-09-01 15:27 ` Oleh
2014-09-02 9:01 ` Rainer M Krug
2014-09-02 12:42 ` Rasmus
2014-09-02 12:52 ` Jonathan Leech-Pepin [this message]
2014-09-03 6:49 ` Rainer M Krug
2014-09-03 11:17 ` Oleh
2014-09-03 11:48 ` Rainer M Krug
2014-09-05 14:27 ` Marcin Borkowski
2014-09-06 2:49 ` Thorsten Jolitz
2014-09-06 9:26 ` Eduardo Ochs
2014-09-06 10:10 ` Thorsten Jolitz
2014-10-30 10:19 ` OrgStruct: start with collapsed view (was: Moving my init.el to Org) Karl Voit
2014-10-30 10:32 ` OrgStruct: start with collapsed view Rasmus
2014-10-30 12:41 ` Thorsten Jolitz
2014-10-31 22:10 ` Scott Randby
2014-11-01 10:16 ` Karl Voit
2014-11-01 10:44 ` Thorsten Jolitz
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='CAEWDx5d_x3hw437ttUQdG7rG_sBZ5i2+Ax02GuMnRZP9=fHfvQ@mail.gmail.com' \
--to=jonathan.leechpepin@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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).