3 ms·
That's quite funny. I've ditched the terminal for vim with split screen, for pretty much the same reason that you are using emacs - quicker to shift between she
by lelanthran 4y ago
That's quite funny. I've ditched the terminal for vim with split screen, for pretty much the same reason that you are using emacs - quicker to shift between shells and copy/paste become so much more (also, searching command history is not intuitive).
Here's my shell script for vimterm.sh:
vim -c 'call Tmux()'
And here's the relevant function from my .vimrc:
function! Tmux()
vsplit
terminal
set nonumber
wincmd j
q
wincmd l
terminal
set nonumber
wincmd j
q
endfun
- u801e 4y agoI never really set up a function for it, but what I usually do is in a new vim instance, I'll run the :term command, press ctrl-w o to make it the only window and then run a nested vim instance in that term window (typically one instance per vim tab). I'll open new terminals by running :tab :term. Basically, I'm using one instance of vim as a session manager to run other programs in, including vim itself. You can pass ctrl-w to a nested vim instance by pressing ctrl-w .
- lelanthran 4y ago> You can pass ctrl-w to a nested vim instance by pressing > > ctrl-w . Huh, never knew that; thanks :-)