101010.pl

Felix Palmen 📯<a href="https://techhub.social/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> users can get a <a href="https://techhub.social/tags/port" class="mention hashtag" rel="nofollow noopener" target="_blank">#port</a> of <a href="https://techhub.social/tags/dos2ansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#dos2ansi</a> v1.4 here, patch applies to the ports tree with `git am` (hint, use a local git branch to avoid cluttering your `main`): <a href="https://people.freebsd.org/~zirias/patches/0001-textproc-dos2ansi-Add-new-port.patch" rel="nofollow noopener" translate="no" target="_blank">https://people.freebsd.org/~zirias/patches/0001-textproc-dos2ansi-Add-new-port.patch</a>The port comes in two flavors: "nox11" makes <a href="https://techhub.social/tags/showansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#showansi</a> optional and doesn't add any dependencies. "x11" (the default flavor) always includes showansi and adds runtime dependencies to <a href="https://techhub.social/tags/xterm" class="mention hashtag" rel="nofollow noopener" target="_blank">#xterm</a> and <a href="https://techhub.social/tags/ibmfonts" class="mention hashtag" rel="nofollow noopener" target="_blank">#ibmfonts</a>, so the default configuration of showansi works out of the box.Still unsure whether I should add it to the official ports tree .... 🤔

Felix Palmen 📯I'm about to prepare yet another release, <a href="https://techhub.social/tags/dos2ansi" class="mention hashtag" rel="nofollow noopener" target="_blank">#dos2ansi</a> v1.3.Finding these bitmap fonts triggered two things:1. I realized dos2ansi needs a mode to NOT attempt to mimic <a href="https://techhub.social/tags/VGA" class="mention hashtag" rel="nofollow noopener" target="_blank">#VGA</a> looks by chosing more similarly looking characters: A font recreating the orignal IBM fonts probably won't have glyphs for these other characters (and the original ones will look, well, original 😜 ...)2. It gave me the idea that I now had everything in place for some sort of "ANSI viewer", just needs a script to tie together dos2ansi, <a href="https://techhub.social/tags/xterm" class="mention hashtag" rel="nofollow noopener" target="_blank">#xterm</a>, <a href="https://techhub.social/tags/less" class="mention hashtag" rel="nofollow noopener" target="_blank">#less</a> and the <a href="https://techhub.social/tags/ibmfonts" class="mention hashtag" rel="nofollow noopener" target="_blank">#ibmfonts</a>. So, here it is: showansi. It should work with other X terminals, pagers, fonts, for configuration see the updated README: <a href="https://github.com/Zirias/dos2ansi" rel="nofollow noopener" translate="no" target="_blank">https://github.com/Zirias/dos2ansi</a>The script first calls dos2ansi to query some <a href="https://techhub.social/tags/SAUCE" class="mention hashtag" rel="nofollow noopener" target="_blank">#SAUCE</a> metadata it then uses to pick the most appropriate font, window size and title for xterm.The screenshot uses completely unconfigured Xorg and xterm, to show the script sets everything as needed.<a href="https://techhub.social/tags/ansiart" class="mention hashtag" rel="nofollow noopener" target="_blank">#ansiart</a> <a href="https://techhub.social/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#retrocomputing</a>

Recent searches

Search options

Administered by:

Server stats:

#ibmfonts