|
diff --git a/content/posts/2026-01-09-vim.md b/content/posts/2026-01-09-vim.md
|
| ... |
| 200 |
makes adding new breakpoints with `:Break` just seamless. This goes for all |
200 |
makes adding new breakpoints with `:Break` just seamless. This goes for all |
| 201 |
other commands as well. You can read more about other commands with `:h |
201 |
other commands as well. You can read more about other commands with `:h |
| 202 |
Termdebug` or on https://vimhelp.org/terminal.txt.html. |
202 |
Termdebug` or on https://vimhelp.org/terminal.txt.html. |
|
|
203 |
|
|
|
204 |
## Isn't this setup a bit elaborate? |
|
|
205 |
|
|
|
206 |
Yes and no. I don't change these files much at all. When I start a new C |
|
|
207 |
project I just copy the existing one and call it a day. And any significantly |
|
|
208 |
complex project will require certain per project specific configurations |
|
|
209 |
anyway. |
|
|
210 |
|
|
|
211 |
This also makes it shareable with other people without dumping your whole setup |
|
|
212 |
on them. There are drawback like with anything else, but I have found this |
|
|
213 |
approach to be the lesser of two evils kinda think. Even Vim users can ignore |
|
|
214 |
these files by not enabling local configuration files. |
|
|
215 |
|
|
|
216 |
Like any other tool, it's on you to make your development workflow as |
|
|
217 |
frictionless as possible and no tool is perfect. |