From: Troy Hinckley <email@example.com>
To: Bastien <firstname.lastname@example.org>
Subject: Re: org-babel-load-file support elisp
Date: Mon, 3 Feb 2020 15:08:05 -0700 [thread overview]
Message-ID: <CALOSHoRZeqq3-DbPFQOgjTVZ-nEWfuCfwZYHvY5inmfpFOCzPQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]
> I think supporting "#+begin_src elisp" would be confusing
elisp is already supported in all other babel
functions. org-babel-load-file is the only function that makes a
distinction as far as I can tell. And since that function is outlier it
makes sense to document this limitation in its docstring.
Or even better would be to detect if the user had elisp blocks and throw
and error. Though I am not sure how to do that outside of seeing if
tangling elisp is successful.
On Feb 3, 2020, 12:23 PM -0700, Bastien <email@example.com>, wrote:
I tracked down an issue trying to load a literate config file.
org-babel-load-file calls org-babel-tangle-file with lang set to
"emacs-lisp". This means that it won't tangle any blocks with
language set to "elisp", which is equivalent. I can't think of an
easy way to fix this since you would need to target both languages.
Maybe at very least we could add something to the doc string to draw
attention to this limitation.
I think supporting "#+begin_src elisp" would be confusing but I agree
we could give a hint somewhere about this.
Can you suggest which docstring should be updated and how?
[-- Attachment #2: Type: text/html, Size: 2062 bytes --]
next prev parent reply other threads:[~2020-02-03 22:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 17:30 org-babel-load-file support elisp Troy Hinckley
2020-02-03 19:23 ` Bastien
2020-02-03 22:08 ` Troy Hinckley [this message]
2020-02-03 22:47 ` Tim Cross
[not found] ` <ZclaOPJYs9OChIJ0EmvuYezQf9yKAMMunMPz71gz74t9DKUs83QU20uf80bmCLIA8fvx-dQ_DP_89q6s5ddr1Qfirstname.lastname@example.org>
2020-02-04 6:03 ` Jack Kamm
2020-02-04 6:29 ` Tim Cross
2020-02-04 17:57 ` Berry, Charles via General discussions about Org-mode.
2020-02-10 7:25 ` Bastien
2020-02-10 8:00 ` Norman Tovey-Walsh
2020-02-12 21:42 ` Bastien
2020-02-12 22:18 ` Troy Hinckley
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).