From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Ken Manheimer" Newsgroups: gmane.emacs.devel Subject: Re: blink-cursor-end sometimes fails and disrupts pre-command-hook Date: Sat, 19 Aug 2006 12:59:54 -0400 Message-ID: <2cd46e7f0608190959x51bd9b6fha48aa041578d952b@mail.gmail.com> 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> <87ejvc8zwi.fsf@furball.mit.edu> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1156006813 8604 80.91.229.2 (19 Aug 2006 17:00:13 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 19 Aug 2006 17:00:13 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Aug 19 19:00:11 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 1GEUB8-0007kd-Q0 for ged-emacs-devel@m.gmane.org; Sat, 19 Aug 2006 19:00:11 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GEUB8-0006An-9m for ged-emacs-devel@m.gmane.org; Sat, 19 Aug 2006 13:00:10 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GEUAw-00069s-CZ for emacs-devel@gnu.org; Sat, 19 Aug 2006 12:59:58 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GEUAu-000690-9w for emacs-devel@gnu.org; Sat, 19 Aug 2006 12:59:57 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GEUAu-00068x-5E for emacs-devel@gnu.org; Sat, 19 Aug 2006 12:59:56 -0400 Original-Received: from [64.233.182.191] (helo=nf-out-0910.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GEUHs-0003Xc-77 for emacs-devel@gnu.org; Sat, 19 Aug 2006 13:07:08 -0400 Original-Received: by nf-out-0910.google.com with SMTP id q29so1837124nfc for ; Sat, 19 Aug 2006 09:59:54 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=de6SXoDx4zS5rDhwq1lgKW42TysWmHroXUdju38iof/kPg5/aDkBR3B2rUYkV3c7KwjDDnZFgiypft/cMdZ4V+77cRVNmnR2J304Jpm40rsjTFIJjg5o9bR2Q89kO6VJcNBVmNWG7KqjPTHovxPDS5fpAXA/K/PRlTB/i3KvPQk= Original-Received: by 10.48.220.15 with SMTP id s15mr5466089nfg; Sat, 19 Aug 2006 09:59:54 -0700 (PDT) Original-Received: by 10.78.144.19 with HTTP; Sat, 19 Aug 2006 09:59:54 -0700 (PDT) Original-To: "Chong Yidong" In-Reply-To: <87ejvc8zwi.fsf@furball.mit.edu> Content-Disposition: inline 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:58523 Archived-At: On 8/19/06, Chong Yidong wrote: > >> 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. i'll do that, soon (i've run out of time, today). (incidentally, did my rant about `backtrace' make sense to anyone, and if so, might it be feasible to fix it? my model is python's exception mechanism, which enables you to obtain the backtrace of an error at the point that the exception is caught, which is an extremely valuable introspection tool for debugging and executive operation...) -- ken ken.manheimer@gmail.com http://myriadicity.net