feed.xml

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>~hellricer/</title>
        <description>— a terminal dweller</description>        
        <link>https://hellricer.github.io</link>
        <atom:link href="https://hellricer.github.io/feed.xml" rel="self" type="application/rss+xml" />
        
            <item>
                <title>Decoding the TRAKTOR4 field</title>
                <description>&lt;p&gt;The Native Instrument&#39;s Traktor line of software is kind of infamous when it comes to its library management.&lt;/p&gt;
&lt;p&gt;It only reads a handful of standard ID3 fields and it encodes its own metadata inside a non-standard private field.  As one could expect, the format is binary and proprietary.&lt;/p&gt;
&lt;p&gt;Luckily, &lt;a href=&#34;https://web.archive.org/web/20130525033615/http://dope.cz/code&#34;&gt;some clever folks already figured it out back in 2013&lt;/a&gt; and it seems that the format haven&#39;t changed since then.  They also provided a parser implemented in Perl, but it wasn&#39;t archived.&lt;/p&gt;
&lt;p&gt;But since we know the format, we can now write our own parser using some Modern Tools™.&lt;/p&gt;
&lt;h3&gt;Format&lt;/h3&gt;
&lt;p&gt;Data are structured as a &lt;em&gt;n-ary&lt;/em&gt; tree of frames.  Each frame consists of the header and the data content.&lt;/p&gt;
&lt;hr&gt;

&lt;pre&gt;&lt;code&gt;0x00 0x04 Frame identifier (reversed for some reason)
0x04 0x04 Frame&#39;s length in bytes (=LEN)
0x08 0x04 Number of child frames
0x0c LEN  Data content of the frame
&lt;/code&gt;&lt;/p</description>
                <pubDate>Wed, 05 May 2021 00:00:00 </pubDate>
                <link>https://hellricer.github.io/2021/05/05/decoding-traktor4-field.html</link>
                <guid isPermaLink="true">https://hellricer.github.io/2021/05/05/decoding-traktor4-field.html</guid>
            </item>
        
            <item>
                <title>Open source games for MS-DOS</title>
                <description>&lt;h2&gt;Intro&lt;/h2&gt;
&lt;p&gt;Most you of probably remember GORILLA.BAS or DONKEY.BAS co-written by Bill Gates himself and many are probably aware that some FPS shooters like Doom and Quake were open-sourced, but otherwise source code wasn&#39;t something you saw very often in the DOS gaming world.&lt;/p&gt;
&lt;p&gt;But turns out that some developers did decide to release the games&#39; sources over the course of years.  Most of them have been already rewritten to SDL, making them portable to pretty much any modern platform, but for me the real question is — how hard is it to compile the actual DOS binaries?&lt;/p&gt;
&lt;p&gt;Why would anyone want to do that, you ask?  Because, well..  uhm.  Anyway, let&#39;s get into it!&lt;/p&gt;
&lt;h2&gt;Mario &amp;amp; Luigi&lt;/h2&gt;
&lt;iframe width=&#34;901&#34; height=&#34;507&#34; src=&#34;https://www.youtube.com/embed/uu9SO6WOnYY&#34; frameborder=&#34;0&#34; allow=&#34;accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture&#34; allowfullscreen&gt;&lt;/iframe&gt;
&lt;p&gt;&lt;small&gt;&lt;em&gt;&lt;/em&gt;&lt;/small&gt;&lt;/p&gt;
&lt;p&gt;Let&#39;s start with this Mario </description>
                <pubDate>Sun, 01 Nov 2020 00:00:00 </pubDate>
                <link>https://hellricer.github.io/2020/11/01/opensource-msdos-games.html</link>
                <guid isPermaLink="true">https://hellricer.github.io/2020/11/01/opensource-msdos-games.html</guid>
            </item>
        
            <item>
                <title>Making fzf experience a bit more consistent</title>
                <description>&lt;p&gt;As for increasingly many people, &lt;code&gt;fzf&lt;/code&gt; became deeply ingrained into my workflow. But there are few things that I find a bit odd.&lt;/p&gt;
&lt;p&gt;First, I don&#39;t really see the advantage of having &lt;code&gt;Ctrl-T&lt;/code&gt; mapped to &lt;em&gt;&#34;find files in current directory&#34;&lt;/em&gt;. What I often want is to search only in some subdirectory.&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;cp Music/&amp;lt;Ctrl-T&amp;gt;
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;doesn&#39;t quite work for me, because the search starts in my home directory. What I have to use is &lt;code&gt;cp Music/**&amp;lt;Tab&amp;gt;&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;Second thing I don&#39;t quite understand is why author needed to treat &lt;code&gt;kill&lt;/code&gt; command differently than all the other ones - while you need to type &lt;code&gt;**&amp;lt;Tab&amp;gt;&lt;/code&gt; for &lt;code&gt;ssh&lt;/code&gt; or &lt;code&gt;export&lt;/code&gt;, the &lt;code&gt;kill&lt;/code&gt; has to be run with &lt;code&gt;kill &amp;lt;Tab&amp;gt;&lt;/code&gt; (and &lt;code&gt;kill **&amp;lt;Tab&amp;gt;&lt;/code&gt; doesn&#39;t work). There&#39;s even &lt;a href=&#34;https://github.com/junegunn/fzf/issues/385&#34;&gt;an issue&lt;/a&gt; about the problem, but</description>
                <pubDate>Thu, 16 Apr 2020 00:00:00 </pubDate>
                <link>https://hellricer.github.io/2020/04/16/a-bit-more-consistent-fzf.html</link>
                <guid isPermaLink="true">https://hellricer.github.io/2020/04/16/a-bit-more-consistent-fzf.html</guid>
            </item>
        
            <item>
                <title>Test-drive your terminal</title>
                <description>&lt;p&gt;Along with shell, terminal emulator is for many the most important part of operating system.  It&#39;s where you spend most of your time!&lt;/p&gt;
&lt;p&gt;There are tones of them to choose from.  Some prefer them as leightweight as possible, others like them to handle things like tabs, splits, etc.&lt;/p&gt;
&lt;p&gt;But how does your terminal perform at actually displaying stuff?  I wrote this shell script to test how various terminals handle colors, extended text decorations and few other things.&lt;/p&gt;
&lt;div&gt;
  &lt;script src=&#34;https://gist.github.com/hellricer/e514d9615d02838244d8de74d0ab18b3.js&#34;&gt;&lt;/script&gt;
&lt;/div&gt;

&lt;p&gt;Here&#39;s how decorations look in &lt;code&gt;gnome-terminal&lt;/code&gt;:&lt;/p&gt;
&lt;figure&gt;
    &lt;a href=&#34;https://hellricer.github.io//assets/images/terminal-decorations.jpg&#34;&gt;&lt;img src=&#34;https://hellricer.github.io//assets/images/terminal-decorations.jpg&#34; alt=&#34; Image: &#34; title=&#34;gnome-terminal getting it almost right.&#34; /&gt;&lt;/a&gt;
    &lt;figcaption&gt;gnome-terminal getting it almost right.&lt;/figcaption&gt;
&lt;/figure&gt;

&lt;h2&gt;Results&lt;/h2&gt;
</description>
                <pubDate>Sat, 05 Oct 2019 00:00:00 </pubDate>
                <link>https://hellricer.github.io/2019/10/05/test-drive-your-terminal.html</link>
                <guid isPermaLink="true">https://hellricer.github.io/2019/10/05/test-drive-your-terminal.html</guid>
            </item>
        
            <item>
                <title>Soupmonkey</title>
                <description>&lt;p&gt;&lt;a href=&#34;/2019/05/29/elinks-with-beautifulsoup.html&#34;&gt;In my last blog-post&lt;/a&gt; , I discovered an easy way to manipulate DOM before rendering it in Elinks using BeautifulSoup library.&lt;/p&gt;
&lt;p&gt;I called it DevTools for ELinks, but as one reddit user correctly noted, it&#39;s conceptually more similar to user-scripts.&lt;/p&gt;
&lt;p&gt;That gave me an idea to completely separate rule-files for individual domains in a similar way that Greasemonkey, Tampermonkey and similar user-script managers do.&lt;/p&gt;
&lt;p&gt;So, I introduce &lt;a href=&#34;https://github.com/hellricer/soupmonkey&#34;&gt;soupmonkey!&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The usage is simplified as well - all you have to do is clone the repository into your &lt;code&gt;~/.elinks/&lt;/code&gt; folder and decorate the &lt;code&gt;pre_format_html_hook&lt;/code&gt; in the hooks file.  So your &lt;code&gt;~/.elinks/hooks.py&lt;/code&gt; might look like this:&lt;/p&gt;
&lt;hr/&gt;

&lt;pre&gt;&lt;code&gt;import soupmonkey

@soupmonkey.inject
def pre_format_html_hook(url, html):
    return html
&lt;/code&gt;&lt;/pre&gt;
&lt;hr/&gt;

&lt;p&gt;And that&#39;s it!&lt;/p&gt;
&lt;p&gt;As of writ</description>
                <pubDate>Fri, 04 Oct 2019 00:00:00 </pubDate>
                <link>https://hellricer.github.io/2019/10/04/modify-dom-in-elinks-with-soupmonkey.html</link>
                <guid isPermaLink="true">https://hellricer.github.io/2019/10/04/modify-dom-in-elinks-with-soupmonkey.html</guid>
            </item>
        
            <item>
                <title>ELinks with BeautifulSoup</title>
                <description>&lt;p&gt;For many terminal dwellers like me, browsing the web is one of the last few scenarios where we have to leave our cozy terminals into the harsh cold GUI world. Complexity of today&#39;s websites simply won&#39;t cut it without graphics, preferably with high screen resolution.&lt;/p&gt;
&lt;p&gt;That&#39;s not to say that it&#39;s not worth to experiment with terminal-based browsers, though! Most people probably know about &lt;code&gt;w3m&lt;/code&gt; for its ability to display actual images and &lt;code&gt;lynx&lt;/code&gt; as the oldest one. But in this post, I&#39;d like to talk about &lt;a href=&#34;http://elinks.cz/&#34;&gt;ELinks&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;It&#39;s arguably most feature-packed (read “bloated”) and also most user-friendly of the three. It supports tabs, multiple downloads, bookmarks, it has rudimentary support for CSS and even JavaScript. And, after some tweaking, it can actually look pretty good!&lt;/p&gt;
&lt;figure&gt;
    &lt;a href=&#34;https://hellricer.github.io//assets/images/elinks-ddg.png&#34;&gt;&lt;img src=&#34;https://hellricer.github.io//assets/images/elinks-ddg.png&#34; a</description>
                <pubDate>Wed, 29 May 2019 00:00:00 </pubDate>
                <link>https://hellricer.github.io/2019/05/29/elinks-with-beautifulsoup.html</link>
                <guid isPermaLink="true">https://hellricer.github.io/2019/05/29/elinks-with-beautifulsoup.html</guid>
            </item>
        
            <item>
                <title>Ctrl+Arrows in terminal</title>
                <description>&lt;p&gt;Basically every program with some kind of input field supports &lt;code&gt;Ctrl+Arrows&lt;/code&gt; for skipping over words,
&lt;code&gt;Ctrl+Backspace&lt;/code&gt;, &lt;code&gt;Ctrl+Del&lt;/code&gt; for deleting words, &lt;code&gt;Ctrl+Shift+Delete&lt;/code&gt; for deleting rest of the line, etc.&lt;/p&gt;
&lt;p&gt;Terminal emulators, on the other hand…&lt;/p&gt;
&lt;p&gt;We could go to great lengths explaining reasons, history of vt100, etc… But the reality is that even when you&#39;re not particularly fond of GUI apps, you probably use at least a web browser and you likely have these shortcuts engraved into your muscle memory anyway.&lt;/p&gt;
&lt;p&gt;Of course, you can use &lt;code&gt;Alt+Arrow&lt;/code&gt; and other &lt;a href=&#34;https://readline.kablamo.org/emacs.html&#34;&gt;very powerful&lt;/a&gt; &lt;code&gt;readline&lt;/code&gt; bindings, but that means learning
whole new, &lt;a href=&#34;https://clementc.github.io/blog/2018/01/25/moving_cli/&#34;&gt;quite esoteric set of shortcuts for rather basic things&lt;/a&gt; like moving around and deleting text.&lt;/p&gt;
&lt;p&gt;So, if you want to join me in spitting on the VT100&#39;s grave </description>
                <pubDate>Tue, 21 May 2019 00:00:00 </pubDate>
                <link>https://hellricer.github.io/2019/05/21/ctrl-arrows-in-terminal.html</link>
                <guid isPermaLink="true">https://hellricer.github.io/2019/05/21/ctrl-arrows-in-terminal.html</guid>
            </item>
        
            <item>
                <title>New webpage</title>
                <description>&lt;p&gt;Hello!&lt;/p&gt;
&lt;p&gt;My name is Hellricer.&lt;/p&gt;
&lt;p&gt;This blog will serve as a place to talk about my experiences with terminals and terminal-based programs, great software I&#39;ve found, tricks &amp;amp; tips for making your time in terminal more enjoyable, “ricing” and GNU/Linux in general.&lt;/p&gt;
&lt;p&gt;Most posts will revolve around programs like &lt;code&gt;vim&lt;/code&gt;, &lt;code&gt;tmux&lt;/code&gt;, &lt;code&gt;bash&lt;/code&gt; and so on.&lt;/p&gt;
&lt;h1&gt;About this website&lt;/h1&gt;
&lt;p&gt;This website is based on Jekyll and uses modified version of &lt;a href=&#34;https://github.com/mmistakes/so-simple-theme&#34;&gt;so-simple-theme&lt;/a&gt;, but I&#39;m using &lt;a href=&#34;http://obraz.pirx.ru&#34;&gt;Obraz&lt;/a&gt; for generating it.&lt;/p&gt;
&lt;p&gt;It aims to be modern-looking and responsive, while still being tiny (~1MB) and usable even in terminal-based browsers like &lt;code&gt;w3m&lt;/code&gt;, &lt;code&gt;lynx&lt;/code&gt; or &lt;code&gt;elinks&lt;/code&gt; (pictured below).&lt;/p&gt;
&lt;figure&gt;
    &lt;a href=&#34;https://hellricer.github.io//assets/images/editing-webpage.png&#34;&gt;&lt;img src=&#34;https://hellricer.github.io//assets/images/editin</description>
                <pubDate>Mon, 20 May 2019 00:00:00 </pubDate>
                <link>https://hellricer.github.io/2019/05/20/new-webpage.html</link>
                <guid isPermaLink="true">https://hellricer.github.io/2019/05/20/new-webpage.html</guid>
            </item>
        
            <item>
                <title>Genes in Middle-earth</title>
                <description>&lt;p&gt;&lt;em&gt;...one script to find them all,
and into GEDCOM bind them...&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Ever since I was a child, Middle-earth was a special place for me.  Out of all the imaginary places invented for the entertainment, &lt;em&gt;Arda&lt;/em&gt; is arguably the most complex one.  The amount of information that accompanies the stories is overwhelming.  Tolkien is known to be genius linguist - languages of his world evolve in time, fork into dialects and influence each other.  But his sense for geography and history is just as incredible.  There are more than 70 kingdoms with several hundreds of people documented at least to some extent.  Some can be find in family trees printed in appendices of the books, some family relations are only mentioned in stories, but there&#39;s lot of them.  So, how about we map them?&lt;/p&gt;
&lt;p&gt;I&#39;m obviously not the first one to think of digitalizing Tolkien&#39;s genealogies.  &lt;a href=&#34;http://www.minastirith.com/cgi-bin/ultimatebb.cgi?ubb=get_topic;f=1;t=000070&#34;&gt;There are&lt;/a&gt; some ancien</description>
                <pubDate>Thu, 30 Apr 2015 00:00:00 </pubDate>
                <link>https://hellricer.github.io/2015/04/30/genes-in-middle-earth.html</link>
                <guid isPermaLink="true">https://hellricer.github.io/2015/04/30/genes-in-middle-earth.html</guid>
            </item>
        
            <item>
                <title>Color me impressed</title>
                <description>&lt;p&gt;I&#39;m crazy about colors.&lt;/p&gt;
&lt;p&gt;I work with terminal emulators all the time and nothings is more deterrent to
me than big wall of black &amp;amp; white text spitted out into my 300x100 terminal.&lt;/p&gt;
&lt;p&gt;I want my errors red and successes green, I want numbers, URLs and paths pop
out from the rest of the text, I want colored logs, compiler outputs, source
code snippets... It really makes your terminal experience much more fun.&lt;/p&gt;
&lt;p&gt;So let&#39;s take a look where my obsession brought me so far.&lt;/p&gt;
&lt;h2&gt;Brief history&lt;/h2&gt;
&lt;p&gt;In the late 70s, the number of character-oriented terminals was rapidly
expanding. Of course there was no &#34;de jure&#34; standard and each manufacturer
handled their &lt;a href=&#34;http://en.wikipedia.org/wiki/Escape_sequence&#34;&gt;escape sequences&lt;/a&gt;
differently. That meant that every screen-handling program had to be written
for one (type of) terminal only.&lt;/p&gt;
&lt;p&gt;To deal with these incompatibilities, Bill Joy foresightedly created the
&lt;code&gt;termcap&lt;/code&gt; library (&lt;strong&gt;term&lt;/strong</description>
                <pubDate>Wed, 08 Oct 2014 00:00:00 </pubDate>
                <link>https://hellricer.github.io/2014/10/08/color-me-impressed.html</link>
                <guid isPermaLink="true">https://hellricer.github.io/2014/10/08/color-me-impressed.html</guid>
            </item>
        
    </channel>
</rss>