Ihor Radchenko writes:
> Feel free to push.
I note that we now have a new compiler warning after your changes:
⛔ Warning (comp): ob-clojure.el:268:45: Warning: Unused lexical argument
‘params’
May you please take a look?
If the function argument is really unused, replace it with _ in
`ob-cloju
Hi all,
I've collected some tests about ob-haskell, using GHCi.
This patch is not ready for final review. It's a preliminary version.
These tests are about GHCi, and only about GHCi (that's why I named
the file 'test-ob-haskell-ghci.el').
Some tests are revealing bugs; they are flagged with:
Hi Ihor,
>> Bruno Barbier writes:
>>
>>> Sorry, I'm still working on adding a 'test-ob-haskell.el', when I have
>>> some spare time, but I'm unable so far to find tests that I can't
>>> reliably break.
FTR: I've opened a new thread, with a patch containing tests:
https://lists.gnu.org/arc
Bruno Barbier writes:
> All the tests will randomly fail; that is an ob-haskell bug (see
> the command 'test-ob-haskell-ghci.el' to make them fail).
First of all, thanks for the patch! Tests are especially welcome.
>From a first look, random failures appear to be related to session
initializati
Ihor Radchenko writes:
> From a first look, random failures appear to be related to session
> initialization. It appears that ob-haskell is re-using sessions even
> if :session is nil (default). And multiple session not allowed?? (I am
> looking at `org-babel-haskell-initiate-session', which igno
Hi Ihor,
Ihor Radchenko writes:
> From a first look, random failures appear to be related to session
> initialization.
My function 'test-ob-haskell-ghci' should protect against that; it
ensures the "*haskell*" buffer is always new. From what I understand,
this is an input buffering problem:
Max Nikulin writes:
>> Bummer the dash will not be supported. :(
>
> You had an opportunity to submit an alternative patch fixing regexps.
But why? We have seen such attempts already, such as
"[PATCH] Add support for $…$ latex fragments followed by a dash"
The attempts were always rejected.
Rudolf Adamkovič writes:
> The attempts were always rejected. So, just a "bummer". :)
As I said in the linked message, supporting "-" will not solve the basic
issue, which is with the Org syntax not being LaTeX. Intra-word markup,
including $...$, requires workarounds. It is the trade-off we h
On 3/11/23 10:58, Ihor Radchenko wrote:
Zelphir Kaltstahl writes:
The issue is not with defining via (define ...) inside a (let ...) in Guile. It
is about importing macros at the time, when the body of the (let ...) is already
evaluated, which is at a later phase than macro expansion. By wrapp
Hi Max,
On 2023-03-16 at 11:09 -04, Max Nikulin wrote...
> Ken, you wrote that you have other patches for ob-screen.el. Do you
> plan to sent them?
Here is the other patch. Respect custom screen command.
-k.
>From ff919de09e020fa053f5727f3b36026a3a773f88 Mon Sep 17 00:00:00 2001
From: "Kenne
On 19/03/2023 18:08, Rudolf Adamkovič wrote:
Max Nikulin writes:
You had an opportunity to submit an alternative patch fixing regexps.
But why? We have seen such attempts already, such as
"[PATCH] Add support for $…$ latex fragments followed by a dash"
I am sorry, I missed that this pat
Hi Ihor.
The heading and first lines of the table:
|---+---+-|
| NPS (~\Oslash_int pulg.) | DN (~\Oslash_int mm) | PP/PE (\Oslash_ext mm) |
|---+---+-|
| 1/8" | DN 6 | PE 10 / PP 10 |
Ihor Radchenko writes:
> I note that we now have a new compiler warning after your changes:
> ⛔ Warning (comp): ob-clojure.el:268:45: Warning: Unused lexical argument
> ‘params’
>
> May you please take a look?
> If the function argument is really unused, replace it with _ in
> `ob-clojure-eval
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 co
Hi,
You can write \(n\)-dimensional space.
On Wed, Mar 15, 2023, 02:18 Yuchen Guo wrote:
> Sometimes I encounter such texts:
>
>One of the useful features of a basis $B$ in an $n$-dimensional space
>
> When entered as-is in Org mode and exported to LaTeX, the string
> "$n$-dimensional" is e
HI
I just wanted to start a _friendly_ exchange of thought which may end
up in some code related with citations and LaTeX. (sort of my SoC :-)
)
It all starts with the support for the LaTeX '\jobname' macro. It is
quite convenient and I have been using it for a long time now. In the
'old dog don'
16 matches
Mail list logo
