emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Norman Tovey-Walsh <ndw@nwalsh.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-babel-load-file support elisp
Date: Mon, 10 Feb 2020 08:00:49 +0000	[thread overview]
Message-ID: <m28slavpla.fsf@nwalsh.com> (raw)
In-Reply-To: <87imke9a54.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 2228 bytes --]

>> 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?

My 2¢ from the peanut gallery.

Generally speaking, I’m in favor of consistency. A couple of months ago,
I stumbled over the fact that ‘elisp’ seemed to do syntax highlighting
correctly but didn’t tangle. I didn’t, at the time, work out the cause
of the problem, I just learned to use ‘emacs-lisp’ as the language name.

Looking at this thread, it seems like there are a bunch of exceptions to
the rule that the language is be the name of the mode without ‘-mode’.

Just off the top of my head, I can think of several languages supported
by multiple modes. If the rule is that the language is the mode name,
then if I use ‘extra-special-language-mode’ to edit ‘language’, do I
have to use ‘extra-special-language’ as the language name? Is that going
to seem natural? What burden does that put on the developer of
‘extra-special-language-mode’ to make tangle and other Org-mode features
work like they would for ‘language-mode’?

I wonder if it makes more sense to invent a mechanism for assigning
language synonyms that can be used throughout Org?

                                        Be seeing you,

P.S. Just to prove I can play devil’s advocate, I’m very conscious of
the fact that a few days ago, I invented an ‘xproc-mode’ as a vacuous
extension to ‘xml-mode’ precisely *because* I wanted to define different
org-babel-execute behavior.

Norman Tovey-Walsh <ndw@nwalsh.com> | Some disguised deceits
https://nwalsh.com/                 | counterfeit truth so perfectly
                                    | that not to be taken in by them
                                    | would be an error of
                                    | judgment.--La Rochefoucauld

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2020-02-10  8:01 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
2020-02-10  8:00         ` Norman Tovey-Walsh [this message]
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=m28slavpla.fsf@nwalsh.com \
    --to=ndw@nwalsh.com \
    --cc=emacs-orgmode@gnu.org \


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