<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Input Handling on Phosphor BBS</title>
		<link>https://phosphorbbs.net/tags/input-handling/</link>
		<description>Recent content in Input Handling on Phosphor BBS</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sun, 20 Sep 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://phosphorbbs.net/tags/input-handling/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>The Case of the Very Random Dead Ctrl-T</title>
				<link>https://phosphorbbs.net/blog/the-case-of-the-very-random-dead-ctrl-t/</link>
				<pubDate>Sun, 20 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://phosphorbbs.net/blog/the-case-of-the-very-random-dead-ctrl-t/</guid>
				<description>&lt;p&gt;Two weeks into the popup chat feature, users started reporting the same thing in different words: &lt;em&gt;Ctrl-T is very random.&lt;/em&gt; Sometimes it opened the chat popup instantly. Sometimes it did nothing — not even an error. Same terminal, same screen, same key. First press of the session would work, three presses in a row would work, then a press after closing the popup with ESC would go dead. Then it would work again. There was no pattern, which was the most maddening part — a consistently broken key is a bug report; an inconsistently broken key is a haunting.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
