Wow. Thanks for the quick resolution!
On Feb 12, 2020, 2:42 PM -0700, Bastien , wrote:
> Hi Troy,
>
> Troy Hinckley writes:
>
> > 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
Hi Troy,
Troy Hinckley writes:
> 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.
This is now fixed in
>> 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 a
Hi Tim and Troy,
Tim Cross 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 langua
> On Feb 3, 2020, at 10:03 PM, Jack Kamm wrote:
>
> Tim Cross writes:
>
>> 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.
>
> Sorry to be pedantic, but I think shell sour
Well there are exceptions to all rules aren't there?
Yes, strictly speaking, for shell scripts, only 'sh' fits with the
-mode rule. However, that mode is also slightly different from
other language modes in that it supports many shell 'dialects'.
The thing is, the more 'liberal' we are with wha
Tim Cross writes:
> 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.
Sorry to be pedantic, but I think shell source blocks are another
exception here. They can use various synonym
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
the
> 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 docstri
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 si
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 t
11 matches
Mail list logo
