From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Lars Hansen" Newsgroups: gmane.emacs.bugs Subject: A list of bugs Date: Fri, 26 Jul 2002 23:34:52 +0200 Sender: bug-gnu-emacs-admin@gnu.org Message-ID: <001b01c234ec$47632000$72dd52c3@x874761> NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Trace: main.gmane.org 1027723935 19233 127.0.0.1 (26 Jul 2002 22:52:15 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Fri, 26 Jul 2002 22:52:15 +0000 (UTC) Return-path: Original-Received: from fencepost.gnu.org ([199.232.76.164]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 17YDwU-000506-00 for ; Sat, 27 Jul 2002 00:52:14 +0200 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.35 #1 (Debian)) id 17YDwo-00080U-00; Fri, 26 Jul 2002 18:52:34 -0400 Original-Received: from delysid.gnu.org ([158.121.106.20]) by fencepost.gnu.org with esmtp (Exim 3.35 #1 (Debian)) id 17YDwG-0007sd-00; Fri, 26 Jul 2002 18:52:00 -0400 Original-Received: from richardson.uni2.net ([130.227.52.104]) by delysid.gnu.org with esmtp (Exim 3.34 #2) id 17YCjH-0002z5-00 for ; Fri, 26 Jul 2002 17:34:32 -0400 Original-Received: from x874761 (p419-114.ppp.get2net.dk [195.82.221.114]) by richardson.uni2.net (8.11.6/8.11.6) with SMTP id g6QLYBh32204 for ; Fri, 26 Jul 2002 23:34:11 +0200 Original-To: X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Errors-To: bug-gnu-emacs-admin@gnu.org X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Bug reports for GNU Emacs, the Swiss army knife of text editors List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.bugs:2930 X-Report-Spam: http://spam.gmane.org/gmane.emacs.bugs:2930 Hi I have collected a few bugs, described below. expand-file-name crashes Emacs ------------------------------ Calling expand-file-name with default-directory set to nil, such as in (let ((default-directory nil)) (expand-file-name "foo")) makes Emacs crash without a word. I experience the problem with Emacs 21.2 and 20.7 under MS Windows. Microsoft Windows cannot shut down Emacs ---------------------------------------- Start Emacs (21.2 or 20.7) under MS Windows and try to close MS Windows. Then you get an error message saying that MS Windows cannot shut down Emacs. I suspect that Emacs does not handle the WM_QUERYENDSESSION = (0x0011) sent to applications by MS Windows to make them do things like ask the = user if unsaved files should be saved. I have not checked whether my = suspicion holds. Font lock in multi line text strings ------------------------------------ Font lock in emacs-lisp-mode gets very confused when a multi line text = string (such as a doc string) have a line starting with 'with' or '(' (no = quotes). Redraw of MS Windows title bar ------------------------------ When running under MS Windows, the title bar of Emacs frames often = flicker. I seems they are redrawn unnecessarily. This problem is introduced with = Emacs 21, it is not there with Emacs 20. Scroll/timer bug ---------------- I have reported this bug before -- however at that time I suspected the = error to be MS Windows specific. Now I have seen it on a Linux system as well. When I scroll a window by holding down the the down-arrow button, the scrolling motion have anoying jumps now and then. What happes is, obviously, that the window gets recentered. I suspect this problem has to do with timers. It can be reproduce with Emacs 20 or 21 under MS Windows using a .emacs = file with the following lines: (setq display-time-interval 1) (display-time-mode t) (setq scroll-margin 1) (setq scroll-conservatively 1000) Start Emacs and visit any relatively large file. Hold the down-arrow = button down. The window will the scroll upwards, and most of the time the point stays, as i should, one row from the bottom of the window. But = occasionally it will go down to the bottom of the screen. If you have a fast keyboard repeat rate you will see that the problem comes when the clock on the mode line is updated. Not necessarily each second, but sometimes a few seconds in a row. It probably depends on when keyboard events occur related to the timer events. You can also reproduce the problem without using automatic keyboard repeating, just by pressing the down-arrow = about say 50-100 times, waiting for the correct timing to occur. If you then = stop, when the problem comes, point stays at the bottom of the window. I have the problem on a Suse Linux system as well -- here the problem = comes from something in the site file, but I don't know exactly what. Lars Hansen e-mail: larsh@math.ku.dk