INim VS nvim-treesitter-textobjects

- `nim secret`[0]: code is interpreted with Nim's vm, it is limited to compile-time (e.g. no C/C++).

- `nlvm r`[1]: nlvm backend supports JIT compilation and repl-like interface was added in latest release.

- `inim`[2]: supports all nim code, but it's not really a true repl. It adds code to a file and recompiles it (you can see the source file with `ctrl+x`). I'd recommend to use it with clang compiler, because it's a bit faster than gcc in my experience. It's the best option right now. And I use it almost daily.

First two options have rudimentary input system. But you can get command history and left-right navigation by wrapping them with rlwrap (should be preinstalled on most *nixes): `rlwrap nim secret`, `rlwrap nlvm r`.

There are plans to support incremental compilation for the next Nim release (it is currently broken). That would improve inim and other repls experience significantly.

[0]: https://nim-lang.org/docs/manual.html#restrictions-on-compil...

[1]: https://forum.nim-lang.org/t/10697

[2]: https://github.com/inim-repl/INim

Go must be terrible to google too! Nim's easy to google though, it's how I got to rust really. I'm actually the maintainer of inim, the nim repl: https://github.com/inim-repl/INim

I was hoping to use nvim-treesitter-textobjects to jump to the next argument via something like this:

You want to look at nvim-treesitter-textobjects. It let's you define keymaps for navigating text objects defined by treesitter and you can also use them with commands like d, c and so on.

Thank you! It looks like nvim-treesitter-textobjects is a good plugin to start with:

https://github.com/nvim-treesitter/nvim-treesitter-textobjec...

I'm aware of nvim-treesitter-textobjects and I suspect my answer lies in this plugin, but is there a way to move between root nodes that is agnostic of the node type?

Thanks! I just started using https://github.com/nvim-treesitter/nvim-treesitter-textobjects, and it works as a charm.

nvim-treesitter-textobjects

In this case, reading here is probably a good start: https://github.com/nvim-treesitter/nvim-treesitter-textobjects

Have a look at https://github.com/nvim-treesitter/nvim-treesitter-textobjects. Set up the @block.inner and @block.outer textobjects and it should work.

nvim-treesitter-textobjects lets you jump to (for instance) functions more accurately than with a regex-based approach using ]f

Or even better, one can use nvim-treesitter-textobjects. It already provides function/class selection and go-to functionality out-of-the-box.