{"version":"2.1.239","anchor":"readline-style-word-motion-and-a-kill-ring-in-the-text-input","canonical_anchor":"readline-style-word-motion-and-a-kill-ring-in-the-text-input","heading":"Readline-style word motion and a kill ring in the text input","tier":"use","area":"Text Input","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/readline-style-word-motion-and-a-kill-ring-in-the-text-input","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Readline-style word motion and a kill ring in the text input\n\nThe prompt box gained readline word motions and a kill ring on Meta-Backspace, Meta-d and Ctrl-D.\n\n**What**\n\nThe prompt input gained a second set of word motions modelled on readline: forward and backward word movement, kill-word and backward-kill-word, wired to Meta-Backspace, Meta-d and Ctrl-D, with killed text pushed onto a kill ring rather than simply deleted. The older word-motion behaviour is still present for the other mode.\n\n**Details**\n\n- Word boundaries for the new mode come from a separate cache with readline's boundary rules, kept alongside the existing one.\n- Meta-d appends the killed word to the kill ring with a direction, so successive kills accumulate.\n- The check that interrupts on keypress now runs before the early return for control keys.\n- Which of the two modes is active is decided by an internal boolean that does not trace to any setting or command-line flag in this build.\n\n**Evidence**\n\n`getReadlineWordBoundaries`, `killWord`\n\n- Area: Text Input\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5"}