In fleet view, text cut in one input can now be pasted into another.
What's wrong with this entry?
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.
- 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.
killRing: k7o(),
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Background task notifications arrive inside a system-reminder
Both mention background task
-
v2.1.235
Several finished background tasks now report as one line
Both mention background task
-
v2.1.236
Background-task notices no longer look like user approval
Both mention background task