Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.

Inbox
ReportR-4230GitHub issuePublicReceived

Tmux extended-keys setting for `Ctrl + Shift + X` bindings

Reported by EFrMG · filed Mar 17, 2026Closed upstream on 2026-07-18. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

Received and recorded verbatim. Nothing has been checked yet.

At a glance

1 · What is claimed?
Only the report text below — no validator has restated it as checkable claims yet.
2 · What does it affect?
Not yet mapped to any requirement or component.
3 · Is it reproducible?
No validation has been run yet.
4 · What remains unclear?
  • Not validated yet: no claims, no reproducer.
5 · What happens next?
Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.

Original report

Tmux extended-keys setting for `Ctrl + Shift + X` bindingsrevision 1 · captured 2026-10-04 11:49 UTC via poll

System details

Omarchy 3.4.2

What's wrong?

Tmux lacks support for some types of bindings

Adding set -s extended-keys on enables the CSI u keyboard protocol, which is newer and poor tmux was not born with. It allows for more complex bindings that would register as partial bindings otherwise.

Reproduce it

The simplest way I have is to create a markdown file (.md) and write the following:

# a heading
a paragraph right below it

When one saves on nvim with Ctrl + S, the two lines get a newline inserted in between by the formatter. A way to avoid that is to run noa w; so here's a binding for it:

-- Save without formatting
vim.keymap.set({ "n", "v", "i" }, "<C-S-s>", "<Cmd>noa w<CR>", { desc = "Save w/o formatting", silent = true })

Then, from inside and outside tmux one could try to press Ctrl + Shift + S on that buffer, and check after the migration how from inside tmux it does instead works (not adding the newline).

View raw text
### System details

Omarchy 3.4.2

### What's wrong?

## Tmux lacks support for some types of bindings

Adding `set -s extended-keys on` enables the **CSI u keyboard protocol**, which is newer and poor tmux was not born with. It allows for more complex bindings that would register as partial bindings otherwise.

## Reproduce it

The simplest way I have is to create a markdown file (`.md`) and write the following:

```
# a heading
a paragraph right below it
```

When one saves on nvim with `Ctrl + S`, the two lines get a newline inserted in between by the formatter. A way to avoid that is to run `noa w`; so here's a binding for it:

```lua
-- Save without formatting
vim.keymap.set({ "n", "v", "i" }, "<C-S-s>", "<Cmd>noa w<CR>", { desc = "Save w/o formatting", silent = true })
```

Then, from inside and outside tmux one could try to press `Ctrl + Shift + S` on that buffer, and check after the migration how from inside tmux it does instead works (not adding the newline).

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

Not linked to any known issue, other report or change yet.

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

No decision has been recorded yet.