When double-click skips the choice

You know what you want: open this file with that app, just this once. The shell already knows several handlers exist. Double-click (or Enter) does not ask. It commits.

There is no native modifier on Windows File Explorer that intercepts that handoff and forces the Open with dialog. Same story on macOS Finder and on the usual Linux file managers (Nautilus, Dolphin, and friends). You get there through the context menu, Properties / Get Info, or a third-party default-handler wrapper — never through a gesture that means choose now at the moment of open.

That is a missing interrupt, not a missing menu item.

The gap is cross-platform

Stock paths still work. They are just the wrong altitude for a frequent, momentary decision:

• Windows: Shift+F10 (or the Menu key), then Open with; or Properties → Change…
• macOS: Control-click → Open With; Control+Option+click for Always Open With; Command+I for the inspector
• Linux: context menu → Open With Other Application (wording varies)

Useful. Discoverable if you already hunt menus. Invisible if your hand is already on the mouse for a double-click.

Modifier+click patterns that do exist are taken by other jobs. Option+double-click in Finder opens and closes the folder window. Middle-click on a folder often opens a tab. None of those mean “pick a handler for this file.”

Claim the unused interrupt

Two bindings sit largely unused for files and map cleanly to the job:

1. Ctrl + double-click — “I want to control which application opens this.” Semantic mnemonic, not a random chord. On Windows Explorer it has no stock file-open binding; that makes it a viable interrupt.
2. Middle-click on a file — folders already own middle-click for tabs in many environments; files often do nothing (Explorer), are ignored (Nautilus), or silently default-open (Dolphin). Reclaiming middle-click on files for Open with keeps the “alternate open” family consistent without stealing folder-tab behavior.

Either binding should open the system app picker for the selected file — temporary choice, same honesty surface as today’s Open with — not silently rebind the permanent default. Permanent defaults stay in Properties / Get Info / “Always.”

Product representation again

Association databases already list multiple capable apps. The first-class open gesture pretends there is only one. That is the same class of bug as hiding a real option the engine already knows: knowledge exists behind the glass; the interrupt never arrives at the fingertip.

Intuition over backwards convention applies. Teaching everyone a deeper context-menu path forever is temporary theater. A one-gesture interrupt compounds across every file type, every day, on every desktop that still treats double-click as an unstoppable commitment.

Where to go next

The idea is the interrupt. Recipes for AutoHotkey on Windows, Finder/third-party patterns on macOS, and Linux wrappers or input hooks live in the docs — not here.

• Docs — Open-with interrupt
• Sibling pattern — When example files lose their type (association honesty once you do open)

OS vendors and file-manager maintainers can ship this as a first-class binding. Until then, the interrupt is small enough to prototype, clear enough to argue for, and honest enough to belong in the repertoire.