From: "Eddward DeVilla" <eddward@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: customize question
Date: Tue, 7 Nov 2006 11:10:53 -0600 [thread overview]
Message-ID: <b71b18520611070910ned0b819sb05e356a7475088d@mail.gmail.com> (raw)
Hi all,
I'm afraid this might be more of an emacs question than an orgmode
specific question. I'm trying to move my org-mode config out of my
.emacs as much as possible and into something a little more
compartmentalized. I had tried to do as much as I could with #+, but
they can only go some far, and for security reasons, I think that is
probably good.
Right now, my thinking is to have a lisp file that I can call from
.emacs to set everything I need for orgmode. I'll have the org file
listed in a file instead of having it maintained in the .emacs. I
won't have to keep common sections in the org files with file specific
configurations and I could even define dynamic blocks and hooks in my
configuration. From the one lisp file I could get references to
any/all of the other files I would need to look at to copy, move or
back up my org setup. I could also put non-org but project related
configurations in there like macros for inserting blank project forms.
My question is, can I just move the settings from
(custom-set-variables ...) out into a separate file without
consequences? I know I wouldn't be able to use custom the same way,
but I think I'd still prefer having it separate over having the
interface to change things. I just didn't know if there was something
else magical about the variables maintained by custom. If there is a
better answer, feel free to say so or point me at something to read on
the topic.
Thanks,
Edd
next reply other threads:[~2006-11-07 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-07 17:10 Eddward DeVilla [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-20 15:10 customize question Ian Zimmerman
2002-12-20 17:50 ` Kevin Rodgers
2002-12-20 19:22 ` Kai Großjohann
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b71b18520611070910ned0b819sb05e356a7475088d@mail.gmail.com \
--to=eddward@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.