Exploring code

This is the first of three opinionated posts on building a better keyboard.

1. Why? This post will cover both what's wrong with most keyboards, and why I opted for a Corne keyboard.

2. Hardware. The next post will discuss actually building the keyboard.

3. Software. The final post will cover configuring the software to suit my needs.

Pycharm has some pretty ligature support. It'd be good to have similar in emacs - let's take a look at how to set that up.

When working with org-babel, it's useful to be able to select from which environment python is run. There's the obvious brute-force approach - activating the appropriate environment before launching emacs - but quitting and restarting emacs is a lot of hassle if you need to change the environment in a running emacs. Besides, I'm a big advocate of launching emacs on startup, and only exiting it when you shutdown your computer. So here, I'll show how to choose the python being run within org-babel.

It's not obvious (to me, anyway) how to use hugo cross-reference links with org-mode format posts. This very short post gives an example of how to do so.

Now to add some comments to this blog. Utterances looks promising. It uses github issue comments to provide the commenting infrastructure, so should be easy to setup.

A quick summary of deploying this Hugo generated site to Github pages (and hence hdyson.dev) via the instructions from the Hugo docs.

One of the issues with an editor as configurable as emacs is that an emacs .init.el file ends up an unmaintanable mess of barely understood code snippets, duplicate and contradictory settings, and a treasure trove of forgotten knowledge.

We can do better.

So in this post I'll show you how to have a documented, human-readable emacs configuration file.

Following on from Boing Boing, I finally got my emacs setup just how I like it:

I like the look of the Beautiful Hugo theme, so let's see how easy it is to setup.