Technotales

I love this hack for hitting C-c C-c in vim and having your current paragraph telegraphed to whatever screen window you want. I imagine it'd work for demos just as well as developing bash scripts. http://technotales.wordpress.com/2007/10/03/like-slime-for-vim/

> Git Diff with Vimdiff https://technotales.wordpress.com/2009/05/17/git-diff-with-vimdiff/

I tried using slimv as well some time ago but I never managed to get it working properly. I don't remember exactly what happened but I believe there were some bugs (like the lag you mention) and I couldn't figure out how to properly transfer just the piece of code I wanted to the repl. Plus I didn't want most of the plugins that slimv added (paredit for instance). I ended up using this method http://technotales.wordpress.com/2007/10/03/like-slime-for-vim/ instead. I put just the basic functions into a plugin and that has been enough for me ever since. I use it for lisps though, not haskell.

Since the blog isn't taking comments, posting it here. > doesn't work very well with is Python, because it preserves whitespace when it moves the code over the REPL. If that's the only issue, it's easy to fix it. All you need to do is to replace multiple new lines with single new line. let s:foo_text = substitute(a:text, '\n\s*\n\+', '\n', 'g') . "\n" Here is my slightly modified slime.vim: http://gist.github.com/589934 I have been using it on Ubuntu with vim and IPython and it seems to work fine. When I started using slime.vim for Python, I ran into whitespace issue and Jonathan(slime.vim developer) resolved it when I asked him on his blog. http://technotales.wordpress.com/2007/10/03/like-slime-for-vim/ You can search for Rahul in the comments.

The manpage for screen should tell you how to send commands to the screen session (the -X option, I believe). You just need to create a function/binding in Vim that tells screen to create a new 'window' and run that test suite in that 'window.' Screen is basically a terminal multiplexer. This would work a little differently if you were using gVim instead of Vim (from within the same screen session that you're sending the test suite command to). If you were using gVim you'd need to use a named screen session (the -S option) and send the screen command to the named session (and possible have logic in the Vim/gVim function to start a named session if one doesn't already exist). Then you'd need a separate terminal window attached to that screen session to view the test suite output. Do a search for vim and REPL or SLIME for articles like this: http://technotales.wordpress.com/2007/10/03/like-slime-for-vim/ These articles use the vim+screen combo to send commands to an interpreter, but you can use the same concepts to send your test suite to a screen session.

I think if you only want to see how wizards do it, you'll have to fully master emacs. As a non-wizard and vim-forever guy, who only occasionally writes Clojure for hobby projects, here's my advice. For a long time I got by with creating a split-screen terminal with 'screen', and then used vim-slime (https://technotales.wordpress.com/2007/10/03/like-slime-for-vim/). It doesn't have to be split, I just like it that way, but the idea is you have essentially two views talking to the same screen session. In one you launch a repl (with lein, or even a ruby/python repl if you want) and on the other half you open vim and type things like ctrl+c etc. to send fragments from vim to the repl. More recently I've been using slimv (https://kovisoft.bitbucket.io/tutorial.html and https://github.com/kovisoft/slimv -- and if you want my three vimrc prefs http://pastebin.com/VjwrEJJQ) after using it for Lisp, which uses swank, and found I could also do some of this for Clojure's repl (https://github.com/technomancy/swank-clojure). Unfortunately it's kind of outdated, that's not where the community is going (and I haven't really bothered to figure out exactly where that is, though that project's readme gives hints, nor have I really tried Fireplace recently enough to say if I still dislike it). But it works for me, for now, unless I want to use ClojureScript. I'd say give it a shot, you might like it.