{"version":"2.1.221","anchor":"vim-register-and-last-find-state-persist-across-inputs-in-a-","canonical_anchor":"vim-register-and-last-find-state-persist-across-inputs-in-a-","heading":"Vim register and last-find state persist across inputs in a session","tier":"use","area":"Terminal UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/vim-register-and-last-find-state-persist-across-inputs-in-a-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Vim register and last-find state persist across inputs in a session\n\nVim yanks and f\/t searches now carry over between prompts instead of resetting each time.\n\n**What**\n\nYanks and f\/t searches now carry from one input to the next, because the shared part of the vim state was lifted out of the per-editor object into session state.\n\n**Details**\n\n- The per-editor vim state lost `lastChange`; dot-repeat is now tracked on a component ref instead.\n- What remains, `{ lastFind, register, registerIsLinewise }`, is stored once in session state as `vimSharedState`.\n\n**Evidence**\n\n`vimSharedState`\n\n- Area: Terminal UI\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 0\/5"}