vim-slime VS tmux

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.

This got me thinking about my recent pivot, my switch to Neovim by way of LazyVim to write most of my code, and using tmux to keep terminal states alive after closing a session.

I use Tmux. It's a terminal-agnostic multiplexer. Gives you persistence and automation superpowers.

https://github.com/tmux/tmux/wiki

Having a common set of tools already set up in different windows or sessions in Tmux or Zellij is obviously an option, but there is a subset of us ( 👋 ) that would rather just have fingertip access to our common tools inside of our editor.

Once you have your Mac or Linux machine ready, make sure to downlaod and install TMUX (Terminal Mulitplexer). A lot of our scripts are going to be running headless inside of a TMUX session as it's an incredibly clean way to manage and organise different workspaces simultaneously. A lot of our scripts will help us to interact with TMUX so don't worry if it looks a little intimidating at first. You can install TMUX using your package manager in the terminal, use whichever applies to you:

After having spent too much time trying to get the simple https://github.com/csdvrx/sixel-tmux/ features into mainline tmux (last November https://github.com/tmux/tmux/issues/3753), maybe it'd be easier to jump ship as use zellij?

Could anyone offer recommendations on "riced" zellij configuations, or just a demo where it shows doing with (say charts of disk usage per folder), watching a movie with mpv + keeping a vim to type on?

Well, I now use tmux and tmuxinator. I have had many failed tmux attempts over the years, but I'm firmly bedded in now.

Which leads me to clipboards. Linux has two of them! Adding to the interest, I typically use Neovim remotely, via an SSH connection to a Tmux session. And on my Linux system, I use urxvt as my terminal program. All of these are very UNIX-y tools, and somehow they all need to play nicely together.

The downside of overmind is that it requires tmux, which is a terminal multiplexer tool. If you don't already use tmux, I'd say it's probably not worth learning it just for the purposes of using overmind. But if you're like me and already know/use tmux, this can be a great solution to pursue.