You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
install https://github.com/tpope/vim-pathogen into ~/.vim/
install https://github.com/jpalardy/vim-slime into ~/.vim/bundle
copied default vimrc to a user copy: cp /etc/vimrc ~/.vim/vimrc
added the following to the end of ~/.vim/vimrc
" vim slime
let g:slime_python_ipython = 1
let g:slime_target = "tmux"
let g:slime_paste_file = "$HOME/.slime_paste"
" Pathogen load
filetype off
call pathogen#infect()
call pathogen#helptags()
filetype plugin indent on
Open a new tmux session with name "default"
tmux new -s default
Create a new (vertical) pane. Panes are referenced by [window num].[pane num]. In a new tmux session, the first window and pane is 0.0. The second will be 0.1. If I create a new window and pane, it will be assigned 1.0.
Let's assume I stay in window 0 and create a new pane 0.1. In pane 0.1, start up desired program e.g. using ipython on a linux box e.g.
One preps a fresh vim session to send to the REPL pane by hitting < ctrl-c, ctrl-c >. For example, assume in original pane 0.0 I open a script using vim to send to REPL pane 0.1. Hitting < ctrl-c, ctrl-c > in vim pane 0.0 initiates a prompt at the bottom of vim to name the session (default) and the target pane (0.1). That is, if coding with vim in pane 0.0 with the intention to send code to pane 0.1, I would see the following at the bottom of my vim session:
tmux socket name or absolute path: default
tmux target pane: 0.1
From now until the vim session is close (:wq), hitting < ctrl-c, ctrl-c > will send the current BLOCK (not line) of code. Again, BLOCK of code, NOT LINE of code.