3 ms·

Can't really say enough good things about Vim. I retired early as a staff software engineer because of the work I did using Vim. From hacking silly games in C i

Can't really say enough good things about Vim. I retired early as a staff software engineer because of the work I did using Vim. From hacking silly games in C in high school to now, I've always been able to use Vim and run circles around any "modern" text editor or IDE. I feel like I owe Vim as much public praise as I can give so others can reap the rewards like I did. What really frustrates me is how little people seem to want to invest in their tools, or the outright lies they tell themselves about how much configuration they need to use Vim on a daily basis. My Vim config is 200 lines, and my last commit was 3 years ago. I've invested maybe a few days of my life into configuring Vim and I use it 8-16 hours a day. Vim can do so much on its own. It has autocomplete, fuzzy finding, integration with build systems, file search, navigation using a directory browser, jump to symbol, parse compiler output to jump to bugs, support for gdb and breakpoints, a built in terminal, copy to and from the system clipboard, and with literally 8 lines of code you can get support for every linter, LSP, etc. known to man, fuzzy finding, and git integration that let's you use native git commands with seamless editor integration.

aadhavans 2y ago
Could you share your config?
nop_slide 2y ago
I've been rocking dual Pycharm w/ Vim bindings plus a neovim setup and bounce between. The only thing preventing me from going 100% neovim is Pycharm's python debugger. I have setup neovim-dap[0] with all the related plugins, it works for simple script but it bugs out and crashes when running our Flask web app. I rely heavily on the Pycharm debugger to step through our app. Have you had a good experience with setting up a debugger in vim/neovim or is that not part of your workflow? 0: https://github.com/mfussenegger/nvim-dap https://github.com/mfussenegger/nvim-dap
- toprerules 2y ago
  I don't use DAP so I can't help you there. I use vim for editing code. When I need to debug I run lldb or gdb in a separate tmux window, if I need to see the code I enable TUI mode. There are many wrappers including TermDebug, Vimspector, termdbg, etc. to add visual breakpoints, but I have never found them necessary - because again gdb/lldb can already show you the code in various formats including assembly. It sounds like you are using Pycharm in exactly the same way you can already use a standalone debugger. For Python I find a built in debugger especially unnecessary. Most interpreted languages have a debugger that can be triggered from the source code to drop into an interpreter, and Python is no exception - see pdb and breakpoint().
  - nop_slide 2y ago
    A little ashamed that I have never used pdb directly, I'm going to try to broaden my horizons and learn about it more :) Appreciate your perspective. Cheers

aadhavans 2y ago

Could you share your config?

nop_slide 2y ago

I've been rocking dual Pycharm w/ Vim bindings plus a neovim setup and bounce between. The only thing preventing me from going 100% neovim is Pycharm's python debugger. I have setup neovim-dap[0] with all the related plugins, it works for simple script but it bugs out and crashes when running our Flask web app. I rely heavily on the Pycharm debugger to step through our app. Have you had a good experience with setting up a debugger in vim/neovim or is that not part of your workflow? 0: https://github.com/mfussenegger/nvim-dap https://github.com/mfussenegger/nvim-dap

toprerules 2y ago
I don't use DAP so I can't help you there. I use vim for editing code. When I need to debug I run lldb or gdb in a separate tmux window, if I need to see the code I enable TUI mode. There are many wrappers including TermDebug, Vimspector, termdbg, etc. to add visual breakpoints, but I have never found them necessary - because again gdb/lldb can already show you the code in various formats including assembly. It sounds like you are using Pycharm in exactly the same way you can already use a standalone debugger. For Python I find a built in debugger especially unnecessary. Most interpreted languages have a debugger that can be triggered from the source code to drop into an interpreter, and Python is no exception - see pdb and breakpoint().
- nop_slide 2y ago
  A little ashamed that I have never used pdb directly, I'm going to try to broaden my horizons and learn about it more :) Appreciate your perspective. Cheers