From: Brady Trainor <algebrat@uw.edu>
To: emacs-orgmode@gnu.org
Subject: Re: Moving my init.el to Org
Date: Sun, 31 Aug 2014 18:24:12 -0700 [thread overview]
Message-ID: <lu0hrv$fta$1@ger.gmane.org> (raw)
In-Reply-To: <20140831103706.549dc45b@aga-netbook>
On 8/31/2014 1:37 AM, Marcin Borkowski wrote:
> 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?
Another pro for `outshine`, I've made a folding expression for Vim that
respects `outshine` behavior, as far as I use it.
augroup filetype_lisp
au!
au FileType lisp setlocal foldmethod=expr foldexpr=ELispLevel()
augroup END
function! ELispLevel()
let n = len(matchstr(getline(v:lnum), '^;\+'))
let l = n - 2
if n >= 3
return ">" . l
else
return "="
endif
endfunction
From Vim, typing `:help fold-expr RET` will give a clue as to the ">"
and "=" expressions.
I tried the init.org for a while, it was fun so you should try it for a
while, but I've been trying to reduce how many conversions I have in my
projects. And I finally succumbed to the convention of breaking some
parts of my init file into parts (nav, org, etc). Trying to keep my init
files easy to drop-in and understand was a factor, as I'm always trying
to convert people to Emacs and org-mode (success zero so far). And
troubleshooting may be considered easier.
More specifically, consider that if you try to convert someone to Emacs
and org-mode via an init.org file, they will have to deal with three new
problems at once.
1. The order of loading org, babel, and the .org file, and any possible
issues with old versions of org builtin to Emacs
2. As you show them the emacs-lisp, they may get distracted by all the
#+BEGIN_SRC emacs-lisp etc., wondering simultaneously how everything
fits together
3. Learning org-mode and .emacs in an intertwined way
Brady
next prev parent reply other threads:[~2014-09-01 1:24 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 [this message]
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
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='lu0hrv$fta$1@ger.gmane.org' \
--to=algebrat@uw.edu \
--cc=emacs-orgmode@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.
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).