Skip to content

Instantly share code, notes, and snippets.

View the-mikedavis's full-sized avatar

Michael Davis the-mikedavis

View GitHub Profile
@GrantCuster
GrantCuster / userChrome.css
Last active May 31, 2025 15:41
My minimal, gruvbox inspired Firefox customization
/* Check out https://www.reddit.com/r/FirefoxCSS/ for an explanation on how to customize */
/* This hides a ton of buttons because I use Vimium for most navigation */
/* Screenshot at https://feed.grantcuster.com/post/1596224341/ */
:root {
--base00: #282828;
--base01: #3c3836;
--base02: #504945;
--base04: #bdae93;
--base05: #d5c4a1;
@christianparpart
christianparpart / terminal-synchronized-output.md
Last active July 3, 2025 13:46
Terminal Spec: Synchronized Output

Synchronized Output

Synchronized output is merely implementing the feature as inspired by iTerm2 synchronized output, except that it's not using the rare DCS but rather the well known SM ? and RM ?. iTerm2 has now also adopted to use the new syntax instead of using DCS.

Semantics

When rendering the screen of the terminal, the Emulator usually iterates through each visible grid cell and renders its current state. With applications updating the screen a at higher frequency this can cause tearing.

This mode attempts to mitigate that.

Introduction

There are two types of consumer processing failures:

  1. Poison messages. Messages that are badly formatted and either cause the consuming application to crash or otherwise fail to process the message.

  2. Downstream dependency failures. I.e. when a message is valid but a downstream dependency such as a database isn't available. This category can further be subdived into:

    a. All messages on the queue are destined to the same unavailable downstream.

b. The downstream dependencies may be different depending on the message. (e.g. different databases or integration endpoints).