From: Eli Zaretskii <eliz@gnu.org>
To: Ryan Johnson <ryanjohn@ece.cmu.edu>
Cc: 7117@debbugs.gnu.org
Subject: bug#7117: 23.2.2 mangles terminal escape sequences
Date: Thu, 30 Sep 2010 17:44:32 +0200 [thread overview]
Message-ID: <8362xnp76n.fsf@gnu.org> (raw)
In-Reply-To: <4CA4A948.70907@ece.cmu.edu>
> Date: Thu, 30 Sep 2010 17:14:16 +0200
> From: Ryan Johnson <ryanjohn@ece.cmu.edu>
> CC: monnier@iro.umontreal.ca, 7117@debbugs.gnu.org
>
> >> From the above, it seems that scrolling past beginning or end of buffer
> >> triggers an error, which I guess is somewhat justifiable.
> > Indeed. Perhaps we need some infrastructure to ignore errors in this
> > case (I assume `ignore-errors' won't help). Or maybe we should allow
> > not to discard input when we signal an error. Or maybe discard-input
> > should be smarter, and not discard partial escape sequences?
> One thing I don't get is, I've been using emacs over painfully slow ssh
> connections for literally years -- sometimes slow enough that keystrokes
> take visible time to echo. This was never really an issue before.
What would you expect to see, that would cause you think it was "an
issue"? When Emacs is keyboard-driven, typing text and scrolling
commands seldom happen in such a quick succession that hitting end of
buffer while scrolling would discard text you typed meanwhile. And
even if it did, how would you know for sure you actually typed it?
next prev parent reply other threads:[~2010-09-30 15:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 12:10 bug#7117: 23.2.2 mangles terminal escape sequences Ryan Johnson
2010-09-27 20:52 ` Stefan Monnier
2010-09-28 4:53 ` Ryan Johnson
2010-09-30 11:37 ` Ryan Johnson
2010-09-30 14:39 ` Ryan Johnson
2010-09-30 14:59 ` Eli Zaretskii
2010-09-30 15:14 ` Ryan Johnson
2010-09-30 15:44 ` Eli Zaretskii [this message]
2010-09-30 16:11 ` Ryan Johnson
2022-02-07 0:33 ` Lars Ingebrigtsen
2022-03-07 2:37 ` Lars Ingebrigtsen
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=8362xnp76n.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=7117@debbugs.gnu.org \
--cc=ryanjohn@ece.cmu.edu \
/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).