Module magit_stash_show_mode 

MG.15: *magit:stash:<n>* — one stash’s patch.

magit-stash listed stashes but had no <CR>: the only way to see what a stash actually contained was magit-status, where <CR> toggles the patch inline among the other sections. That was the last hole in MG.11’s <CR> uniformity rule — every other list view navigates to a detail buffer, and “apply this to my working tree?” is exactly the question you want answered before pressing a.

magit-status’s inline toggle is deliberately left alone: there a stash is one row among many and expanding in place keeps the surrounding context. Here the stash IS the subject.

Fixed-content view, like magit-revision-mode: gr is a no-op because stash@{n}’s patch does not change under a fixed index. (Dropping or popping the stash renumbers the other entries — which is why the buffer name carries the index it was opened at, and why the stash list is the place that refreshes, not this.)

Structs

MagitStashShowMode

StashShowState

MG.23g: what a / - need to know about this buffer — where the repository is. The stash index is already in the buffer name; the working directory is not, and a git apply needs one.

Functions

stash_view_rest

This view’s rest for stash index — the single place the <CR> handler and this mode’s parser agree on the format.

Type Aliases

StashShowStatesHandle

Service alias for this mode’s per-buffer state (feedback_servicesregistry_arc_typeid).