> Filed by Claude (Claude Code) on behalf of @whiskeytuesday, who hit this on their machine and reviewed this report before it was filed.

## Summary

`omarchy-font-set` never delivers its "you must restart your terminal" notifications. Both calls pass the message where `omarchy-notification-send` expects a *glyph*, so the message is consumed by `-g`, no headline argument is left, and `omarchy-notification-send` exits 1 with its usage string instead of sending anything.

The failure is silent in normal use: `omarchy-font-set` has no `set -e`, and the two calls are the last statements before `omarchy-hook`, so the script still exits 0. Users who change fonts while Ghostty or Foot is running are simply never told to restart, and the stale font reads as "the font change didn't work".

## Steps to reproduce

With Ghostty (or Foot) running:

```bash
omarchy font set "JetBrainsMono Nerd Font"
```

Observed on stdout, in place of the notification:

```
Usage: omarchy-notification-send [--exec <command>] [--app-name <app-name>] [-g <glyph>] [-u <low|normal|critical>] [--image <path-or-uri>] <headline> [description] [notify-send options]
```

Reduced to the exact call the script makes:

```bash
$ omarchy-notification-send -g  "You must restart Ghostty to see font change"
Usage: omarchy-notification-send [--exec <command>] ... <headline> [description] [notify-send options]
$ echo $?
1
```

No notification appears in either case.

## Root cause

`bin/omarchy-font-set` (lines 71 and 75 on `master`):

```bash
omarchy-notification-send -g  "You must restart Ghostty to see font change"
omarchy-notification-send -g  "You must restart Foot to see font change"
```

`-g` is `--glyph` and takes a value (`bin/omarchy-notification-send`, `parse_omarchy_option`):

```bash
-g | --glyph)
  if (($# < 2)); then ... fi
  glyph=$2
  parsed_option_args=2
```

So `glyph` becomes `"You must restart Ghostty to see font change"`, `$#` drops to 0, and the `(($# < 1))` guard prints usage and exits 1.

The doubled space after `-g` on both lines suggests a glyph was intended there and was lost at some point.

## Expected

A notification with a headline, as `omarchy-display-text-size` does for the same Foot-cannot-reload case:

```bash
omarchy-notification-send "Restart Foot to apply the new terminal font size" ...
```

## Suggested fix

Either drop the empty flag:

```bash
omarchy-notification-send "You must restart Ghostty to see font change"
```

or restore a glyph:

```bash
omarchy-notification-send -g "󰛖" "You must restart Ghostty to see font change"
```

Both verified working on the affected machine (exit 0, notification delivered).

A guard in `omarchy-notification-send` — warning when a `--glyph` value looks like a sentence, or making a missing headline noisier than a usage line on stdout — would also have surfaced this at the call site.

## System

AMD Ryzen 7 PRO 5850U, AMD Cezanne (Radeon Vega Mobile), Omarchy 4.0.0-1

| | |
|---|---|
| Omarchy | 4.0.0-1 |
| Hyprland | 0.56.2 |
| Kernel | 7.1.8-arch1-3 |
| Machine | ThinkPad P14s Gen 2a |
| Ghostty | 1.3.1-arch2 |
| Foot | 1.27.0 |

Full `omarchy-debug` output omitted: this is an argument-order defect that reproduces from the source alone and is present on `master` (verified via `repos/basecamp/omarchy/contents/bin/omarchy-font-set` at time of filing), not just in the installed package. Happy to attach the log if useful.

Checked for duplicates before filing; nothing found in issues or PRs. Note that open PR #6958 modifies `bin/omarchy-font-set` for an unrelated reason and stubs `omarchy-notification-send` in its new test, but does not change these two lines.