Achim Gratz writes:
> "Eric Schulte" writes:
>> Thanks for the suggestions, I've just implemented them.
>
> This likely relates to commit eb0068e9, which raises this warning
>
> In org-babel-demarcate-block:
> ob.el:1141:49:Warning: reference to free variable `org-babel-load-languages'
>
> duri
"Eric Schulte" writes:
> Fixed, Thanks -- Eric
Confirmed.
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
___
Fixed, Thanks -- Eric
Achim Gratz writes:
> "Eric Schulte" writes:
>> Thanks for the suggestions, I've just implemented them.
>
> This likely relates to commit eb0068e9, which raises this warning
>
> In org-babel-demarcate-block:
> ob.el:1141:49:Warning: reference to free variable `org-babel-l
"Eric Schulte" writes:
> Thanks for the suggestions, I've just implemented them.
This likely relates to commit eb0068e9, which raises this warning
In org-babel-demarcate-block:
ob.el:1141:49:Warning: reference to free variable `org-babel-load-languages'
during byte-compile.
Achim.
--
+<[Q+
Hi Seb,
I plan to extend the block demarcation function to all block types, but
haven't yet found the time.
Best -- Eric
Sébastien Vauban writes:
> Hi Eric,
>
> Sébastien Vauban wrote:
>> "Eric Schulte" wrote:
>>> Sébastien Vauban
>>> writes:
Is it possible to envision completion of the
Hi Eric,
Sébastien Vauban wrote:
> "Eric Schulte" wrote:
>> Sébastien Vauban
>> writes:
>>> Is it possible to envision completion of the language name? Writing
>>> =emacs-lisp= could become easier...
>>
>> Thanks for the suggestions, I've just implemented them.
>
> Tested. Simply fan-tas-tic!
J
Hi Eric,
"Eric Schulte" wrote:
> Sébastien Vauban writes:
>> Two comments about that great function:
>>
>> - Would it be possible to leave the code where it is, and have it selected
>> (in a region), when the question about the language is asked?
>>
>> Currently, it seems to be temporarily "c
