<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Parser on Phosphor BBS</title>
		<link>https://phosphorbbs.net/tags/parser/</link>
		<description>Recent content in Parser on Phosphor BBS</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Wed, 23 Sep 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://phosphorbbs.net/tags/parser/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Markdown in a Terminal: Building a MarkdownWidget for jterm</title>
				<link>https://phosphorbbs.net/blog/markdown-in-a-terminal-building-the-markdownwidget/</link>
				<pubDate>Wed, 23 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://phosphorbbs.net/blog/markdown-in-a-terminal-building-the-markdownwidget/</guid>
				<description>&lt;p&gt;Every BBS has the same problem: text that wants to be formatted. Help screens with headings and bullet lists. News articles with paragraphs. Mail that would really use a code block for that error dump. The traditional answers are all bad in the same way — hard-coded ANSI sequences baked into strings, a private wiki-syntax nobody else can read, or walls of plain text with no structure at all.&lt;/p&gt;&#xA;&lt;p&gt;jterm now ships a third answer: a &lt;strong&gt;MarkdownWidget&lt;/strong&gt; that parses real markdown and renders it as styled terminal lines.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
