unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: Mark Plaksin <happy@mcplaksin.org>, emacs-devel@gnu.org
Subject: Re: term.el and undo
Date: 25 Aug 2004 10:03:34 +0200	[thread overview]
Message-ID: <x51xhv1w6h.fsf@lola.goethe.zz> (raw)
In-Reply-To: <E1Bzpb8-0005ny-I4@fencepost.gnu.org>

Richard Stallman <rms@gnu.org> writes:

>     Personally I'd be happy with *no* undo in term buffers.  Undo
>     with the patch works as expected when in line mode and editing a
>     command-line.  That's the only time that undo seems useful.
>     With the patch using undo at any other time makes the cursor
>     jump around from line to line which is confusing.
> 
> I do not understand what you mean.  Could you describe a precise
> test case in which this jumping occurs?

I'd suppose that the terminal has one idea of the cursor location, and
undo happens at other points.

However, since the whole point of term is to provide an
ncurses-capable terminal, and since undo or any other output or cursor
movement operation not initiated from the device writing into the
pseudotty would lead to a discrepancy between the screen contents and
the application's expectations, _any_ editing by the user including
undo would seem completely pointless.  term probably keeps track of
its own cursor position, so at least you can use copy and paste to do
screenshots as long as the application is not writing to the screen,
but apart from read-only operations like that, user access does not
seem sensible.  "Undo" might be a curiosity to go back in time in the
term, but just like it would seem necessary to move the cursor to the
expected place before inserting new output, it would seem necessary to
completely redo all changes before the application writes new
material.

Since this would require specialized undo semantics, I think we are
better off with disabling it altogether by default.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2004-08-25  8:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-22 23:39 term.el and undo Richard Stallman
2004-08-23  1:43 ` undo in compilation mode Karl Chen
2004-08-23 23:26   ` Richard Stallman
2004-08-23 23:32     ` Florian Weimer
2004-08-24 21:02       ` Richard Stallman
2004-08-24 23:25         ` Karl Chen
2004-08-24  2:08     ` Stefan
2004-08-24 14:50       ` Karl Chen
2004-08-25  4:41         ` Richard Stallman
2004-08-24 20:13 ` term.el and undo Mark Plaksin
2004-08-25  4:41   ` Richard Stallman
2004-08-25  8:03     ` David Kastrup [this message]
2004-08-25 12:59       ` Florian Weimer
2004-08-25 20:25         ` Mark Plaksin
2004-08-25 22:40       ` Richard Stallman

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=x51xhv1w6h.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=happy@mcplaksin.org \
    /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).