From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: [new exporter] is #+bind supported?
Date: Tue, 05 Mar 2013 19:18:29 +0100 [thread overview]
Message-ID: <87sj491zii.fsf@Rainer.invalid> (raw)
In-Reply-To: 87hakp3i2t.fsf@ucl.ac.uk
Eric S Fraga writes:
> It is rather annoying to have the old org files picked up
> automatically. My git copy of org-mode is before anything else in my
> =load-path= variable. I know there has been a whole thread on the list
> about this but I did not see any solution to this; did I miss one? I
> track emacs-snapshot weekly and org-mode more frequently.
No, nothing complete yet. Here's what I have so far, some autoload
definitions might still be there, but will error out due to the fact
that their target files are not in load-path anymore.
--8<---------------cut here---------------start------------->8---
;;
;; Kill our ancestors
;;
;; clean load-path
(setq load-path
(delq nil (mapcar
(function (lambda (p)
(unless (string-match "lisp/org$" p)
p))
load-path)))
;; remove property list to defeat cus-load and remove autoloads
(mapatoms (function (lambda (s)
(let ((sn (symbol-name s)))
(when (string-match "^\\(org\\|ob\\)-?" sn)
(setplist s nil)
(when (autoloadp s)
(unintern s)))))))
(add-to-list 'load-path "/path/to/org-master")
(load "org-loaddefs.el" nil nil 'nosuffix)
--8<---------------cut here---------------end--------------->8---
I still need to generate the custom-load definitions with the build
system so that you can browse customize without loading all Org files
first.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada
next prev parent reply other threads:[~2013-03-05 18:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 14:20 [new exporter] is #+bind supported? Eric S Fraga
2013-03-05 14:33 ` Achim Gratz
2013-03-05 16:52 ` Eric S Fraga
2013-03-05 18:18 ` Achim Gratz [this message]
2013-03-06 8:44 ` Eric S Fraga
2013-03-06 20:09 ` Achim Gratz
2013-03-07 8:36 ` Eric S Fraga
2013-03-05 22:07 ` Nicolas Goaziou
2013-03-06 8:51 ` Eric S Fraga
2013-03-06 10:21 ` Nicolas Goaziou
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=87sj491zii.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).