I use vim-sexp (custom fork), the sexp for humans thing from tpope, a custom form of vim-racket, and my simpl plugin (which recently got racket support).

I use vim-racket and kitty, and run raco make -v (or raco setup -Dmv --pkgs my-project && raco test -p my-project if I have it in a package) a lot.

For vim, I have heard some people use lexima.vim instead of the guns/vim-sexp

I mostly use Emacs now though, so not sure what the benefits are for one plugin over another

BTW, for vim-sexp, I couldn’t get the Alt key mappings working

@ben.knoble Do you have a good solution for making the Alt (Meta) key work in Vim?

I have seen you around the vi stack exchange (you’re a moderator?) a lot so I have the preconceived notion you know everything about Vim lol.

I don’t use mappings with alt keys :) theoretically it works in gvim or in terminal vim with some xterm modifyOtherKeys thing, but again, I don’t use them. For sexp, there’s tpope’s sexp mappings for humans which are far more “vim”

And yeah, I moderate on http://vi.stackexchange.com\|vi.stackexchange.com (I wish the http://vi.se\|vi.se shortlink worked everywhere), but I have a long way to go to learn everything! Mostly I like the :help and I try to avoid plugins that do too much or don’t fit in well with what I feel like vim is, very personal, lol

I see, yeah. The http://vi.se\|vi.se shortlink takes me to some non-English site unforunately

Yeah, on stackexchange sites stuff like [<http://vi.se\|vi.se>] gets a magic link in comments.

It can be made to ^^ but again I don’t tend to use it

With Caps Lock as a Ctrl key and Space as my leader, I use those more often

Yep, I have the same mappings (except I still have Caps Lock mapped to Escape instead of Ctrl)

Have you tried out Emacs? Emacs has an incredibly good vi emulation layer called evil

It is light years ahead of similar vim emulation layers on VSCode, for example

I don’t use Emacs without evil

Ive heard about it so many times. Ive also heard you have to spend a fair amount of time making plugins work with it? And I’m not quite ready to port my very large vim config to emacs

Well, I think I would just start with the basics first. Obviously it will take some time to get comfortable and have a suitable setup. It is certainly worth a try I would say. Things like vim-sexp exist because of Emac’s paredit mode

paredit mode is so powerful when dealing with lisps, it’s difficult to describe

Anyway, yeah, I don’t believe in the whole editor war thing, but if you want to work with Lisps, I would definitely give Emacs a try

Btw, the Alt key works in Neovim.

@ben.knoble do you use #lang? how do you load it in your repl?

@samdphillips that does not fully leverage a repl driven development does it?

Simpl supports the racket filetype; you would need to write support for other filetypes (vim-racket purports to support setting filetype based on #langs, but so far my fork does a bit better). It’s not hard to add extra support, though. Tbh my fork is a work in progress, and I’m not writing enough racket to make all the changes I need to make rn (ie they arent a priority).

I presume one could use racket -l ... -i or whatever the right command is for other langs

REPL driven development is kinda overrated tbh

(for me at least)

REPLs are only really useful when you want to try out a small example

But yeah

I do think some users have a workflow that allows copy-and-paste of code between REPL and editor and that works as a kind of REPL driven development, but that has never really worked for me.