From: Sven Bretfeld <sven.bretfeld@ntnu.no>
To: Org-mode <emacs-orgmode@gnu.org>
Subject: Feature request: Maintaining multiple init files with one org file
Date: Sat, 28 Jul 2018 11:25:37 +0200 [thread overview]
Message-ID: <87va8ziuem.fsf@ntnu.no> (raw)
Hi
I don't know how you guys maintain init files for different hosts. I
have one org-file with the header:
#+PROPERTY: header-args :tangle ~/.emacs
The file is synced to all my machines and produces the local init files
on each. Most configurations are shared, but some are host-specific
(e.g. font size).
Sadly export filtering does not work with the tangle function. It would
be nice to be able to do something like:
,----
| * Default Frame
| ** Office Computer :OFFICE:
| #+begin_src emacs-lisp
| (setq default-frame-alist '(
| (font . "-PfEd-DejaVu Sans Mono-normal-normal-normal-*-26-*-*-*-m-0-iso10646-1")
| (width . 102)
| (height . 41))
| #+end_src
|
| ** Computer at home :HOME:
| #+begin_src emacs-lisp
| (setq default-frame-alist '(
| (font . "-PfEd-DejaVu Sans Mono-normal-normal-normal-*-18-*-*-*-m-0-iso10646-1")
| (width . 150)
| (height . 50))
| #+end_src
|
| ** Laptop :LAPTOP:
| #+begin_src emacs-lisp
| (setq default-frame-alist '(
| (font . "-PfEd-DejaVu Sans Mono-normal-normal-normal-*-12-*-*-*-m-0-iso10646-1")
| (width . 80)
| (height . 30))
| #+end_src
`----
It should be clear what this is about. On the office computer you would
prepare the file headers to exclude the tags HOME and LAPTOP from being
tangled and, after saving/tangling the file, you would have a nice init
file suiting this computer. At home the same by excluding the other tags
etc.
This would save a lot of work and you would have a tidy way to maintain
all your init files without (if (string-equal (system-name) clauses.
If the noexport tag worked, it would also save a lot of time and mess
when debugging your init file in case of an error.
I don't actually understand why the developers decided not to implement
export filtering in the tangling operations. I know about the COMMENT
keyword, but the above example should make clear that this solution is
far from handy.
Maybe there is another way that escaped me so far?
All best,
Sven
next reply other threads:[~2018-07-28 9:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-28 9:25 Sven Bretfeld [this message]
2018-07-28 13:53 ` Feature request: Maintaining multiple init files with one org file Amin Bandali
2018-07-29 10:49 ` Sven Bretfeld
2018-07-29 0:06 ` Tim Cross
2018-07-29 10:42 ` Sven Bretfeld
2018-07-30 7:07 ` Eric S Fraga
2018-07-30 12:15 ` Sven Bretfeld
2018-07-30 19:25 ` Diego Zamboni
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=87va8ziuem.fsf@ntnu.no \
--to=sven.bretfeld@ntnu.no \
--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).