4 ms·

So I've recently got into using vim and quite like the split screen features. How would I mix something like this in for doing day to day running commands and

So I've recently got into using vim and quite like the split screen features. How would I mix something like this in for doing day to day running commands and editing stuff with a vim split screen workflow? Sorry if this seems like a difficult question, but even stories of how people manage this would be great :)

bricestacey 15y ago
I am a tmux/vim user and I find this a constant problem. Split tmux panes don't allow your vim windows to communicate with each other (you could always fallback to using the system buffer, though that is often insufficient). Yet, split vim windows don't allow a shell in a single window.
- te_chris 15y ago
  Theres actually a vim plugin I've been using that comes with Janus that loads up a shell in a vim buffer. It's been quite helpful, but I still find myself having separate macvim and terminal windows open, especially for rails dev. I normally have vim open for editing and a terminal window open with tabs for rails console, guard for rspec, server and general terminal open.
- ibisum 15y ago
  I don't use tmux, but terminator instead. Where tmux is a terminal multiplexor, terminator is .. a terminal! With amazing split-window abilities .. So I work like this: a "main window" in terminator with my vim session (in which vim administers its own windows - great with cscope integration and so on) and two sub-windows. The two sub-windows are for doing things like shell hacking on the project, another for builds, and so on. To cut/paste between the windows, when necessary, I either use tee to put things in /tmp for easy ":r"-ing in vim, or I just use the window manager clipboard. In the 'main editing window' where vim has its own windows for each file and so on, yank/paste work great - to go from shell to shell, mouse-select/mouse-middle-button work great. Debugging, you say, with line-by-line code inspection? In a sub-shell: 'gdb -tui' is awesome. I also build most of my projects such that ':make' returns a proper vim clist that can easily be easily navigated through standard vim bindings.. I don't use tmux, screen, for the simple reason that I like the flexibility that having terminator manage the windows gives .. Check it out, in case you're interested.
- JoshTriplett 15y ago
  If you want a shell in a vim buffer, try ConqueTerm: https://code.google.com/p/conque/ https://code.google.com/p/conque/ Seems to work quite well, both for simple shell-like programs and full screen-oriented commands. It does depend on a vim with Python support compiled in, but that doesn't seem like a huge constraint.
b14ck 15y ago
I use vim splits as well. I find my typical workflow is something like this: 1) Open a tmux split (vertical). 2) In the left tmux pane, open vim (and split horizontally). 3) On the right side, have my tests open and running via a watch command, eg: watch -n 10 "nosetests", or something similar.

bricestacey 15y ago

I am a tmux/vim user and I find this a constant problem. Split tmux panes don't allow your vim windows to communicate with each other (you could always fallback to using the system buffer, though that is often insufficient). Yet, split vim windows don't allow a shell in a single window.

te_chris 15y ago
Theres actually a vim plugin I've been using that comes with Janus that loads up a shell in a vim buffer. It's been quite helpful, but I still find myself having separate macvim and terminal windows open, especially for rails dev. I normally have vim open for editing and a terminal window open with tabs for rails console, guard for rspec, server and general terminal open.
ibisum 15y ago
I don't use tmux, but terminator instead. Where tmux is a terminal multiplexor, terminator is .. a terminal! With amazing split-window abilities .. So I work like this: a "main window" in terminator with my vim session (in which vim administers its own windows - great with cscope integration and so on) and two sub-windows. The two sub-windows are for doing things like shell hacking on the project, another for builds, and so on. To cut/paste between the windows, when necessary, I either use tee to put things in /tmp for easy ":r"-ing in vim, or I just use the window manager clipboard. In the 'main editing window' where vim has its own windows for each file and so on, yank/paste work great - to go from shell to shell, mouse-select/mouse-middle-button work great. Debugging, you say, with line-by-line code inspection? In a sub-shell: 'gdb -tui' is awesome. I also build most of my projects such that ':make' returns a proper vim clist that can easily be easily navigated through standard vim bindings.. I don't use tmux, screen, for the simple reason that I like the flexibility that having terminator manage the windows gives .. Check it out, in case you're interested.
JoshTriplett 15y ago
If you want a shell in a vim buffer, try ConqueTerm: https://code.google.com/p/conque/ https://code.google.com/p/conque/ Seems to work quite well, both for simple shell-like programs and full screen-oriented commands. It does depend on a vim with Python support compiled in, but that doesn't seem like a huge constraint.

b14ck 15y ago

I use vim splits as well. I find my typical workflow is something like this: 1) Open a tmux split (vertical). 2) In the left tmux pane, open vim (and split horizontally). 3) On the right side, have my tests open and running via a watch command, eg: watch -n 10 "nosetests", or something similar.