I’ve never been too pleased with the default behaviour of Backspace during
isearch. If the last key you hit was C-s, then it does the same as C-r
(albeit with less repetition), and if your match failed several characters ago,
you need to hit it that many times to get back on track. Fortunately, asmeurer
took the time to phrase this problem I barely realised I had.
SX.el, the awesome Emacs client for the StackExchange network, has been stable and happy for many months now, and it’s about time I mentioned it here. We have put considerable effort into making the interface intuitive, teaching you how to use it without the need for explanations. In fact, it would probably be a disservice to the package for me to post a tutorial, so I won’t just yet. Instead, I’ll just urge you to give it a try. [...]
Cluttered as our keyboards are with key-binds, it's always nice when we can combine two disjoint functionalities in the same key. I have M-k and C-M-k bound to killing the next and previous sexp, respectively, but that is never something I need inside a string or when typing a file name in the minibuffer. Then these keys become utterly useless! [...]
Over the last couple of weeks, I’ve been working on a Clojure debugger for Cider that is strongly inspired by Edebug. Stepping trough code of any form and injecting values into running code are the features available in this first release. [...]
Thanks to Nicolas Petton, Emacs is getting a new built-in sequence library in 25.1, and it’s already available on GNU Elpa for everyone. There’s not much to be said about this besides the obvious “it’s about time”. [...]
Did you know you can fetch Github pull requests with git by adding a
remote.origin.fetch configuration? That insightful tip is a courtesy of Oleh
at (or emacs, a very active blog that has a habit of unbalancing parentheses
wherever it goes). I like the tip so much I wanted to add something to it.
Instead of manually adding that line to you
.git/config file, why not have
Magit do that for you?
After adding asynchronous operations to Paradox, I saw the need to provide some visual feedback to the user. In the simplest sense, this could be a fixed message on the mode-line, such as “Upgrading…” or “Working”, but this is not enough. I needed movement. Movement implies something is ongoing. It catches your eye and gives you that subconscious reassurance that progress is being made. A tiny spinning wheel, hourglass, or rainbow is enough to sooth all your doubts, unerringly restoring your confidence on the software and those who made it. [...]
Now that you’ve started your journey on the Typography Express by using round double quotes, take a seat and extend that to your apostrophes as well. This snippet binds a round apostrophe to the ' key, but also inserts a pair of single round quotes with a prefix. [...]
Almost every directory I work with, is either directly under “~/Dropbox/” or
under “~/Dropbox/Work/”. However, I never actually visit these two directories,
only the directories inside them. The number of possible targets for
is approaching the outer borders of two-digit land, so there's no hope for my
brain to remember registers for all of these.
I've just released Paradox version 2.0. If you've been following the blog, you already know this features the ability to do background upgrades. Below is a list of other features. [...]
After the previous post, I got in touch with the nice fellas at emacs-devel about including comment-line in Emacs. Understandably, there was a wee bit of concern with using up one of the oh-so-important C- binds, so it's been put under C-x C-; for now. [...]
Paradox has had this feature for a while, but I've never blogged about it. When you're in the Packages Menu, and you're about to upgrade your packages with the always reliable U x, do you ever wonder what's actually changed in them? When I do it, there's usually something between 5 and 20 of them just waiting for me to answer y, but rarely do I see any actual difference in the new versions. [...]
When your computer is feeling slow and you decide to upgrade it, where do you start? You start by finding the bottleneck, of course. That awesome CPU won't do you any good with crappy RAM disk. The same logic holds for your coding skills. [...]