This is a suppliment to the guide provided on the namelessMC tutorials page.
I hereby claim:
- I am codingwithanxiety on github.
- I am roselie (https://keybase.io/roselie) on keybase.
- I have a public key ASDwHaFhlQSFD9EwZGlZan9D3iKLkJgh1tP7m_TylX8Sigo
To claim this, I am signing this object:
| --- A notification module for WezTerm using notify-send. | |
| -- This module provides functionality to send notifications using the 'notify-send' command, | |
| -- which is available on most Linux distributions that implement the org.freedesktop.Notifications specification. | |
| local wezterm = require 'wezterm' | |
| local M = {} | |
| --- Check if a value exists in a table. | |
| -- @local |
| { pkgs ? import <nixpkgs> {} }: | |
| pkgs.callPackage ./fchat-horizon.nix {} |
Hey, folks. It’s Rose — Project Lead (PL) for Horizon and F-Chat 3.0, and a developer on the F-List team.
I originally wrote Horizon’s Bus Factor when I only held the PL role for Horizon. Since then, my responsibilities and involved projects have expanded. This document updates and extends that plan to cover both Horizon and F-Chat 3.0.
This document exists to reduce uncertainty, protect contributors, and ensure continuity if I am temporarily or permanently unavailable.
This file is the authoritative list of FPM record keys. A key exists once it has
an entry here; its meaning is what its entry says. The specification
(fpm-standard.md) defines the format itself; this registry defines the
vocabulary. keys.json mirrors these entries for tooling and MUST stay in sync.
Registry rules, from specification section 3.6:
- Keys are never removed or reused. A key that turns out badly is marked