racket-gui-easy VS vim-slime

Looks like you're already in Emacs. I strongly recommend racket-mode as mentioned in another thread.

With regard to prototyping GUI's I'd suggest taking a look at https://github.com/mfelleisen/7GUI. https://github.com/Bogdanp/racket-gui-easy could also be a good place to start.

With regard to Racket more generally, I'm probably not the best person to ask since I had a very high friction start where I just banged my head against the wall until things made sense.

I took a similar approach in my Racket library, gui-easy[1,2]. Though I opted to not defer any computations, any observable (similar to a signal from the post) update propagates to observers immediately, and there's no incrementality -- observables are just boxes whose changes you can subscribe to. Regarding the disposal problem, I used weak references and regarding the where to take observables and where to take concrete values as input question, I decided that any place an observable can go in, a concrete value can as well and it's been a convenient choice so far. For fun, here's an example[3] that builds the todo UI from the post.

[1]: https://docs.racket-lang.org/gui-easy/index.html

For native apps, I would devote coding resources to the Guile-GI project which generates Guile bindings to the cross-platform Gtk C library by way of the Gnome Object Introspection and Reflection library. I would also port the Racket gui-easy library over to Guile-GI so declarative GUIs could be written.

There is also gui-easy a declarative gui framework: https://docs.racket-lang.org/gui-easy/index.html

It’s not the only version either

See https://github.com/Bogdanp/racket-gui-easy/tree/master/examp...

  },

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.