You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Background TasksArea: what it touches
ImprovementsKind: in v2.1.233,
ImprovementsSection of the release
What
Text you cut in one fleet view input can be yanked into another. The fleet view now creates its own kill ring and hands it to every input it renders, instead of each input falling back to the process-wide default.
Details
The kill ring (the buffer holding cut text for later yanking) is created once by the fleet view host state and passed down through a provider.
Inputs outside the fleet view are unaffected and still use the ambient default.
Evidence
killRing: k7o(),
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
