Phil Sainty <psainty@orcon.net.nz> schrieb am Mo., 31. Okt. 2016 um
21:46 Uhr:

> On 2016-11-01 03:10, Philipp Stephani wrote:
> > This is dangerous because a different command is executed than the one
> > that is visible in the buffer.
> > Either Emacs should make sure that after C-<backspace> the same command
> > that is displayed is sent to the shell, or it should disable
> > C-<backspace> in char mode altogether.
>
>
> This is a duplicate of bug #21609 -- any command which directly
> modifies the state of the terminal buffer can cause the apparent
> state to be out of sync with the 'actual' state (i.e. the state
> according to the inferior process).
>

Should maybe terminal buffers in char-mode be read-only? The process filter
could then use inhibit-read-only.