From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chong Yidong Newsgroups: gmane.emacs.devel Subject: Re: blink-cursor-end sometimes fails and disrupts pre-command-hook Date: Sat, 19 Aug 2006 12:15:57 -0400 Message-ID: <87ejvc8zwi.fsf@furball.mit.edu> References: <2cd46e7f0608181530l1c1a18f7k1923f610edf73f59@mail.gmail.com> <87veoo95zy.fsf@furball.mit.edu> <2cd46e7f0608190731j6247e8bbr7f7f8d1ecb6ac3ce@mail.gmail.com> <87r6zc9475.fsf@furball.mit.edu> <2cd46e7f0608190805x70bd8715n6f1b552d57a80a5c@mail.gmail.com> <87irko92nc.fsf@furball.mit.edu> <2cd46e7f0608190858g5865c343w455700d22dbbc91a@mail.gmail.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1156004191 32074 80.91.229.2 (19 Aug 2006 16:16:31 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 19 Aug 2006 16:16:31 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Aug 19 18:16:29 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1GETUh-0000nt-LF for ged-emacs-devel@m.gmane.org; Sat, 19 Aug 2006 18:16:20 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GETUg-0004Hu-Lq for ged-emacs-devel@m.gmane.org; Sat, 19 Aug 2006 12:16:18 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GETUT-0004Fn-2b for emacs-devel@gnu.org; Sat, 19 Aug 2006 12:16:05 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GETUR-0004DD-IH for emacs-devel@gnu.org; Sat, 19 Aug 2006 12:16:03 -0400 Original-Received: from [18.72.1.2] (helo=south-station-annex.mit.edu) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1GETbP-0007ft-LT for emacs-devel@gnu.org; Sat, 19 Aug 2006 12:23:15 -0400 Original-Received: from central-city-carrier-station.mit.edu (CENTRAL-CITY-CARRIER-STATION.MIT.EDU [18.7.7.72]) by south-station-annex.mit.edu (8.13.6/8.9.2) with ESMTP id k7JGG2P3001600; Sat, 19 Aug 2006 12:16:02 -0400 (EDT) Original-Received: from outgoing-legacy.mit.edu (OUTGOING-LEGACY.MIT.EDU [18.7.22.104]) by central-city-carrier-station.mit.edu (8.13.6/8.9.2) with ESMTP id k7JGFxX6001010; Sat, 19 Aug 2006 12:16:02 -0400 (EDT) Original-Received: from furball.mit.edu (SYDNEYPACIFIC-THREE-NINETY-NINE.MIT.EDU [18.95.6.144]) ) by outgoing-legacy.mit.edu (8.13.6/8.12.4) with ESMTP id k7JGFva1013074; Sat, 19 Aug 2006 12:15:57 -0400 (EDT) Original-Received: from cyd by furball.mit.edu with local (Exim 3.36 #1 (Debian)) id 1GETUL-00015O-00; Sat, 19 Aug 2006 12:15:57 -0400 Original-To: "Ken Manheimer" In-Reply-To: <2cd46e7f0608190858g5865c343w455700d22dbbc91a@mail.gmail.com> (Ken Manheimer's message of "Sat, 19 Aug 2006 11:58:04 -0400") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) X-Spam-Score: 1.217 X-Scanned-By: MIMEDefang 2.42 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:58521 Archived-At: >> The question is, why did this surface only with the latest Emacs >> update? > > actually, it isn't necessarily the latest emacs update, though it > probably is a one within the last several weeks. i started noticing > the problem a week or so ago, but didn't have time to investigate > until yesterday. i may not have done an update for a week or more > until before i first started seeing the problem. Could you try to track down why the error happens? One way I suggest doing this is to go through the various `error' calls inside run-with-timer, and make them additionally print a message or save something to a variable. If we can find out which `error' is being triggered, we can figure out whether it's a problem with Emacs, or with your customizations.