<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>emacscarnival202506 &amp;mdash; Kemal&#39;s Braindump</title>
    <link>https://write.moxnet.eu/tag:emacscarnival202506</link>
    <description>Rambling thoughts and reflections</description>
    <pubDate>Thu, 16 Apr 2026 08:32:18 +0200</pubDate>
    <item>
      <title>Brainiac v1.0 released</title>
      <link>https://write.moxnet.eu/brainiac-v1-0-released</link>
      <description>&lt;![CDATA[#emacs #brainiac #emacscarnival202506&#xA;&#xA;I am glad to announce that my custom Emacs configuration Brainiac has reached release status. I am now using it without major changes since a couple of weeks, so it&#39;s time to freeze this version if other people want to use it.&#xA;&#xA;!--more--&#xA;&#xA;Introduction&#xA;&#xA;Why do I aim to have a minimal configuration? &#xA;I am a perfectionist and tend to get lost in details. When a configuration gets larger, I loose time by tweaking it over and over again. By keeping the configuration minimal, I reduce the danger of going down the Emacs rabbit hole and increase the probability that I will focus on more important things in life.&#xA;&#xA;Brainac is aimed to be a simple and easy to understand configuration for task management and note taking. It&#39;s not aimed at programmers, but at people trying to implement a workflow like GTD or build something like a Second Brain without overcomplicating the process, e.g. connection graphs, AI support etc.&#xA;&#xA;The configuration is very opinionated, as it&#39;s based on my workflow. I am not trying to make it generic, just clean and easily extendable. I stick with the built-in packages in order to reduce dependencies and complexity.&#xA;&#xA;Short description&#xA;&#xA;Noteworthy stuff:&#xA;I picked up some sane defaults from multiple sources, like turning on the revert mode, enabling smart parenthesis, tuning of built-in completion engine etc.&#xA;The tasks and notes should look nice and readable, because of this I use the modus-operandi theme and style some things additionally to either push them to the background or to make them stick out more visually.&#xA;You can easily capture tasks, webpage links/quotes (using org-protocol) and screenshots (using org-download, org-attach and flameshot).&#xA;A simple journal with timestamped entries is configured in the capture templates.&#xA;Notes are also captured over a template and you can assign categories to them. Format is inspired by Denote.&#xA;You can export the notes to HTML (uses custom CSS) or Markdown. From there you can print to PDF or other formats.&#xA;Additionally to normal org-clock functionality, you can define a special task and clock in it per default with C-c j w. I use this to clock my work time.&#xA;&#xA;I will not go deeper into details of the configuration, go thru it and explore. Most of the stuff can be understood by reading the help on variables and functions.&#xA;&#xA;Currently I am using the configuration with Ubuntu Linux LTS 24.04 KDE and Emacs 29.3. If you use something else, you will probably have to tweak it.&#xA;&#xA;Structure and install&#xA;&#xA;The configuration consists of two major files:&#xA;brainiac.org which contains the configurations that will be tangled to early-init.el and init.el,&#xA;brainiac.css a simple CSS for the exported notes.&#xA;&#xA;Unpack the zip file from here to your HOME folder ~/brainiac. You will get the structure like this:&#xA;&#xA;~/brainiac/&#xA;    -- config/ &lt;- this is where the configuration files are&#xA;    -- notes/ &lt;- this is where all notes go&#xA;    -- attach/ &lt;- this is where the attachments land&#xA;    -- export/ &lt;- this is where the exported files are&#xA;    -- main.org &lt;- this is the main org file to use for tasks, projects etc.&#xA;After unpacking open the brainiac.org and tangle it.&#xA;&#xA;External apps needed are:&#xA;Org Capture for Firefox&#xA;Flameshot&#xA;&#xA;Workflow&#xA;&#xA;I provide a template for main.org that is based on the workflow I use:&#xA;&#xA;Top level headings are categories in my life. &#xA;Under top level headings I create tasks and put them thru the states TODO, PROG, WAIT, DONE or CANC to track their progress.&#xA;I use tags to provide more context to tasks, e.g. work, names, project relation etc.&#xA;If a task comes from an Email I deal with this by using the following form TODO @ &#34;Subjectofthe_Email&#34;, then it&#39;s easy to find it in my Emails when I need extra information on the task.&#xA;Your daily agenda is at C-c a n. That will show you scheduled tasks for today and deadlines coming up, I work on that first. &#xA;Every task that is not scheduled or has no deadline, is shown in a backlog below the day tasks. I use priorities to sort this backlog and give me clarity on what to work next.&#xA;Use PRJ tag to mark your projects that will be broken down to tasks.  I usually use statistic cookies at the end of the name of the project to show me an overview of tasks in the project. &#xA;You can have a look at your projects with C-c a P. I inspect the projects once a week during the review, to see if some of them need attention, e.g. they are stuck C-c a #.&#xA;When showing notes to other people I usually do a quick C-c C-e h o which exports the note to HTML and shows it in Firefox.&#xA;&#xA;Open for feedback and improvements&#xA;&#xA;If you have feedback, improvement propositions etc., just reach out to me.&#xA;&#xA;br&#xD;&#xA;- -&#xD;&#xA;&#xD;&#xA;Have any thoughts or comments?]]&gt;</description>
      <content:encoded><![CDATA[<p><a href="https://write.moxnet.eu/tag:emacs" class="hashtag"><span>#</span><span class="p-category">emacs</span></a> <a href="https://write.moxnet.eu/tag:brainiac" class="hashtag"><span>#</span><span class="p-category">brainiac</span></a> <a href="https://write.moxnet.eu/tag:emacscarnival202506" class="hashtag"><span>#</span><span class="p-category">emacscarnival202506</span></a></p>

<p>I am glad to announce that my custom Emacs configuration <em>Brainiac</em> has reached release status. I am now using it without major changes since a couple of weeks, so it&#39;s time to freeze this version if other people want to use it.</p>



<h2 id="introduction" id="introduction">Introduction</h2>

<p>Why do I aim to have a minimal configuration?
I am a perfectionist and tend to get lost in details. When a configuration gets larger, I loose time by tweaking it over and over again. By keeping the configuration minimal, I reduce the danger of going down the Emacs rabbit hole and increase the probability that I will focus on more important things in life.</p>

<p><em>Brainac</em> is aimed to be a simple and easy to understand configuration for task management and note taking. It&#39;s not aimed at programmers, but at people trying to implement a workflow like <a href="https://thomasjfrank.com/productivity/the-5-minute-guide-to-gtd-getting-things-done/">GTD</a> or build something like a <a href="https://www.buildingasecondbrain.com/">Second Brain</a> without overcomplicating the process, e.g. connection graphs, AI support etc.</p>

<p>The configuration is very opinionated, as it&#39;s based on my workflow. I am not trying to make it generic, just clean and easily extendable. I stick with the built-in packages in order to reduce dependencies and complexity.</p>

<h2 id="short-description" id="short-description">Short description</h2>

<p>Noteworthy stuff:
– I picked up some sane defaults from multiple sources, like turning on the revert mode, enabling smart parenthesis, tuning of built-in completion engine etc.
– The tasks and notes should look nice and readable, because of this I use the <a href="https://protesilaos.com/emacs/modus-themes">modus-operandi</a> theme and style some things additionally to either push them to the background or to make them stick out more visually.
– You can easily capture tasks, webpage links/quotes (using <code>org-protocol</code>) and screenshots (using <code>org-download</code>, <code>org-attach</code> and <code>flameshot</code>).
– A simple journal with timestamped entries is configured in the <a href="https://orgmode.org/manual/Capture-templates.html">capture templates</a>.
– Notes are also captured over a template and you can assign categories to them. Format is inspired by <a href="https://protesilaos.com/emacs/denote">Denote</a>.
– You can export the notes to HTML (uses custom CSS) or Markdown. From there you can print to PDF or other formats.
– Additionally to normal <code>org-clock</code> functionality, you can define a special task and clock in it per default with <code>C-c j w</code>. I use this to clock my work time.</p>

<p>I will not go deeper into details of the configuration, go thru it and explore. Most of the stuff can be understood by reading the help on variables and functions.</p>

<p>Currently I am using the configuration with Ubuntu Linux LTS 24.04 KDE and Emacs 29.3. If you use something else, you will probably have to tweak it.</p>

<h2 id="structure-and-install" id="structure-and-install">Structure and install</h2>

<p>The configuration consists of two major files:
– <code>brainiac.org</code> which contains the configurations that will be tangled to <code>early-init.el</code> and <code>init.el</code>,
– <code>brainiac.css</code> a simple CSS for the exported notes.</p>

<p>Unpack the <code>zip</code> file from <a href="https://moxnet.eu/s/484jpnTLZ7k9r4Y">here</a> to your HOME folder <code>~/brainiac</code>. You will get the structure like this:</p>

<pre><code>~/brainiac/
    -- config/ &lt;- this is where the configuration files are
    -- notes/ &lt;- this is where all notes go
    -- attach/ &lt;- this is where the attachments land
    -- export/ &lt;- this is where the exported files are
    -- main.org &lt;- this is the main org file to use for tasks, projects etc.
</code></pre>

<p>After unpacking open the <code>brainiac.org</code> and <a href="https://orgmode.org/manual/Extracting-Source-Code.html">tangle</a> it.</p>

<p>External apps needed are:
– <a href="https://addons.mozilla.org/en-US/firefox/addon/org-capture/">Org Capture for Firefox</a>
– <a href="https://flameshot.org/">Flameshot</a></p>

<h2 id="workflow" id="workflow">Workflow</h2>

<p>I provide a template for <code>main.org</code> that is based on the workflow I use:</p>
<ul><li>Top level headings are <a href="https://orgmode.org/manual/Categories.html">categories</a> in my life.</li>
<li>Under top level headings I create tasks and put them thru the states <code>TODO</code>, <code>PROG</code>, <code>WAIT</code>, <code>DONE</code> or <code>CANC</code> to track their progress.</li>
<li>I use <a href="https://orgmode.org/manual/Tags.html">tags</a> to provide more context to tasks, e.g. work, names, project relation etc.</li>
<li>If a task comes from an Email I deal with this by using the following form <code>TODO @ &#34;Subject_of_the_Email&#34;</code>, then it&#39;s easy to find it in my Emails when I need extra information on the task.</li>
<li>Your daily agenda is at <code>C-c a n</code>. That will show you scheduled tasks for today and deadlines coming up, I work on that first.</li>
<li>Every task that is not scheduled or has no deadline, is shown in a backlog below the day tasks. I use <a href="https://orgmode.org/manual/Priorities.html">priorities</a> to sort this backlog and give me clarity on what to work next.</li>
<li>Use <code>PRJ</code> tag to mark your projects that will be broken down to tasks.  I usually use <a href="https://orgmode.org/manual/Breaking-Down-Tasks.html">statistic cookies</a> at the end of the name of the project to show me an overview of tasks in the project.</li>
<li>You can have a look at your projects with <code>C-c a P</code>. I inspect the projects once a week during the review, to see if some of them need attention, e.g. they are stuck <code>C-c a #</code>.</li>
<li>When showing notes to other people I usually do a quick <code>C-c C-e h o</code> which exports the note to HTML and shows it in Firefox.</li></ul>

<h2 id="open-for-feedback-and-improvements" id="open-for-feedback-and-improvements">Open for feedback and improvements</h2>

<p>If you have feedback, improvement propositions etc., just <a href="mailto:kemal@moxnet.eu">reach</a> out to me.</p>

<p><br></p>

<hr>

<p><em>Have any <a href="mailto:kemal@moxnet.eu">thoughts or comments</a>?</em></p>
]]></content:encoded>
      <guid>https://write.moxnet.eu/brainiac-v1-0-released</guid>
      <pubDate>Thu, 03 Jul 2025 11:43:17 +0200</pubDate>
    </item>
    <item>
      <title>Announcing Brainiac Project</title>
      <link>https://write.moxnet.eu/announcing-brainiac-project</link>
      <description>&lt;![CDATA[#emacscarnival202506 #brainiac&#xA;&#xA;Somewhere during the COVID pandemic I started checking out #emacs, because of a talk I saw on #orgmode that tickled my curiosity.&#xA;&#xA;!--more--&#xA;&#xA;In the beginning I didn&#39;t dig into the manuals, as you should do, but started using the editor directly and customized stuff by integrating code snippets from different posts and blogs I stumbled upon, while looking for solutions for problems I faced.&#xA;&#xA;Over the years as my proficiency grew, so did my Emacs config. Although I regularly removed packages I didn&#39;t use, at some point in time I did task management, note taking, blogging, news reading etc. with Emacs and kept on bringing in new packages into the mix.&#xA;I didn&#39;t really reach the state of bankcruptcy, but I gathered some #elisp snippets I didn&#39;t understand or simply didn&#39;t remember why I got them at all.&#xA;&#xA;So in order to force myself to finally start reading the manuals and to learn some proper Elisp, I started hacking on a new configuration for #emacs ... as this is what you do as an Emacs user.&#xA;&#xA;The goal of the Brainiac configuration is to minimize the configuration to the bare minimum I need (e.g. tasks and notes) and try to stick to the built-in packages as much as possible. If I need something extra, I would try to implement it myself.&#xA;&#xA;You can follow how the configuration progresses here: Brainiac.&#xA;It is already fully functional and I am using it daily for private and work related stuff. When it reaches v1.0, I will write about my workflow that defined the configuration.&#xA;&#xA;br&#xD;&#xA;- -&#xD;&#xA;&#xD;&#xA;Have any thoughts or comments?]]&gt;</description>
      <content:encoded><![CDATA[<p><a href="https://write.moxnet.eu/tag:emacscarnival202506" class="hashtag"><span>#</span><span class="p-category">emacscarnival202506</span></a> <a href="https://write.moxnet.eu/tag:brainiac" class="hashtag"><span>#</span><span class="p-category">brainiac</span></a></p>

<p>Somewhere during the COVID pandemic I started checking out <a href="https://write.moxnet.eu/tag:emacs" class="hashtag"><span>#</span><span class="p-category">emacs</span></a>, because of a talk I saw on <a href="https://write.moxnet.eu/tag:orgmode" class="hashtag"><span>#</span><span class="p-category">orgmode</span></a> that tickled my curiosity.</p>



<p>In the beginning I didn&#39;t dig into the manuals, as you should do, but started using the editor directly and customized stuff by integrating code snippets from different posts and blogs I stumbled upon, while looking for solutions for problems I faced.</p>

<p>Over the years as my proficiency grew, so did my Emacs config. Although I regularly removed packages I didn&#39;t use, at some point in time I did task management, note taking, blogging, news reading etc. with Emacs and kept on bringing in new packages into the mix.
I didn&#39;t really reach the state of <a href="https://www.emacswiki.org/emacs/DotEmacsBankruptcy">bankcruptcy</a>, but I gathered some <a href="https://write.moxnet.eu/tag:elisp" class="hashtag"><span>#</span><span class="p-category">elisp</span></a> snippets I didn&#39;t understand or simply didn&#39;t remember why I got them at all.</p>

<p>So in order to force myself to finally start reading the manuals and to learn some proper Elisp, I started hacking on a new configuration for <a href="https://write.moxnet.eu/tag:emacs" class="hashtag"><span>#</span><span class="p-category">emacs</span></a> ... as this is what you do as an Emacs user.</p>

<p>The goal of the <em>Brainiac</em> configuration is to minimize the configuration to the bare minimum I need (e.g. tasks and notes) and try to stick to the built-in packages as much as possible. If I need something extra, I would try to implement it myself.</p>

<p>You can follow how the configuration progresses here: <a href="https://moxnet.eu/s/D5ZCNJwrwFjf8LY">Brainiac</a>.
It is already fully functional and I am using it daily for private and work related stuff. When it reaches v1.0, I will write about my workflow that defined the configuration.</p>

<p><br></p>

<hr>

<p><em>Have any <a href="mailto:kemal@moxnet.eu">thoughts or comments</a>?</em></p>
]]></content:encoded>
      <guid>https://write.moxnet.eu/announcing-brainiac-project</guid>
      <pubDate>Sun, 08 Jun 2025 23:44:53 +0200</pubDate>
    </item>
  </channel>
</rss>