From: Philipp Stephani <p.stephani2@gmail.com>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: 24837@debbugs.gnu.org, 21609@debbugs.gnu.org
Subject: bug#21609: bug#24837: 26.0.50; term.el: In char mode, displayed and executed commands can differ
Date: Wed, 23 Nov 2016 20:21:56 +0000 [thread overview]
Message-ID: <CAArVCkRhAueaw+cVBdfswrcKBTjy1GCLc_YFetPGNdG9DAfcSg@mail.gmail.com> (raw)
In-Reply-To: <08c3b161-174d-1fb7-5df4-bbf7f7d47ee9@orcon.net.nz>
[-- Attachment #1: Type: text/plain, Size: 981 bytes --]
Phil Sainty <psainty@orcon.net.nz> schrieb am Mi., 23. Nov. 2016 um
21:09 Uhr:
> 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.
>
>
Hmm, then maybe the entire buffer also needs to be made intangible, except
for the actual position of the terminal cursor?
[-- Attachment #2: Type: text/html, Size: 1712 bytes --]
next prev parent reply other threads:[~2016-11-23 20:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 14:10 bug#24837: 26.0.50; term.el: In char mode, displayed and executed commands can differ Philipp Stephani
2016-10-31 20:46 ` Phil Sainty
2016-11-23 19:44 ` Philipp Stephani
2016-11-23 20:08 ` bug#21609: " Phil Sainty
2016-11-23 20:21 ` Philipp Stephani [this message]
2017-09-02 14:14 ` Eli Zaretskii
2017-09-03 2:58 ` Phil Sainty
2017-09-03 3:09 ` bug#21609: " Phil Sainty
2017-09-04 9:55 ` Phil Sainty
2017-09-04 10:10 ` bug#24837: " Phil Sainty
2017-09-04 11:59 ` bug#21609: " Phil Sainty
2017-09-24 10:59 ` Philipp Stephani
2017-09-25 0:48 ` bug#21609: " Phil Sainty
2017-09-25 3:09 ` Phil Sainty
2017-09-29 8:37 ` Eli Zaretskii
2017-10-08 12:39 ` bug#21609: " Phil Sainty
2017-10-09 14:04 ` Phil Sainty
2017-10-09 15:32 ` Eli Zaretskii
2017-10-10 10:16 ` bug#28777: Clarifying the temporary documentation update marks in etc/NEWS Phil Sainty
2017-10-10 12:25 ` Eli Zaretskii
2017-10-10 11:11 ` bug#24837: bug#21609: bug#24837: 26.0.50; term.el: In char mode, displayed and executed commands can differ Phil Sainty
2017-10-10 12:35 ` Eli Zaretskii
2017-10-12 10:54 ` Phil Sainty
2017-10-12 12:04 ` bug#21609: " Eli Zaretskii
2017-10-21 8:20 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAArVCkRhAueaw+cVBdfswrcKBTjy1GCLc_YFetPGNdG9DAfcSg@mail.gmail.com \
--to=p.stephani2@gmail.com \
--cc=21609@debbugs.gnu.org \
--cc=24837@debbugs.gnu.org \
--cc=psainty@orcon.net.nz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).