From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Eli Zaretskii" Newsgroups: gmane.emacs.bugs Subject: Re: Bug in GNU Emacs display code Date: Tue, 01 Mar 2005 21:38:17 +0200 Message-ID: <01c51e96$Blat.v2.4$5d968380@zahav.net.il> References: <20050301043930.3F54923CFA@ws5-3.us4.outblaze.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: main.gmane.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7BIT X-Trace: sea.gmane.org 1109706087 29849 80.91.229.2 (1 Mar 2005 19:41:27 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 1 Mar 2005 19:41:27 +0000 (UTC) Cc: bug-emacs@gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Mar 01 20:41:27 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1D6DEs-00072e-NX for geb-bug-gnu-emacs@m.gmane.org; Tue, 01 Mar 2005 20:41:03 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D6DXU-0002jk-Ow for geb-bug-gnu-emacs@m.gmane.org; Tue, 01 Mar 2005 15:00:16 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D6DSm-0007XK-9G for bug-gnu-emacs@gnu.org; Tue, 01 Mar 2005 14:55:24 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D6DSj-0007VK-9p for bug-gnu-emacs@gnu.org; Tue, 01 Mar 2005 14:55:23 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D6DSi-0007Uo-81 for bug-gnu-emacs@gnu.org; Tue, 01 Mar 2005 14:55:21 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D6DEV-0005BV-08 for bug-gnu-emacs@gnu.org; Tue, 01 Mar 2005 14:40:39 -0500 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by fencepost.gnu.org with esmtp (Exim 4.34) id 1D6DEU-0004kg-ON for bug-emacs@gnu.org; Tue, 01 Mar 2005 14:40:38 -0500 Original-Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.34) id 1D6DE2-00059E-LF for bug-emacs@gnu.org; Tue, 01 Mar 2005 14:40:11 -0500 Original-Received: from [192.114.186.24] (helo=legolas.inter.net.il) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D6DE2-00058m-A3 for bug-emacs@gnu.org; Tue, 01 Mar 2005 14:40:10 -0500 Original-Received: from zaretski (tony02-25-115.inter.net.il [80.230.25.115]) by legolas.inter.net.il (MOS 3.5.6-GR) with ESMTP id DVW81115 (AUTH halo1); Tue, 1 Mar 2005 21:39:59 +0200 (IST) Original-To: "Sam Lauber" X-Mailer: emacs 22.0.50 (via feedmail 8 I) and Blat ver 2.4 In-reply-to: <20050301043930.3F54923CFA@ws5-3.us4.outblaze.com> (sam124@operamail.com) X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list 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 X-MailScanner-To: geb-bug-gnu-emacs@m.gmane.org Xref: main.gmane.org gmane.emacs.bugs:10840 X-Report-Spam: http://spam.gmane.org/gmane.emacs.bugs:10840 > From: "Sam Lauber" > Date: Tue, 01 Mar 2005 05:39:30 +0100 > Cc: > > On DJGPP, with Emacs 21.3, it seems that if I hit C-x C-c > before it gets to the splash screen, the exit handler code > is not called, and the display is not reset. If I do it > after, it works normally. This is (emacs-version): > > "GNU Emacs 21.3 (i686-pc-msdosdjgpp optimized for Pentium 4) > of 2005-02-28 on DELL" > > (Note that it has the same problem for base i386.) > > Samuel Lauber > > P.S. I don't know if this is DOS-specific, but it's > probably not. It _is_ specific to the DJGPP port, and it's actually a feature (that was there since Emacs 20). The feature is designed to not clear the screen if Emacs exits too quickly after the session begins. That's because the absolute majority of such quick exits are actually crashes during startup, and so it is very important to leave the screen contents intact, because they include vital clues to the reasons of the crash. If this feature somehow got in your way, please tell the details; perhaps we could change it a bit to not interfere with whatever you were doing.