2 ms·

I assume you're using cmake? For C/C++, cquery does completion (which I got working, but honestly didn't like and turned off. There are these two plugins for

I assume you're using cmake? For C/C++, cquery does completion (which I got working, but honestly didn't like and turned off. There are these two plugins for cmake: https://github.com/ilyachur/cmake4vim https://github.com/ilyachur/cmake4vim https://github.com/vhdirk/vim-cmake https://github.com/vhdirk/vim-cmake It would be fairly quick to put something in your vimrc to pop open a small split on the side, run a build command, and show an output. You could also probably pop open a terminal (new vim has the :term command) and maybe script that? If not cmake, it shouldn't be too difficult to replace cmake with something else. I've always found I can get better results from vim that more exactly what I want, but I've got to kind of want it and be willing to write some script to do it. The results are better, but there's more up-front investment.

godelski 7y ago
I'm more looking for a debugger rather than a compiler. Like GDB. I wouldn't call cmake or make debuggers. I have seen a few gdb plugins but at least my experience is that they are extremely wanting.
- big_chungus 7y ago
  Why not just run `:term` followed by full gdb? Doesn't seem like it's worth implementing a whole other interface.
  - godelski 7y ago
    That doesn't enable the same marking of break points and other features you typically get from IDEs. In GDB you can see multiple lines and split your screen, so I wouldn't use :term (I'll split with tmux). But other things that IDE debuggers have are like a file list (nerd tree) and display works better (off to the side). GDB technically has all these things, but it isn't formatted nicely. I use vim to be fast and efficient (and vim plugins for IDEs SUCK, plus are bloated). Do people just not use debuggers around here?
    - big_chungus 7y ago
      Fair enough; I do like the visual breakpoint interface. Honestly, that's one thing MSVC does really well: the debugger. Just curious to see why that didn't work for you. I'm assuming it's viable to implement this, I guess no one yet has.
      - godelski 7y ago
        It looks like there is a debugger in the newest vim. A little playing around with it shows some nice features. Still not quite what I want, but better than nothing.

godelski 7y ago

I'm more looking for a debugger rather than a compiler. Like GDB. I wouldn't call cmake or make debuggers. I have seen a few gdb plugins but at least my experience is that they are extremely wanting.

big_chungus 7y ago
Why not just run `:term` followed by full gdb? Doesn't seem like it's worth implementing a whole other interface.
- godelski 7y ago
  That doesn't enable the same marking of break points and other features you typically get from IDEs. In GDB you can see multiple lines and split your screen, so I wouldn't use :term (I'll split with tmux). But other things that IDE debuggers have are like a file list (nerd tree) and display works better (off to the side). GDB technically has all these things, but it isn't formatted nicely. I use vim to be fast and efficient (and vim plugins for IDEs SUCK, plus are bloated). Do people just not use debuggers around here?
  - big_chungus 7y ago
    Fair enough; I do like the visual breakpoint interface. Honestly, that's one thing MSVC does really well: the debugger. Just curious to see why that didn't work for you. I'm assuming it's viable to implement this, I guess no one yet has.
    - godelski 7y ago
      It looks like there is a debugger in the newest vim. A little playing around with it shows some nice features. Still not quite what I want, but better than nothing.