- https://gitlab.gnome.org/swilmet/vim-swilmet-config (main vimrc with git submodules for plugins)
- https://gitlab.gnome.org/swilmet/vim-easy-c (a new plugin)
- https://gitlab.gnome.org/swilmet/vim-gtk-doc-comments (a plugin that I’ve improved)
Of course there are alternatives to Vim to develop in C with GLib (Builder, Anjuta, VS Code, Emacs, etc).
It’s more for developers who have already learned Vim and would prefer to keep it. Especially newcomers who want to leverage what they already master instead of needing to learn new tools and new workflows.
BTW, it’s the kind of things that I’ve not seen a lot, GNOME developers sharing their Vim or Emacs config, or whatever else.
(Note, this might be silly if you know that I’ve contributed quite a bit to gedit, GtkSourceView etc, but traditionally I’ve always used Vim to develop in C, and used gedit for example for Vala for which there was a good plugin, gnome-latex for LaTeX, and now gedit for basically everything else than C).
(Note also, I’m aware that Builder has a Vim mode too, but I suppose that the Vim mode of Builder is not as powerful as Vim itself, and an IDE is not the taste of everybody).
feel free to copy some chunks, or even use a whole plugin or even copy most of my main vimrc.
And if you know other life-changing Vim plugins when developing in C with GLib, don’t hesitate to share