From mboxrd@z Thu Jan 1 00:00:00 1970 From: Troy Hinckley Subject: Re: org-babel-load-file support elisp Date: Mon, 3 Feb 2020 15:08:05 -0700 Message-ID: References: <87tv47mq59.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="00000000000009c8b4059db329b4" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:55098) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iyjtH-0002ZK-Eh for emacs-orgmode@gnu.org; Mon, 03 Feb 2020 17:08:24 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iyjtF-00010c-7L for emacs-orgmode@gnu.org; Mon, 03 Feb 2020 17:08:23 -0500 In-Reply-To: <87tv47mq59.fsf@gnu.org> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane-mx.org@gnu.org Sender: "Emacs-orgmode" To: Bastien Cc: emacs-orgmode@gnu.org --00000000000009c8b4059db329b4 Content-Type: text/plain; charset="UTF-8" > 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. -Troy Hinckley On Feb 3, 2020, 12:23 PM -0700, Bastien , wrote: Hi Troy, 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? Thanks, -- Bastien --00000000000009c8b4059db329b4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
>=C2=A0I think supporting "#+begin_src elisp&= quot; would be confusing

elisp is already supported in all other babel functions.=C2=A0org= -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 thi= s limitation in its docstring.=C2=A0

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.=C2=A0

-Troy Hinckley

On Feb 3, 2020, 12:23 PM -0700, Bastien &= lt;bzg@gnu.org>, wr= ote:
Hi Troy,

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 o= f 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.=C2=A0

I think supporting "#+begin_src elisp" would be confusing but I a= gree
we could give a hint somewhere about this.

Can you suggest which docstring should be updated and how?

Thanks,

--
Bastien
--00000000000009c8b4059db329b4--