4 ms·

I had no idea Vim had a terminal mode with ':ter|:terminal'! Definitely something I'll look into to improve my own Vim + Git workflow. I've usually just moved V

by usrme 2y ago

I had no idea Vim had a terminal mode with ':ter|:terminal'! Definitely something I'll look into to improve my own Vim + Git workflow. I've usually just moved Vim to the background with Ctrl+Z, done my committing, and then moved Vim back to the foreground with 'fg'.

lelanthran 2y ago
I tend to use it as `:vert terminal`, then start up mysql/psql in that terminal, and use <C-c> in the other pane to send SQL statements to the 'terminal'. Works better than MySQL workbench and other things like that, for me, because it works in a terminal over ssh too.
kmarc 2y ago
I found that once you use tmux+vim, the built in terminal is not much of use, it's even slowing me down
- mythrwy 2y ago
  I don't even use tmux. I just have multiple tabs open in the terminal (usually gnome terminal but I suppose others would work) and toggle back and forth with keyboard shortcuts. I usually develop full stack so will have a front end tab (with multiple Vim buffers), a backend tab (again with multiple buffers), dev servers, a database sql tab (if needed) and a command line tab to grep and git and whatever else. Might sound kind of awkward but it's muscle memory by now and blazing fast for my use case. The one thing I have not figured out yet is how to cleanly integrate AI tools into my workflow. A lot of cutting and pasting which feels very clumsy. I don't want to give up Vim nor my basic workflow. I never used co-pilot just GPT.
  - sejje 2y ago
    One main difference with tmux is that I can script the startup of my "tabbed terminals", and I can background the whole project and switch to another one (a new tmux session is akin to a new desktop workspace full of your tabbed terminals). I used to use your setup, and I was fast. But tmux is much better. (I'm also a full-stack dev btw) Another advantage, I can ssh into the server, start a tmux session, and work there the same way I do on my local. Doing that your way would require a lot of ssh sessions. > The one thing I have not figured out yet is how to cleanly integrate AI tools into my workflow https://github.com/Aider-AI/aider https://github.com/Aider-AI/aider
    - mythrwy 2y ago
      Thanks. Checking Aider out!
      - sejje 2y ago
        No problem. I think aider is not just the terminal-nerd goto here, but I believe it's the best tool for programming with LLMs. It fits your ergonomics, though. Tips: use `/ask` if you don't want it to make changes, and try to use it for small incremental commits, instead of broad sweeping changes. That may change soon with these reasoning models, though. It's also good for writing shell commands.
  - kmarc 2y ago
    As for AI, I use codeium and vim-ai. Codeium has upstream vim support, which is excellent, however the chat functionality is very basic, clumsier than in vscode, but good enough for my use case. I expect things will improve.
troyvit 2y ago
Holy cow same! I use lazygit as my VC tool and now I can just open it in a pane next to vim to make it simpler to interact with git while I'm coding. Been using vim for way to long to have missed this.

by usrme 2y ago

lelanthran 2y ago

I tend to use it as `:vert terminal`, then start up mysql/psql in that terminal, and use <C-c> in the other pane to send SQL statements to the 'terminal'. Works better than MySQL workbench and other things like that, for me, because it works in a terminal over ssh too.

kmarc 2y ago

I found that once you use tmux+vim, the built in terminal is not much of use, it's even slowing me down

mythrwy 2y ago
I don't even use tmux. I just have multiple tabs open in the terminal (usually gnome terminal but I suppose others would work) and toggle back and forth with keyboard shortcuts. I usually develop full stack so will have a front end tab (with multiple Vim buffers), a backend tab (again with multiple buffers), dev servers, a database sql tab (if needed) and a command line tab to grep and git and whatever else. Might sound kind of awkward but it's muscle memory by now and blazing fast for my use case. The one thing I have not figured out yet is how to cleanly integrate AI tools into my workflow. A lot of cutting and pasting which feels very clumsy. I don't want to give up Vim nor my basic workflow. I never used co-pilot just GPT.
- sejje 2y ago
  One main difference with tmux is that I can script the startup of my "tabbed terminals", and I can background the whole project and switch to another one (a new tmux session is akin to a new desktop workspace full of your tabbed terminals). I used to use your setup, and I was fast. But tmux is much better. (I'm also a full-stack dev btw) Another advantage, I can ssh into the server, start a tmux session, and work there the same way I do on my local. Doing that your way would require a lot of ssh sessions. > The one thing I have not figured out yet is how to cleanly integrate AI tools into my workflow https://github.com/Aider-AI/aider https://github.com/Aider-AI/aider
  - mythrwy 2y ago
    Thanks. Checking Aider out!
    - sejje 2y ago
      No problem. I think aider is not just the terminal-nerd goto here, but I believe it's the best tool for programming with LLMs. It fits your ergonomics, though. Tips: use `/ask` if you don't want it to make changes, and try to use it for small incremental commits, instead of broad sweeping changes. That may change soon with these reasoning models, though. It's also good for writing shell commands.
- kmarc 2y ago
  As for AI, I use codeium and vim-ai. Codeium has upstream vim support, which is excellent, however the chat functionality is very basic, clumsier than in vscode, but good enough for my use case. I expect things will improve.

troyvit 2y ago

Holy cow same! I use lazygit as my VC tool and now I can just open it in a pane next to vim to make it simpler to interact with git while I'm coding. Been using vim for way to long to have missed this.