unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ken Manheimer" <ken.manheimer@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: blink-cursor-end sometimes fails and disrupts pre-command-hook
Date: Sat, 19 Aug 2006 12:59:54 -0400	[thread overview]
Message-ID: <2cd46e7f0608190959x51bd9b6fha48aa041578d952b@mail.gmail.com> (raw)
In-Reply-To: <87ejvc8zwi.fsf@furball.mit.edu>

On 8/19/06, Chong Yidong <cyd@stupidchicken.com> 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

  reply	other threads:[~2006-08-19 16:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-18 22:30 blink-cursor-end sometimes fails and disrupts pre-command-hook Ken Manheimer
2006-08-19 15:07 ` Chong Yidong
     [not found] ` <87veoo95zy.fsf@furball.mit.edu>
     [not found]   ` <2cd46e7f0608190731j6247e8bbr7f7f8d1ecb6ac3ce@mail.gmail.com>
     [not found]     ` <87r6zc9475.fsf@furball.mit.edu>
     [not found]       ` <2cd46e7f0608190805x70bd8715n6f1b552d57a80a5c@mail.gmail.com>
2006-08-19 15:16         ` Chong Yidong
2006-08-19 15:58           ` Ken Manheimer
2006-08-19 16:15             ` Chong Yidong
2006-08-19 16:59               ` Ken Manheimer [this message]
2006-08-21 15:36                 ` Stuart D. Herring
2006-08-20 12:05 ` Richard Stallman
2006-08-20 22:49   ` Ken Manheimer
2006-08-21  7:15     ` David Kastrup
2006-08-21 11:13     ` Richard Stallman
2006-08-21 15:31       ` Ken Manheimer
2006-08-21 17:23         ` Stuart D. Herring
2006-08-22 21:12           ` Ken Manheimer
2006-08-23 14:45             ` Richard Stallman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2cd46e7f0608190959x51bd9b6fha48aa041578d952b@mail.gmail.com \
    --to=ken.manheimer@gmail.com \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).