Re: 1 character fix to make ob-haskell compatible with table outputs

2023-03-22 Thread Ihor Radchenko
ParetoOptimalDev via "General discussions about Org-mode." writes: > Oh, great to hear it's fixed! Sorry, I was not clear. I do not know if the bug existed to start with. I just cannot reproduce on the latest main, which can be for many reasons, starting from me misunderstanding the bug, or

Re: 1 character fix to make ob-haskell compatible with table outputs

2023-03-21 Thread General discussions about Org-mode.
Oh, great to hear it's fixed!

Re: 1 character fix to make ob-haskell compatible with table outputs

2023-03-15 Thread Ihor Radchenko
ParetoOptimalDev via "General discussions about Org-mode." writes: > For something like: > > name:tbl > #+begin_src sh > echo -e "1\t2\t3" > #+end_src > > #+RESULTS: > | 1 | 2 | 3 | > > #+begin_src haskell :var table=tbl > print table > #+end_src > > #+RESULTS: > | 1 | 2 | 3 | > > Whereas before

1 character fix to make ob-haskell compatible with table outputs

2023-03-14 Thread General discussions about Org-mode.
Just change the `[` and `]` to `(` and `)` respectively. List of lists aren't parsed correctly by ob-haskell, but tuples of tuples are. That means this code change I just tested works: (defun org-babel-haskell-var-to-haskell (var) "Convert an elisp value VAR into a haskell variable. The