Latest haskell-mode and latest ob-haskell no good together

[borgauf]

I've used ob-haskell which is dependent on haskell-mode for years. Now, however, they can't produce a working REPL buffer together. A 2018 version of ob-haskell and this latest haskell-mode will initialize upon first Haskell Babel code block run a REPL, and it has the usual buffer name *haskell* -- but it's a brain-dead zombie, i.e., nothing entered at the prompt gets evaluated. Pairing latest ob-haskell (2024) with this latest haskell-mode, however, produces no *haskell* REPL buffer. But then I can give the code block a specific REPL buffer name, e.g., :session *myhaskell* and it does create this REPL, but it too is DOA zombiefied.

As I don't expect anyone here to troubleshoot this "off-label" org-mode Babel issue, can someone simply point me to a haskell-mode from, say, a year ago?

[Hi-Angel]

As I don't expect anyone here to troubleshoot this "off-label" org-mode Babel issue, can someone simply point me to a haskell-mode from, say, a year ago?

Well, what I do when I have to frequently switch between multiple versions of some foo-mode for testing or development purposes, is I locate its dir under elpa, like ~/.emacs.d/elpa/foo-mode-VERSION, then I rm -rf it and make a symlink: ln -s ~/Projects/foo-mode ~/.emacs.d/elpa/foo-mode-VERSION.

So what you can do here is 1. Clone the repo, 2. Execute make compile to byte-compile files, 3. make the mode dir under elpa a symlink to the repo.

If you suspect what you're seeing is a regression, you could try bisecting it. Finding the problematic commit would help a lot.