<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>emacs on Exploring code</title>
    <link>https://hdyson.github.io/tags/emacs/</link>
    <description>Recent content in emacs on Exploring code</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 07 Apr 2021 20:55:35 +0100</lastBuildDate><atom:link href="https://hdyson.github.io/tags/emacs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Exploring Python Ligatures</title>
      <link>https://hdyson.github.io/posts/exploring-python-ligatures/</link>
      <pubDate>Wed, 07 Apr 2021 20:55:35 +0100</pubDate>
      
      <guid>https://hdyson.github.io/posts/exploring-python-ligatures/</guid>
      <description>&lt;p&gt;
Pycharm has some pretty ligature support.  It&amp;#39;d be good to have similar in
emacs - let&amp;#39;s take a look at how to set that up.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Selecting which python to use with org-babel</title>
      <link>https://hdyson.github.io/posts/org-babel-conda/</link>
      <pubDate>Sun, 07 Jun 2020 20:56:00 +0100</pubDate>
      
      <guid>https://hdyson.github.io/posts/org-babel-conda/</guid>
      <description>&lt;p&gt;
When working with &lt;a href=&#34;https://orgmode.org/worg/org-contrib/babel/intro.html&#34;&gt;org-babel&lt;/a&gt;, it&amp;#39;s useful to be able to select from which
environment python is run.  There&amp;#39;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&amp;#39;m a big advocate of launching emacs on
startup, and only exiting it when you shutdown your computer.  So here, I&amp;#39;ll
show how to choose the python being run within org-babel.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Making init files intelligible</title>
      <link>https://hdyson.github.io/posts/making-init-files-intelligible/</link>
      <pubDate>Tue, 15 Oct 2019 20:53:56 +0100</pubDate>
      
      <guid>https://hdyson.github.io/posts/making-init-files-intelligible/</guid>
      <description>&lt;p&gt;
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.&lt;/p&gt;
&lt;p&gt;
We can do better.&lt;/p&gt;
&lt;p&gt;
So in this post I&amp;#39;ll show you how to have a documented, human-readable emacs
configuration file.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Complete emacs setup</title>
      <link>https://hdyson.github.io/posts/complete-emacs-setup/</link>
      <pubDate>Tue, 15 Oct 2019 20:34:49 +0100</pubDate>
      
      <guid>https://hdyson.github.io/posts/complete-emacs-setup/</guid>
      <description>&lt;p&gt;
Following on from &lt;a href=&#34;https://boingboing.net/2016/09/30/finally-got-my-emacs-setup-jus.html&#34;&gt;Boing Boing&lt;/a&gt;, I finally got my emacs setup just how I like
it:&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
