From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: org-babel-load-file support elisp Date: Mon, 03 Feb 2020 20:23:14 +0100 Message-ID: <87tv47mq59.fsf@gnu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:52666) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iyhJX-0007b1-99 for emacs-orgmode@gnu.org; Mon, 03 Feb 2020 14:23:20 -0500 In-Reply-To: (Troy Hinckley's message of "Mon, 3 Feb 2020 10:30:56 -0700") 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: Troy Hinckley Cc: emacs-orgmode@gnu.org 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.=C2=A0 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, --=20 Bastien