Skip to main content
Emacs

Return to Question

added 188 characters in body
Source Link
Pablo
Pablo
  • 369
  • 2
  • 8

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.

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.

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.

Source Link
Pablo
Pablo
  • 369
  • 2
  • 8

`kill-words` and related commands erase text in read-only buffers

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.