<?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>Dzu's Blog (Einträge über emacs)</title><link>https://blog.lazy-evaluation.net/</link><description></description><atom:link href="https://blog.lazy-evaluation.net/de/categories/emacs.xml" rel="self" type="application/rss+xml"></atom:link><language>de</language><copyright>Contents © 2025 &lt;a href="mailto:dzu@member.fsf.org"&gt;Detlev Zundel&lt;/a&gt; </copyright><lastBuildDate>Wed, 10 Dec 2025 16:11:12 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Using languagetool with a local server</title><link>https://blog.lazy-evaluation.net/de/posts/linux/languagetool-local.html?pk_campaign=feed</link><dc:creator>Detlev Zundel</dc:creator><description>&lt;div&gt;&lt;div style="text-align:center" class="imageblock" id="orgc8bd528"&gt;

&lt;div id="org71699b0" class="figure"&gt;
&lt;p&gt;&lt;img src="https://blog.lazy-evaluation.net/de/images/language-tool-logo.png" alt="language-tool-logo.png" title="Big lock" align="middle" width="150"&gt;
&lt;/p&gt;
&lt;/div&gt;

&lt;/div&gt;


&lt;p&gt;&lt;a href="https://blog.lazy-evaluation.net/de/posts/linux/languagetool-local.html?pk_campaign=feed"&gt;Weiterlesen…&lt;/a&gt; (4 min verbleiben zum Lesen)&lt;/p&gt;&lt;/div&gt;</description><guid>https://blog.lazy-evaluation.net/de/posts/linux/languagetool-local.html</guid><pubDate>Thu, 03 Apr 2025 23:00:58 GMT</pubDate></item><item><title>Orgmode And Tikz Diagrams</title><link>https://blog.lazy-evaluation.net/de/posts/orgmode-tikz.html?pk_campaign=feed</link><dc:creator>Detlev Zundel</dc:creator><description>&lt;div&gt;&lt;div id="orgcc92790" class="figure"&gt;
&lt;p&gt;&lt;img src="https://blog.lazy-evaluation.net/de/images-generated/ob-tikz-example.svg" alt="ob-tikz-example.svg" class="org-svg"&gt;
&lt;/p&gt;
&lt;/div&gt;

&lt;p&gt;
Of course it is easy to include a diagram with a post, but the
standard procedure to create/edit the diagram with an external GUI
tool does not resonate with me.  Even back in my diploma thesis I fell
in love with Donald Knuth's &lt;a href="https://en.wikipedia.org/wiki/MetaPost"&gt;MetaPost&lt;/a&gt; system to describe diagrams
in a declarative way and let the tool do the drawing.
&lt;/p&gt;

&lt;p&gt;
For some &lt;a href="https://latex-beamer.com/quick-start/"&gt;LaTeX Beamer&lt;/a&gt; presentations I used &lt;a href="http://ditaa.sourceforge.net/"&gt;ditaa&lt;/a&gt; in the meantime but
inside a &lt;b&gt;make&lt;/b&gt; flow that took care of the dependencies.  The diagrams
and the presentation were strictly separated.  For the blog posts I
did not yet have a good solution, until I switched to blogging in
orgmode.  Compared to ReST and Asciidoc posts, Emacs orgmode provides
a much richer ecosystem with lots of hooks into other systems by means
of the &lt;a href="https://orgmode.org/worg/org-contrib/babel/"&gt;org-babel&lt;/a&gt; system.
&lt;/p&gt;

&lt;p&gt;
So by switching the post source format, blogging in orgmode should
actually hook into e.g. Graphviz out of the box.  And indeed with a
little fine tuning, this is an amazingly elegant way to include
visualizations in the posts.
&lt;/p&gt;

&lt;p&gt;
As org-mode (through exporting to LaTex Beamer) has also become the
source format of my presentations, this new freedom easily extends
into presentations and even regular PDF documents by exporting to
LaTeX only.  So the means shown here to produce diagrams for the blog
are also usable when you want to generate Beamer presentations or
LaTeX documents.  As we will see, the choice of output formats is
linked to the targeted use-case.
&lt;/p&gt;

&lt;p&gt;&lt;a href="https://blog.lazy-evaluation.net/de/posts/orgmode-tikz.html?pk_campaign=feed"&gt;Weiterlesen…&lt;/a&gt; (1 min verbleiben zum Lesen)&lt;/p&gt;&lt;/div&gt;</description><guid>https://blog.lazy-evaluation.net/de/posts/orgmode-tikz.html</guid><pubDate>Thu, 20 Mar 2025 20:38:34 GMT</pubDate></item><item><title>Inline Diagrams in Orgmode</title><link>https://blog.lazy-evaluation.net/de/posts/orgmode-diagrams.html?pk_campaign=feed</link><dc:creator>Detlev Zundel</dc:creator><description>&lt;div&gt;&lt;div style="text-align:center" class="imageblock" id="org01d9b7f"&gt;

&lt;div id="orgc4fb143" class="figure"&gt;
&lt;p&gt;&lt;img src="https://blog.lazy-evaluation.net/de/images-generated/orgmode-export.svg" alt="orgmode-export.svg" class="org-svg"&gt;
&lt;/p&gt;
&lt;/div&gt;

&lt;/div&gt;

&lt;p&gt;
Of course it is easy to include a diagram with a post, but the
standard procedure to create/edit the diagram with an external GUI
tool does not resonate with me.  Even back in my diploma thesis I fell
in love with Donald Knuth's &lt;a href="https://en.wikipedia.org/wiki/MetaPost"&gt;MetaPost&lt;/a&gt; system to describe diagrams
in a declarative way and let the tool do the drawing.
&lt;/p&gt;

&lt;p&gt;
For some &lt;a href="https://latex-beamer.com/quick-start/"&gt;LaTeX Beamer&lt;/a&gt; presentations I used &lt;a href="http://ditaa.sourceforge.net/"&gt;ditaa&lt;/a&gt; in the meantime but
inside a &lt;b&gt;make&lt;/b&gt; flow that took care of the dependencies.  The diagrams
and the presentation were strictly separated.  For the blog posts I
did not yet have a good solution, until I switched to blogging in
orgmode.  Compared to ReST and Asciidoc posts, Emacs orgmode provides
a much richer ecosystem with lots of hooks into other systems by means
of the &lt;a href="https://orgmode.org/worg/org-contrib/babel/"&gt;org-babel&lt;/a&gt; system.
&lt;/p&gt;

&lt;p&gt;
So by switching the post source format, blogging in orgmode should
actually hook into e.g. Graphviz out of the box.  And indeed with a
little fine tuning, this is an amazingly elegant way to include
visualizations in the posts.
&lt;/p&gt;

&lt;p&gt;
As org-mode (through exporting to LaTex Beamer) has also become the
source format of my presentations, this new freedom easily extends
into presentations and even regular PDF documents by exporting to
LaTeX only.  So the means shown here to produce diagrams for the blog
are also usable when you want to generate Beamer presentations or
LaTeX documents.  As we will see, the choice of output formats is
linked to the targeted use-case.
&lt;/p&gt;

&lt;p&gt;&lt;a href="https://blog.lazy-evaluation.net/de/posts/orgmode-diagrams.html?pk_campaign=feed"&gt;Weiterlesen…&lt;/a&gt; (9 min verbleiben zum Lesen)&lt;/p&gt;&lt;/div&gt;</description><guid>https://blog.lazy-evaluation.net/de/posts/orgmode-diagrams.html</guid><pubDate>Fri, 30 Sep 2022 19:38:34 GMT</pubDate></item><item><title>Blog internals (or learning new things to fix stuff)</title><link>https://blog.lazy-evaluation.net/de/posts/2022-08-internals.html?pk_campaign=feed</link><dc:creator>Detlev Zundel</dc:creator><description>&lt;div&gt;&lt;div style="text-align:center" class="imageblock" id="org34eb726"&gt;

&lt;div id="org5846d9a" class="figure"&gt;
&lt;p&gt;&lt;img src="https://blog.lazy-evaluation.net/de/images/nikola-50px-transparent.png" alt="nikola-50px-transparent.png" title="Big lock" align="middle" width="150"&gt;
&lt;/p&gt;
&lt;/div&gt;

&lt;/div&gt;

&lt;p&gt;
Recently I was made aware of a &lt;a href="https://www.theregister.com/2022/01/31/website_fine_google_fonts_gdpr/"&gt;consequential GDPR ruling in
Germany&lt;/a&gt;. The summary of the ruling is that a website owner was
sentenced to pay a €100 fine to a visitor of his website because the
website used Google hosted fonts.  The visitor claimed that by loading
the Google fonts, his IP address was exposed to the Google servers and
this violates the GDPR.
&lt;/p&gt;

&lt;p&gt;
Effectively this exposes every website in Germany using Google hosted
web fonts to become the target of an €100 fine.  At first, it seemed
like a theoretic problem, but more recently it seems that people have
&lt;a href="https://www.heise.de/news/DSGVO-Abmahnwelle-wegen-Google-Fonts-7206364.html"&gt;turned this into a business-model&lt;/a&gt; (link is in German) and there now
seem to be a wave of incidents based on this ruling.  So it has become
pretty urgent to fix this for web site owners in Germany.
&lt;/p&gt;

&lt;p&gt;
Checking my &lt;a href="https://getnikola.com/"&gt;Nikola&lt;/a&gt; generated site, I found that the &lt;a href="https://github.com/getnikola/nikola-themes/tree/master/v8/zen"&gt;zen theme&lt;/a&gt; that I
use not only uses Google hosted fonts but also the &lt;a href="https://fontawesome.com/"&gt;Fontawesome icon
set&lt;/a&gt; hosted on its own server.  So I quickly decided that I need to
switch those over to self-hosting before I get one of these lawyer
mails.  This blog post documents the things I learned on this journey
which is still not over.
&lt;/p&gt;

&lt;p&gt;
And I apologize in advance that this post has become rather large and
very technical, but the things are really connected together so I
decided not to split them out into smaller posts.  I sincerely hope
this was the right thing to do.
&lt;/p&gt;

&lt;p&gt;&lt;a href="https://blog.lazy-evaluation.net/de/posts/2022-08-internals.html?pk_campaign=feed"&gt;Weiterlesen…&lt;/a&gt; (17 min verbleiben zum Lesen)&lt;/p&gt;&lt;/div&gt;</description><guid>https://blog.lazy-evaluation.net/de/posts/2022-08-internals.html</guid><pubDate>Thu, 01 Sep 2022 20:36:06 GMT</pubDate></item><item><title>Nikola Blog Posts with Emacs</title><link>https://blog.lazy-evaluation.net/de/posts/nikola-posts-with-emacs.html?pk_campaign=feed</link><dc:creator>Detlev Zundel</dc:creator><description></description><guid>https://blog.lazy-evaluation.net/de/posts/nikola-posts-with-emacs.html</guid><pubDate>Sun, 31 Jan 2021 20:57:06 GMT</pubDate></item><item><title>Emacs, Evince and SyncTeX Magic - Look Ma no Code!</title><link>https://blog.lazy-evaluation.net/de/posts/linux/emacs-evince-and-synctex-magic-nocode.html?pk_campaign=feed</link><dc:creator>Detlev Zundel</dc:creator><description></description><guid>https://blog.lazy-evaluation.net/de/posts/linux/emacs-evince-and-synctex-magic-nocode.html</guid><pubDate>Sat, 30 Jan 2021 16:33:31 GMT</pubDate></item><item><title>Emacs, Evince and SyncTeX Magic</title><link>https://blog.lazy-evaluation.net/de/posts/linux/emacs-evince-and-synctex-magic.html?pk_campaign=feed</link><dc:creator>Detlev Zundel</dc:creator><description></description><guid>https://blog.lazy-evaluation.net/de/posts/linux/emacs-evince-and-synctex-magic.html</guid><pubDate>Tue, 06 Oct 2020 20:38:04 GMT</pubDate></item><item><title>More Colors For My Blog</title><link>https://blog.lazy-evaluation.net/de/posts/linux/more-colors-for-my-blog.html?pk_campaign=feed</link><dc:creator>Detlev Zundel</dc:creator><description></description><guid>https://blog.lazy-evaluation.net/de/posts/linux/more-colors-for-my-blog.html</guid><pubDate>Sun, 24 May 2020 20:13:06 GMT</pubDate></item><item><title>Starting My Rust Journey</title><link>https://blog.lazy-evaluation.net/de/posts/rust/rust-introduction.html?pk_campaign=feed</link><dc:creator>Detlev Zundel</dc:creator><description>&lt;div&gt;&lt;p&gt;With a few things coming together, I have finally decided to look into
yet another programming language.  On the one hand learning a new
language is usually a good way to broaden the fundamenetal
understanding of programming, but this time I do have a specific goal
in mind that I want to reach.&lt;/p&gt;
&lt;p&gt;Only recently I have been looking at various 32 bit Cortex-M ARM
micro-controllers with the vendor provided &lt;code class="docutils literal"&gt;C&lt;/code&gt; programming
environments.  Knowing modern programming languages like Haskell,
OCaml or Go got me so frustrated with these environments that I
decided to find a modern language also fit for this embedded space and
no, I don't think Python is the answer to every problem just as Java
wasn't.  Ultimately, I would like to see a functional programming
language in this space, but I am open to other approaches fitting the
embedded space.&lt;/p&gt;
&lt;p&gt;Being an FSF Emacs user for decades, I am also averse to these
proprietary programming environments that may have some nice features
but ultimately only try to lock the developer into a vendor controlled
ecosystem.  Usually they are all Eclipse based anyway but are
incompatible with one another.  It gives me the shivers installing the
n-th copy of Eclipse for yet another Cortex-M based micro-controller
and I really wonder how we ended up in this very frustrating assembly
of walled in environments.&lt;/p&gt;
&lt;p&gt;So this is the start of a small series of posts that evaluate how easy
it will be to setup a programming environment on GNU/Linux for &lt;a class="reference external" href="https://www.rust-lang.org/"&gt;Rust&lt;/a&gt; based on &lt;a class="reference external" href="https://www.gnu.org/software/emacs/"&gt;GNU Emacs&lt;/a&gt;.  Ultimately I want to target
micro-controllers without a full GNU/Linux system running on them, so
the aim is to also get a cross-compilation setup working.&lt;/p&gt;
&lt;img alt="Rust Logo" class="align-center" src="https://blog.lazy-evaluation.net/images/Rust_programming_language_black_logo.png" style="width: 200px;"&gt;
&lt;p&gt;&lt;a href="https://blog.lazy-evaluation.net/de/posts/rust/rust-introduction.html?pk_campaign=feed"&gt;Weiterlesen…&lt;/a&gt; (4 min verbleiben zum Lesen)&lt;/p&gt;&lt;/div&gt;</description><guid>https://blog.lazy-evaluation.net/de/posts/rust/rust-introduction.html</guid><pubDate>Sun, 24 Feb 2019 20:38:22 GMT</pubDate></item></channel></rss>