From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ryan Johnson Newsgroups: gmane.emacs.bugs Subject: bug#7117: 23.2.2 mangles terminal escape sequences Date: Thu, 30 Sep 2010 18:11:58 +0200 Message-ID: <4CA4B6CE.7060101@ece.cmu.edu> References: <4CA089B5.80601@ece.cmu.edu> <4CA174DA.701@ece.cmu.edu> <4CA47684.5020806@ece.cmu.edu> <4CA4A10B.8050201@ece.cmu.edu> <837hi3p994.fsf@gnu.org> <4CA4A948.70907@ece.cmu.edu> <8362xnp76n.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1285864901 28272 80.91.229.12 (30 Sep 2010 16:41:41 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 30 Sep 2010 16:41:41 +0000 (UTC) Cc: 7117@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Sep 30 18:41:37 2010 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1P1MCO-00068Z-Jw for geb-bug-gnu-emacs@m.gmane.org; Thu, 30 Sep 2010 18:41:36 +0200 Original-Received: from localhost ([127.0.0.1]:48935 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P1MCO-0004rF-0a for geb-bug-gnu-emacs@m.gmane.org; Thu, 30 Sep 2010 12:41:36 -0400 Original-Received: from [140.186.70.92] (port=37128 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P1MCG-0004q3-8D for bug-gnu-emacs@gnu.org; Thu, 30 Sep 2010 12:41:29 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1P1MCE-0005Kr-Qr for bug-gnu-emacs@gnu.org; Thu, 30 Sep 2010 12:41:28 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:53730) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1P1MCE-0005Kn-P6 for bug-gnu-emacs@gnu.org; Thu, 30 Sep 2010 12:41:26 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.69) (envelope-from ) id 1P1Lhq-0001kU-Q4; Thu, 30 Sep 2010 12:10:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Ryan Johnson Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-To: owner@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 30 Sep 2010 16:10:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 7117 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 7117-submit@debbugs.gnu.org id=B7117.12858629476703 (code B ref 7117); Thu, 30 Sep 2010 16:10:02 +0000 Original-Received: (at 7117) by debbugs.gnu.org; 30 Sep 2010 16:09:07 +0000 Original-Received: from localhost ([127.0.0.1] helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1P1Lgx-0001k4-5X for submit@debbugs.gnu.org; Thu, 30 Sep 2010 12:09:07 -0400 Original-Received: from bache.ece.cmu.edu ([128.2.129.23]) by debbugs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1P1Lgu-0001ji-N2 for 7117@debbugs.gnu.org; Thu, 30 Sep 2010 12:09:05 -0400 Original-Received: from [128.178.77.144] (diaspc12.epfl.ch [128.178.77.144]) by bache.ece.cmu.edu (Postfix) with ESMTP id 032AF194; Thu, 30 Sep 2010 12:11:59 -0400 (EDT) User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100802 Lightning/1.0b2 Thunderbird/3.1.2 In-Reply-To: <8362xnp76n.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.11 Precedence: list Resent-Date: Thu, 30 Sep 2010 12:10:02 -0400 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:40579 Archived-At: On 9/30/2010 5:44 PM, Eli Zaretskii wrote: >> Date: Thu, 30 Sep 2010 17:14:16 +0200 >> From: Ryan Johnson >> 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? It's not just keyboard driven. It's a mouse-enabled terminal and the mouse click/wheel actions cause the issues (each one generates a burst of 6-12 characters). As you say, I don't think I've ever seen this happen with keyboard input; pasting commands from a remote X clipboard might have a similar effect, but I've never tried. In the past, scrolling once or twice past buffer begin/end wasn't guaranteed to dump garbage. It would just beep/flash most of the time, and the slow network connection didn't seem to make it worse. Now, if I'm not on intranet, virtually every scroll past-end will dump garbage somewhere. Also, the problem I hit this morning was not related to fast typing/clicking over a slow connection. I was doing an ediff-files session, and about every other time I clicked on a buffer to edit a conflict, emacs would reward me with a mangled escape code... sometimes where point had been and sometimes where it ended up. I wasn't typing fast or clicking madly -- it was more like "a n n n n b n n " The latter problem went away once I got to work and had a fast network; and the former happens much less frequently here (unless I give the wheel a really good spin, but that's understandable). Ryan