From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#17497: 24.4.50; TTY menu glitches Date: Wed, 04 Jun 2014 00:07:24 +0300 Message-ID: <83ppip8zxv.fsf@gnu.org> References: <83vbslbuqr.fsf@gnu.org> <20140531200947.GA779@aerie.jexium-island.net> <83lhtgbrd6.fsf@gnu.org> <20140601152657.GA15078@aerie.jexium-island.net> <838upgbnra.fsf@gnu.org> <20140601171244.GA9362@aerie.jexium-island.net> <20140601171817.GB9362@aerie.jexium-island.net> <20140603184749.GA3646@aerie.jexium-island.net> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1401829704 27932 80.91.229.3 (3 Jun 2014 21:08:24 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 3 Jun 2014 21:08:24 +0000 (UTC) Cc: 17497@debbugs.gnu.org To: dickey@his.com Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Jun 03 23:08:16 2014 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1WrvwO-0002aa-36 for geb-bug-gnu-emacs@m.gmane.org; Tue, 03 Jun 2014 23:08:16 +0200 Original-Received: from localhost ([::1]:55969 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WrvwN-0008Iy-7e for geb-bug-gnu-emacs@m.gmane.org; Tue, 03 Jun 2014 17:08:15 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54532) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WrvwF-0008H2-FG for bug-gnu-emacs@gnu.org; Tue, 03 Jun 2014 17:08:12 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WrvwA-00076g-E1 for bug-gnu-emacs@gnu.org; Tue, 03 Jun 2014 17:08:07 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:43843) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WrvwA-00076c-Ah for bug-gnu-emacs@gnu.org; Tue, 03 Jun 2014 17:08:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1Wrvw9-0002uK-Ju for bug-gnu-emacs@gnu.org; Tue, 03 Jun 2014 17:08:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 03 Jun 2014 21:08:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 17497 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 17497-submit@debbugs.gnu.org id=B17497.140182966011137 (code B ref 17497); Tue, 03 Jun 2014 21:08:01 +0000 Original-Received: (at 17497) by debbugs.gnu.org; 3 Jun 2014 21:07:40 +0000 Original-Received: from localhost ([127.0.0.1]:42719 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1Wrvvo-0002tY-0m for submit@debbugs.gnu.org; Tue, 03 Jun 2014 17:07:40 -0400 Original-Received: from mtaout22.012.net.il ([80.179.55.172]:42436) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1Wrvvk-0002tJ-MJ for 17497@debbugs.gnu.org; Tue, 03 Jun 2014 17:07:38 -0400 Original-Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0N6M004002MWCV00@a-mtaout22.012.net.il> for 17497@debbugs.gnu.org; Wed, 04 Jun 2014 00:07:30 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0N6M0042C2OHCE10@a-mtaout22.012.net.il>; Wed, 04 Jun 2014 00:07:30 +0300 (IDT) In-reply-to: <20140603184749.GA3646@aerie.jexium-island.net> X-012-Sender: halo1@inter.net.il X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.43 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: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:89955 Archived-At: > Date: Tue, 03 Jun 2014 14:47:49 -0400 > From: Thomas Dickey > Cc: Thomas Dickey , 17497@debbugs.gnu.org, > Eli Zaretskii > > > Currently, we're not concerned about optimization, just about tracking > > down a display glitch. The tricky part of this glitch is that if we > > record&replay Emacs's output, the "replay" does not suffer from the > > same glitch. > > sure - but I gave my best answer at the outset. The behavior which > you are describing won't show up by doing replay's, because it would > occur when you have input (from the keyboard) interfering with the > output. > > > So apparently the terminal emulator behaves differently in the "live" > > case than in the "replay" case for some reason. We tried to replay at > > different speeds to see if it was related to timing, but to no avail. > > > > To me, the next logical explanation is that the terminal emulator's > > behavior is influenced y the relative timing of *input* and output. > > :-) > > > For that reasons, your ncurses explanation is very interesting, yet > > I can't imagine how it can be directly related since our "record&replay" > > is done "after" ncurses, directly in the stream between Emacs's process > > and the terminal emulator. > > > > Do you have some other insight that could explain why the terminal > > emulator would react differently in the "live" case than in the > > "replay" case? > > repeating: if the cursor-key sequence of characters is misinterpreted > (for example due to timeouts), then fragments of the sequences will > echo as unexpected characters. > > Incidentally, if an *output* splits up an escape sequence across > buffers in fflush's, then that can also open up holes in timing. > But I think that's less of concern... All this, including input interfering with output, happens during normal Emacs redisplay, but we have never heard any complaints about corrupted display like the ones we get with the menus. The Emacs code which outputs commands and text to the terminal does not know whether a menu has been dropped or not, it just compares the previous display with the desired one, and sends commands to update the regions of the screen that has been changed.