Killing commands, such as kill-word, have started to erase text in read-only buffers. For example, invoking kill-word in dired-mode or mu4e-headers-mode will delete words from a filename or from an email subject, respectively. This has no destructive effects: the files/emails/etc are not themselves affected. Does anyone know what might be causing this behavior?
All my attempts to diagnose it have failed. I tried to bisect the init file, but the issue does not occur immediately after restarting; it happens only after 5–15 minutes of starting the new session, making bisection infeasible.
emacs -Q(no init file)? If not, bisect your init file to find the culprit. If yes, provide a step-by-step recipe to repro (fromemacs -Q).emacs -Q. Unfortunately, I tried to bisect the init file, but the issue does not occur immediately after restarting; it happens only after 5–15 minutes of starting the new session, making bisection infeasible. That’s why I thought of asking here whether anyone had thoughts on what might be causing it.inhibit-read-only(which should only ever be bound with some very specific limited scope).inhibit-read-onlyis set tot, so withdebug-on-variable-changeI should be able to identify the package that is setting its value.