fswatch VS vim-test

Or even better, fswatch (https://github.com/emcrisostomo/fswatch) which works on Linux, BSDs, macOS, Windows, and even Solaris

If you don’t mind shell shell scripting you can use something like fswatch and some shell logic to do something similar.

Well, I am not too lazy to search but I was interested in your experience, especially with reliability.

This one looks interesting: https://github.com/emcrisostomo/fswatch

What about using https://github.com/emcrisostomo/fswatch ?

The required kernel hooks exist in pretty much any common OS these days, it is a user-space tool that is sometimes missing.

It may not be installed by default, but inotifywait is available in common Linux distributions, usually in a package called something like ionotify-tools, and has been for over a decade-ana-half IIRC. It'll work under WSL on Windows too, though only for ext4 devices not bits of the Windows filesystem made available to Linux.

I can't speak to what other OSs include by default, but as every major OS has a different API for defining how to register a lister and how it gets messages no built-in tool is going to be cross platform. There are third party tools which present more cross-platform consistency, most notably https://github.com/emcrisostomo/fswatch#readme (also available in common Linux distros, just an apt install away in Debian for instance).

fswatch is a cross-platform file change monitor. It will watch any files you specify, then run a script on change.

You can do this without polling using a util like fswatch: https://github.com/emcrisostomo/fswatch

> It watches source files, and regenerates the OpenSCAD files automatically

inotify() is awesome. Here's a library in python that does it.

https://michaelcho.me/article/using-pythons-watchdog-to-moni...

There's also inotifywatch on linux and fswatch on mac. I'm sure there's alternatives for BSD Unix and Windows, but I care the least about those OS's.

https://github.com/emcrisostomo/fswatch

For development it's easy to just ParseFiles before every Execute to be sure you have the latest version. But for production something else is needed, fx watch for changes in files and have this trigger a reload (fx using https://github.com/emcrisostomo/fswatch).

If you need inspiration, you can use vim-test as a reference. It's the Vim equivalent of neotest, written in Vimscript (doesn't support tree-sitter and diagnostics).

My plugin NeoTerm.lua supports "run test at cursor" out of the box with vim-test, i.e. zero configuration.

Vim test is great, supports a lot of frameworks and is easy to extend (with vi script) https://github.com/vim-test/vim-test

I am trying to set up the popular vim-test (https://github.com/vim-test/vim-test) plugin so that when I run tests they run on a tmux pane. vim-test uses a default strategy of running the tests via neovim’s built-in terminal. They also support many strategies which include running on a tmux pane.

I use https://github.com/vim-test/vim-test runs tests in a lot of languages. Very fast and clean output.

vim-test run your test with a simple mapping. Works with rSpec and Minitest (and dozens other languages)

I've made the move from vim to Emacs with Evil-mode for a little while now, but still miss https://github.com/vim-test/vim-test. I wonder if there's a port for evil-mode or if you know of something closer to it you can recommend. Thanks

One project that does a fantastic job on these two points is https://github.com/vim-test/vim-test Both adding new execution environments and test-runners can be done with minimal fuzz. Only thing is I would like a tutorial of how to add a new runner.