emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Tim Cross <theophilusx@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-babel-load-file support elisp
Date: Mon, 10 Feb 2020 08:25:27 +0100	[thread overview]
Message-ID: <87imke9a54.fsf@gnu.org> (raw)
In-Reply-To: <871rrbb85a.fsf@gmail.com> (Tim Cross's message of "Tue, 04 Feb 2020 09:47:30 +1100")

Hi Tim and Troy,

Tim Cross <theophilusx@gmail.com> writes:

> I came across this inconsistency a while back. I think the problem is
> that you should *not* be able to use elisp as a language specifier in
> source blocks.
> All other language specifiers comply to the pattern of source block
> languages being the language major mode name without the '-mode', but
> there is no elisp-mode.
> The problem now is that removing support for 'elisp' would break too
> much.

What I suggest for this particular issue is this: first be liberal
while staying consistent (thus allowing "elisp" as Troy suggest),
then be strict when a major release is issued (thus removing aliases
that are problematic, not just "elisp" but others.)

WDYT?  Troy, would you be able to prepare a patch for this?



  parent reply	other threads:[~2020-02-10  7:25 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
2020-02-03 22:47     ` Tim Cross
     [not found]       ` <ZclaOPJYs9OChIJ0EmvuYezQf9yKAMMunMPz71gz74t9DKUs83QU20uf80bmCLIA8fvx-dQ_DP_89q6s5ddr1Q==@protonmail.internalid>
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 [this message]
2020-02-10  8:00         ` Norman Tovey-Walsh
2020-02-12 21:42 ` Bastien
2020-02-12 22:18   ` Troy Hinckley

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:

  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=87imke9a54.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=theophilusx@gmail.com \


* 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).