Ihor Radchenko writes:
> Daniel Kraus writes:
>
>>> The only downside is that people might need to
>>> (require 'ob-clojurescript)
>>> I am thinking if ob-core.el should try to automatically guess the
>>> correct library to be loaded.
>>
>> We could just (require 'ob-clojurescript) inside
Ihor Radchenko writes:
> stardiviner writes:
>
>> For now, ob-clojure.el contains lot of code for ClojureScript. Only some
>> code has same functionality. Like CIDER backend. In the future,
>> ClojureScript part code will increase and different. So I suggest
>> separate them into two source
For now, ob-clojure.el contains lot of code for ClojureScript. Only some
code has same functionality. Like CIDER backend. In the future,
ClojureScript part code will increase and different. So I suggest
separate them into two source code files.
WDYT?
--
[ stardiviner ]
I try to make every word
Daniel Kraus writes:
>> The only downside is that people might need to
>> (require 'ob-clojurescript)
>> I am thinking if ob-core.el should try to automatically guess the
>> correct library to be loaded.
>
> We could just (require 'ob-clojurescript) inside ob-clojure.el ?!
Sure. Though it will
Ihor Radchenko writes:
> stardiviner writes:
>
>> For now, ob-clojure.el contains lot of code for ClojureScript. Only some
>> code has same functionality. Like CIDER backend. In the future,
>> ClojureScript part code will increase and different. So I suggest
>> separate them into two source
stardiviner writes:
> For now, ob-clojure.el contains lot of code for ClojureScript. Only some
> code has same functionality. Like CIDER backend. In the future,
> ClojureScript part code will increase and different. So I suggest
> separate them into two source code files.
>
> WDYT?
The only
For now, ob-clojure.el contains lot of code for ClojureScript. Only some
code has same functionality. Like CIDER backend. In the future,
ClojureScript part code will increase and different. So I suggest
separate them into two source code files.
WDYT?
[stardiviner] GPG key ID:
