Typing tells g. where its edit ended, so no edit scans the whole file twice to find it

setEditText found the last edit's end by comparing the old and new texts from both ends and counting rows to it, twice over the file on every keystroke: edit-char grew with the file (+135% at 300k lines). Typing, deleting, Enter and Tab now pass the end they know (setEditTextEnd); the comparison stays for the edits that do not say (paste, pipes, s). perf edit-char: 50k lines 16661 -> 15286 us, 300k lines 30507 -> 22291 us (render alone ~13.6 ms of each, the render agent's).

Co-Authored-By: Claude Opus 5.5 <[email protected]>

0 files changed, 0 insertions, 0 deletions