From: Sami Airaksinen <samiaira@gmail.com>
To: emacs-orgmode@gnu.org
Subject: [PATCH] org.el: org-babel-load-file loads first tangle file
Date: Thu, 29 Jan 2015 23:49:20 +0200 [thread overview]
Message-ID: <54CAAAE0.208@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 698 bytes --]
Hi,
I use quite sophisticated (read complicated) initialization of my emacs.
Now I finally updated my emacs and org-mode upto date and found out that
org-babel-load-file doesn't work as previously.
I don't know if you have already noticed but if your tangled source
org-mode file has multiple target files for the tangle blocks, it loads
the file which was found last. This most often isn't the file name that
was given as input. There could be more generic solution to this, but I
though that it might be best to keep this patching simple as possible.
This is my first patch proposal so I hope I'm doing right and adding it
as an attachment to this post
--
Sami Airaksinen
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: 0001-org.el-org-babel-load-file-loads-first-tangle-file.patch --]
[-- Type: text/x-patch; name="0001-org.el-org-babel-load-file-loads-first-tangle-file.patch", Size: 1291 bytes --]
From fe2c30fb06935ce871485b4e3816313d59d96cbe Mon Sep 17 00:00:00 2001
From: Sami Airaksinen <samiaira@gmail.com>
Date: Thu, 29 Jan 2015 23:10:02 +0200
Subject: [PATCH] org.el: org-babel-load-file loads first tangle file
(org-babel-load-file): When org-mode FILE has multiple target files
for tangle blocks, `exported-file' will be set to last found
target file, which might not be the `file'.
Therefore fix for this bug is to select the last element of that
tangled file list, which is the tangle target file of the first found
tangle block, most typically the `file'.
Suggestion from a patch proposal by Sami Airaksinen
TINYCHANGE
---
lisp/org.el | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lisp/org.el b/lisp/org.el
index b0e4380..2bc7f30 100755
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -236,7 +236,7 @@ file to byte-code before it is loaded."
(unless (and (file-exists-p exported-file)
(> (funcall age file) (funcall age exported-file)))
(setq exported-file
- (car (org-babel-tangle-file file exported-file "emacs-lisp"))))
+ (car (last (org-babel-tangle-file file exported-file "emacs-lisp")))))
(message "%s %s"
(if compile
(progn (byte-compile-file exported-file 'load)
--
1.9.1
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next reply other threads:[~2015-01-29 21:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 21:49 Sami Airaksinen [this message]
2015-01-30 9:44 ` [PATCH] org.el: org-babel-load-file loads first tangle file Nicolas Goaziou
2015-01-30 12:55 ` Sami Airaksinen
2015-01-30 17:13 ` Nicolas Goaziou
2015-01-31 22:20 ` Sami Airaksinen
2015-01-31 23:04 ` 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=54CAAAE0.208@gmail.com \
--to=samiaira@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 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).