From: Ihor Radchenko <yantar92@posteo.net>
To: Bruno Barbier <brubar.cs@gmail.com>
Cc: "Thomas S. Dye" <tsd@tsdye.online>,
emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Haskell code blocks
Date: Fri, 21 Oct 2022 03:10:42 +0000 [thread overview]
Message-ID: <87o7u57txp.fsf@localhost> (raw)
In-Reply-To: <notmuch-sha1-431220eef964237e131dcf36f817756f3537caf1>
Bruno Barbier <brubar.cs@gmail.com> writes:
> I've attached the patch that I've used to fix ob-haskell.
>
> Should I submit a patch for ob-haskell ?
>
> Bruno
>
>
> From f2e91a62469e84ce1d3036216ae3eca4084f3b94 Mon Sep 17 00:00:00 2001
> From: Bruno BARBIER <brubar.cs@gmail.com>
> Date: Wed, 19 Oct 2022 19:44:42 +0200
> Subject: [PATCH] org-babel-interpret-haskell: Don't remove outputs that match
> inputs
Thanks! Could you also create testing/lisp/test-ob-haskell.el file and
add your examples as tests in there?
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2022-10-21 3:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 1:16 Haskell code blocks Thomas S. Dye
2022-10-19 2:52 ` Ihor Radchenko
2022-10-19 3:50 ` Thomas S. Dye
2022-10-19 4:22 ` Ihor Radchenko
2022-10-19 4:47 ` Thomas S. Dye
2022-10-19 10:17 ` Ihor Radchenko
2022-10-19 18:03 ` Bruno Barbier
[not found] ` <notmuch-sha1-431220eef964237e131dcf36f817756f3537caf1>
2022-10-21 3:10 ` Ihor Radchenko [this message]
2022-11-07 7:24 ` Ihor Radchenko
2022-11-08 18:46 ` Bruno Barbier
2022-11-09 2:54 ` Ihor Radchenko
2023-03-13 11:38 ` Ihor Radchenko
2023-03-15 18:12 ` Bruno Barbier
[not found] ` <notmuch-sha1-86fc4270780c1f4b2624b20be5d3684ddf44d9c0>
2023-03-19 9:20 ` Bruno Barbier
2022-10-22 5:06 ` Jarmo Hurri
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o7u57txp.fsf@localhost \
--to=yantar92@posteo.net \
--cc=brubar.cs@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.online \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.