{"version":"2.1.233","anchor":"fleet-view-shares-one-cut-yank-buffer-across-its-inputs","canonical_anchor":"fleet-view-shares-one-cut-yank-buffer-across-its-inputs","heading":"Fleet view shares one cut\/yank buffer across its inputs","tier":"notice","area":"Background Tasks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/fleet-view-shares-one-cut-yank-buffer-across-its-inputs","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### Fleet view shares one cut\/yank buffer across its inputs\n\nIn fleet view, text cut in one input can now be pasted into another.\n\n**What**\n\nText 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.\n\n**Details**\n\n- 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.\n- Inputs outside the fleet view are unaffected and still use the ambient default.\n\n**Evidence**\n\n`killRing: k7o(),`\n\n- Area: Background Tasks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}