[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#21609: bug#24837: 26.0.50; term.el: In char mode, displayed and exec
|
From: |
Phil Sainty |
|
Subject: |
bug#21609: bug#24837: 26.0.50; term.el: In char mode, displayed and executed commands can differ |
|
Date: |
Thu, 24 Nov 2016 09:08:59 +1300 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 |
On 24/11/16 08:44, Philipp Stephani wrote:
> Phil Sainty <psainty@orcon.net.nz> schrieb am Mo., 31. Okt. 2016 um
>> 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.
That's an interesting thought, and may be worth investigating (offhand
I've no idea whether it's workable), but note that it's not sufficient
to deal with all cases -- any Emacs command which moves point can create
an inconsistent state without modifying the buffer contents.