Addendum to my KDevelop Post

Thu, 12 Sep 2019 00:07:50 +0000

A couple days ago, I wrote about giving KDevelop another look and posted it to reddit’s r/kde. In my post, I’d said it was annoying to have to configure the color schemas per file. Someone commented on the subreddit that if you use the View->Schema menus it’s per file while if you go into Settings->KDevelop settings you can change it for all files.

As a side effect I explored the same options in Kate and set it up like this:

Full post

Moving to KDevelop for my larger Python Projects

Mon, 09 Sep 2019 20:45:02 +0000

When I first started programming it was just at the prompt of my Tandy computer. Then it was in the QBasic text editor on the IBM computers at school. But when I started programming again with “real” languages, I ended up going with Emacs. Although I was first annoyed at the way commands like save were prefixed, it became my favorite editor. I think that was partially because of diving headfirst into the free software movement and partially because I didn’t like vi’s different modes and how annoying that made things if you didn’t realize you weren’t in the text entry mode. Eventually, I moved on to Kate because I love KDE (been running it as my main desktop for over 10 years now) and I loved the features it enabled. Also, since vi (or vim) is found EVERYWHERE while Emacs usually requires installation, I ended up switching to vi whenever I’m ssh’d into a computer. If you add plugins like powerline, it can be pretty awesome to use. Even on my desktop if I’m editing /etc/fstab I’m more likely to pull up vi than the weight of KDE (not that it takes up THAT much RAM).

Full post

Kdevelop on It's a Binary World 2.0

Addendum to my KDevelop Post

Moving to KDevelop for my larger Python Projects