ghcid VS vim-slime

You can use ghcid. It compiles the code, and shows if there are any errors as you save your file. Have two terminals. One for editing your file...other one with ghcid ($ ghcid path/to/filename.hs). Right click on the ghcid terminal and click `always on top`. That way, It will be always visible as you are typing and saving code.

With a combination of ghcid, an hiedb filewatcher and the -fdefer-type-errors flag you can get pretty solid IDE behavior. Currently only ghc 9.4.4 is supported but happy to personally help people set this up if interested!

With an editor integration, you could rig it up to where you could right-click on a Spec, choose "Run spec" from a context menu, and have your editor add that comment to and save dev.hs. Another editor integration could read and parse the contents of ghcid.txt. We have this already for the compiler output, but it doesn't yet parse the test output. But sans an editor integration, you will still see the test output in the console where Ghcid is running.

Sounds like you want ghcid. You can use it run tests on a successful build, and it will watch files in your project and quick-rebuild when there are changes. There shouldn't be any need to modify your Cabal files or test dependencies.

In addition, for Haskell, I usually have ghcid running, which likewise re-runs on every file change, but gives faster feedback about any type errors than the full compiler, and also is configured to evaluate

Have you looked into ghcid? https://github.com/ndmitchell/ghcid

VS Code + Haskell extension is usually best, but ghcid is an alternative which is much simpler, easier to set up, less pretty and powerful but still pretty easy and effective to use. Here's a workflow:

In general, though, I recommend just looking at the cabal files for various libraries and executables. Something like ghcid is good, since it contains a library, an executable, and a test suite.

you should also checkout the ghci vim plugin https://github.com/ndmitchell/ghcid/tree/master/plugins/nvim

https://github.com/jpalardy/vim-slime

you can have a REPL in nvim/vim/tmux/screen/another terminal/or any other window , and send regions from your vim buffer to that repl

For vim users, check out vim-slime[1]. It's really changed my workflow! It can work for any language that uses a REPL, including bash/shell. Combined with tmux, it is an amazing and (in hindsight) obvious tool. I honestly can't imagine myself going back to not having it now.

[1]: https://github.com/jpalardy/vim-slime

For splitting the terminal you could try either toggleterm or tmux. If you want to send things from one tmux pane to another, then you can use slime. For a toggle-able filetree, you can use nvim tree.

I use vim-slime. It works really well in tmux. https://github.com/jpalardy/vim-slime. Just blocks of code as cells

This is yet another plugin to capture text from the current buffer and send it to a tmux pane. I was using https://github.com/jpalardy/vim-slime previously, and wished I could just set sensible defaults for where to send text. Also, I wanted to create my first Neovim plugin! I have to say, after writing a bit of Vimscript in the past, the Neovim Lua API makes me a much happier camper.

I use slime (which sends code to tmux panes), tmux (of course) and ipython for this. For example, the code I sent to ipython was with a simple keybinding ...

If I understand correctly, what you need is a combination of vim, tmux, ipython and vim-slime.

REPL??? Do you have a very-easy-to-use way of running and testing your code? From vim-slime to nvim sniprun to autocommands with the built in terminal, to an external repl like ptpython (for python obviously). iron.nvim and conjure are two other neovim repl plugins. There are many ways of running the code that you're working on, and having something that makes this really easy for you is pretty essential. (sometimes I use inotifytools on linux to literally just run the script every time I save it.)

For the record/list, there's also: - https://github.com/hkupty/iron.nvim and - https://github.com/jpalardy/vim-slime

However, if you're coding in an interpreted language like python, R, bash, etc., then there is one plugin which you are likely to find helpful. That's vim-slime.