emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Pete Ley <peteley11235@gmail.com>
To: Brady Trainor <algebrat@uw.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: sharing my firsts, org babel tangle and "init" .org file
Date: Fri, 18 Apr 2014 17:24:38 -0700	[thread overview]
Message-ID: <87sipa5fp5.fsf@enterprise.sectorq.net> (raw)
In-Reply-To: <lipovi$hv$1@ger.gmane.org> (Brady Trainor's message of "Thu, 17 Apr 2014 16:43:45 -0700")

I've looked at the solution on worg and, though I didn't actually try to
implement, it seems like tangling your init file every time you open
Emacs is a little cumbersome. Please correct me if I'm wrong in this
assumption. I also have a sync script hooked into my tangling that has
to do with exporting some of my config sections to my gopher site so
they're always up to date, so maybe it's just that my tangling
experience is especially involved. 

Here's what I do. Since I probably only edit my config ~10% of the times
that I open Emacs, it seems easier to just have a statically-tangled
init file, so I just basically use C-c C-v C-t instead of C-x C-s to
save my init.org. I also use somewhat customized init files on a few
different hosts which share the same .emacs.d. They share come common
functionality and differ slightly, so there are a few init files tangled
into ~/.emacs.d of the form hostname.el and the init.el file is
basically a switch which chooses which one to load on startup.

Short reference:
http://gopher.floodgap.com/gopher/gw?gopher://sdf.org:70/0/users/framling/emacs/init

  parent reply	other threads:[~2014-04-19  0:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-17 23:43 sharing my firsts, org babel tangle and "init" .org file Brady Trainor
2014-04-18 11:15 ` Bastien
2014-04-20  1:50   ` Eric Schulte
2014-04-19  0:24 ` Pete Ley [this message]
2014-04-19  1:58   ` Grant Rettke
2014-04-19 15:05   ` Charles Berry

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=87sipa5fp5.fsf@enterprise.sectorq.net \
    --to=peteley11235@gmail.com \
    --cc=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).