Jonathan Palardy

Hi @pinggit The `g:slime*` variables bootstrap the config when first invoked. Afterward, the config is copied to `b:` variables and cached. Try `:unlet b:slime_config` and check if that helps matters

Hi @brucejuz You can try the `&ft` (filetype) variable, which reflects the type of file vim thinks you've got open. Let me know how that goes 👍

Hi @pinggit Have a look at [this binding](https://github.com/jpalardy/dotfiles/blob/main/vim/plugins.vim#L28) from my dotfiles. ctrl c, enter -- send the current paragraph and moves the cursor past it. You can modify to accommodate...

They are both [defined here](https://github.com/jpalardy/vim-slime/blob/main/plugin/slime.vim#L12-L13).

Hi @newptcai I don't use kitty myself, so I don't know if this changed. 🤔 Would you be willing to open a documentation PR for this? cc @mdzhang @xiangpeng2008

Hi there, This has been opened for a few weeks ^ Can someone open a PR with their recommended/udpated kitty config?

hi @Barzi2001 Thank you for opening the separate issue for this ^ It's a new day, and I have new ideas: - did you try reducing your config to a...

whoah…

hi @konradzdeb Thanks for reporting this ^ I'll have a look tonight and report back.

hi @konradzdeb I re-read this and nothing jumps at me. Can you try another target, preferably tmux? Let's try to isolate what works and what doesn't. If you have a...