<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="/assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Gustaf Waldemarson (Emacs and Elisp)</title><link>https://gustafwaldemarson.com/</link><description>Entries relating to Emacs and Emacs Lisp and what I do with them.</description><atom:link href="https://gustafwaldemarson.com/tags/emacs.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2025 &lt;a href="mailto:gustaf.waldemarson@gmail.com"&gt;Gustaf Waldemarson&lt;/a&gt; </copyright><lastBuildDate>Sun, 11 May 2025 14:49:25 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Updated Format Specifier Highlighting in Emacs</title><link>https://gustafwaldemarson.com/posts/updated-format-specifier-highlighting-in-emacs/</link><dc:creator>Gustaf Waldemarson</dc:creator><description>&lt;div&gt;&lt;p&gt;
What feels like ages ago now, I wrote a short &lt;a href="/posts/printf-format-highlighting-in-emacs"&gt;post&lt;/a&gt; about improving the syntax
highlighting of format specifiers for &lt;code&gt;printf&lt;/code&gt; style functions (actually, all
strings). While it has worked great for a long time, it is about time to give it
a bit of a face-lift and at the same time make it even more general.
&lt;/p&gt;

&lt;p&gt;
The first item on the agenda however, is to make the original regexp,
&lt;i&gt;manageable&lt;/i&gt;. When we finished things up, we were left with the following:
&lt;/p&gt;

&lt;p&gt;&lt;a href="https://gustafwaldemarson.com/posts/updated-format-specifier-highlighting-in-emacs/"&gt;Read more…&lt;/a&gt; (3 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>elisp</category><category>emacs</category><category>printf</category><category>regexp</category><category>rx</category><guid>https://gustafwaldemarson.com/posts/updated-format-specifier-highlighting-in-emacs/</guid><pubDate>Sun, 18 Aug 2024 10:09:42 GMT</pubDate></item><item><title>Personal ELPA Archive</title><link>https://gustafwaldemarson.com/posts/personal-elpa/</link><dc:creator>Gustaf Waldemarson</dc:creator><description>&lt;div&gt;&lt;p&gt;
There's been a few times over the years when I wanted to install an &lt;code&gt;Emacs&lt;/code&gt;
package that was &lt;i&gt;not&lt;/i&gt; available on any of the common package distributers, such
as &lt;code&gt;GNU ELPA&lt;/code&gt; or &lt;code&gt;MELPA&lt;/code&gt;. Most recently I wanted to install &lt;code&gt;llvm-mode&lt;/code&gt;, but
that package have recently been removed due to the size of the &lt;code&gt;llvm&lt;/code&gt;
repository. Previously, I would have just ended up not using the package at all
or possibly adding the package to my own configuration repository if I really
wanted to use it. This time however, I decided to try to figure out what it
would take to setup your own Emacs package distribution server, and as it turns
out, with a pre-existing webserver, there's only a few file conventions that
need to be fulfilled on the host and client sides to do just that.
&lt;/p&gt;

&lt;p&gt;&lt;a href="https://gustafwaldemarson.com/posts/personal-elpa/"&gt;Read more…&lt;/a&gt; (3 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>elisp</category><category>ELPA</category><category>emacs</category><guid>https://gustafwaldemarson.com/posts/personal-elpa/</guid><pubDate>Sat, 23 Mar 2019 13:32:13 GMT</pubDate></item><item><title>Clang Format</title><link>https://gustafwaldemarson.com/posts/clang-format/</link><dc:creator>Gustaf Waldemarson</dc:creator><description>&lt;div&gt;&lt;p&gt;
I often write code in &lt;code&gt;C&lt;/code&gt; or &lt;code&gt;C++&lt;/code&gt; and frequently use &lt;code&gt;clang-format&lt;/code&gt; to
automatically format the code I'm writing. Although, occasionally I get into a
situation where I should use a different coding style while I'm in a particular
subdirectory.
&lt;/p&gt;

&lt;p&gt;&lt;a href="https://gustafwaldemarson.com/posts/clang-format/"&gt;Read more…&lt;/a&gt; (1 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>clang</category><category>elisp</category><category>emacs</category><guid>https://gustafwaldemarson.com/posts/clang-format/</guid><pubDate>Tue, 10 Apr 2018 13:32:13 GMT</pubDate></item><item><title>Set Variable in Hook</title><link>https://gustafwaldemarson.com/posts/set-variable-in-hook/</link><dc:creator>Gustaf Waldemarson</dc:creator><description>&lt;div&gt;&lt;p&gt;
I've just recently started to use &lt;a href="https://github.com/areina/helm-dash"&gt;helm-dash&lt;/a&gt; for most of my documentation
look-ups. I did however find it a bit awkward to configure. For it to work its
magic, each &lt;code&gt;major-mode&lt;/code&gt; should set &lt;code&gt;helm-dash-docsets&lt;/code&gt; to a list of strings
with the docsets it should activate. The most straightforward way that I found
to do this was this was with a small lambda in the major-mode hook.
&lt;/p&gt;

&lt;p&gt;&lt;a href="https://gustafwaldemarson.com/posts/set-variable-in-hook/"&gt;Read more…&lt;/a&gt; (1 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>elisp</category><category>emacs</category><guid>https://gustafwaldemarson.com/posts/set-variable-in-hook/</guid><pubDate>Wed, 27 Sep 2017 10:42:36 GMT</pubDate></item><item><title>Printf Format Highlighting</title><link>https://gustafwaldemarson.com/posts/printf-format-highlighting-in-emacs/</link><dc:creator>Gustaf Waldemarson</dc:creator><description>&lt;div&gt;&lt;p&gt;
Most of my work is done in either &lt;code&gt;C&lt;/code&gt; or &lt;code&gt;C++&lt;/code&gt;, so I frequently use the &lt;code&gt;printf&lt;/code&gt;
family of functions to write a wide variety of stuff to the display. Naturally,
I'd like the format specifiers to stand out from the rest of the characters in
the strings, so for the longest time I used this piece of &lt;code&gt;elisp&lt;/code&gt; code to
achieve that:
&lt;/p&gt;

&lt;p&gt;&lt;a href="https://gustafwaldemarson.com/posts/printf-format-highlighting-in-emacs/"&gt;Read more…&lt;/a&gt; (2 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>elisp</category><category>emacs</category><category>printf</category><category>regexp</category><guid>https://gustafwaldemarson.com/posts/printf-format-highlighting-in-emacs/</guid><pubDate>Mon, 27 Feb 2017 08:24:55 GMT</pubDate></item><item><title>Emacs, Elisp and Org Mode</title><link>https://gustafwaldemarson.com/posts/emacs-elisp-and-org-mode/</link><dc:creator>Gustaf Waldemarson</dc:creator><description>&lt;div&gt;&lt;p&gt;
I have a confession to make.
&lt;/p&gt;

&lt;p&gt;
I'm sort of an Emacs fanatic.
&lt;/p&gt;

&lt;p&gt;
Well, perhaps fanatic is a strong word but it &lt;i&gt;does&lt;/i&gt; reflect the manner in which
I try to integrate my whole workflow into and around it. And so far, I rarely
ever have to leave the leave Emacs or the terminal. Best of all, I almost never
have move my hand those &lt;b&gt;dreadful&lt;/b&gt; decimeters to the right to use the mouse.
&lt;/p&gt;

&lt;p&gt;&lt;a href="https://gustafwaldemarson.com/posts/emacs-elisp-and-org-mode/"&gt;Read more…&lt;/a&gt; (2 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>elisp</category><category>emacs</category><category>orgmode</category><guid>https://gustafwaldemarson.com/posts/emacs-elisp-and-org-mode/</guid><pubDate>Wed, 28 Sep 2016 20:00:46 GMT</pubDate></item></channel></rss>