emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Schulte <schulte.eric@gmail.com>
To: Nicolas Richard <theonewiththeevillook@yahoo.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: add "elisp" to org-babel-tangle-lang-exts to support "elisp" source blocks [8.2.5h (release_8.2.5h-680-g12df70 @ /home/youngfrog/sources/org-mode/lisp/)]
Date: Thu, 06 Mar 2014 14:58:02 -0700	[thread overview]
Message-ID: <87a9d3ug55.fsf@gmail.com> (raw)
In-Reply-To: 87wqg8wskr.fsf@yahoo.fr

Applied, Thanks.

Nicolas Richard <theonewiththeevillook@yahoo.fr> writes:

> Hello,
>
> "elisp" (vs "emacs-lisp") code blocks are supported via an entry
> "org-src-lang-modes" but not in org-babel-tangle-lang-exts.
>
> The patch below is to fix that.
>
> From: Nicolas Richard <theonewiththeevillook@yahoo.fr>
> Date: Wed, 5 Mar 2014 16:49:30 +0100
> Subject: [PATCH] lisp/ob-tangle.el: "elisp" should get tangled to ".el" files.
>
> ---
>  lisp/ob-tangle.el | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/lisp/ob-tangle.el b/lisp/ob-tangle.el
> index 5797ea4..8923e16 100644
> --- a/lisp/ob-tangle.el
> +++ b/lisp/ob-tangle.el
> @@ -41,7 +41,8 @@
>  (declare-function org-before-first-heading-p "org" ())
>  
>  (defcustom org-babel-tangle-lang-exts
> -  '(("emacs-lisp" . "el"))
> +  '(("emacs-lisp" . "el")
> +    ("elisp" . "el"))
>    "Alist mapping languages to their file extensions.
>  The key is the language name, the value is the string that should
>  be inserted as the extension commonly used to identify files

-- 
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D

      reply	other threads:[~2014-03-06 22:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05 15:52 Bug: add "elisp" to org-babel-tangle-lang-exts to support "elisp" source blocks [8.2.5h (release_8.2.5h-680-g12df70 @ /home/youngfrog/sources/org-mode/lisp/)] Nicolas Richard
2014-03-06 21:58 ` Eric Schulte [this message]

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=87a9d3ug55.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=theonewiththeevillook@yahoo.fr \
    /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).