Like so many other programmers, I’ve come to love Vim. I’ve always had a deep respect for the efficiency of Vim, but it wasn’t until I combined the power of Vim text editing with the agility of CLion’s code navigation engine, that I really feel in love. Vim integrates so seemlessly with CLion that I’ve completely forgetten that it’s a plugin and not just a basic part of the tool.
Other than my command shell, CLion is the most powerful tool in my arsenal. This is first post in a series about how I found CLion and it’s most essential features for embedded C code development. In this post I talk about CLion’s most basic features, but in future posts I’ll talk about the plugins I use and more specifics to embedded code development.
Once upon a time I was lost in the world of dotfiles. I spent way too much time editing my bash profile, installing vim plugins, and tweaking my system configuration. Although it started out fun and gave me a sense of control over my system, I eventually got tired of the random bugs and incompatibility issues that naturally come with too much tweaking. Then I found yadr.
