all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: emacs-devel@gnu.org
Subject: Re: Timer out of nowhere
Date: Wed, 13 Feb 2013 20:43:29 +0100	[thread overview]
Message-ID: <87boboatjy.fsf@web.de> (raw)
In-Reply-To: <87r4kkaxcp.fsf@fimbulvetr.bsc.es> ("Lluís"'s message of "Wed, 13 Feb 2013 19:21:26 +0100")

Lluís <xscript@gmx.net> writes:

> Every once in a while, I get this error:
>
> Debugger entered--Lisp error: (error "Selecting deleted buffer")
>   adict-guess-dictionary-maybe(#<killed buffer>)
>   apply(adict-guess-dictionary-maybe #<killed buffer>)
>   byte-code("r\301\b\302H\b\303H\"\210)\301\207" [timer apply 5 6] 4)
>   timer-event-handler([t 0 2 0 t adict-guess-dictionary-maybe
> (#<killed buffer>) idle 0])
>
> This is from [1].

Yes, I see the same since I've upgraded my emacs.

> The strange part is that I just killed every possible buffer (in case
> it was a local timer on any of them), and `timer-list' shows
> absolutely no entry with `adict-guess-dictionary-maybe'.

It's in `timer-idle-list'.

> Any ideas on how to track this problem?

It's a bug in auto-dictionary.  I guess that in prior Emacs version, the
problem was also there, but just no message was raised.

Anyway, once `auto-dictionary-mode' calls `run-with-idle-timer', the
timer stays in `timer-idle-list' even after its buffer has been killed.

I think this is not hard to fix.  The timer runs
`adict-guess-dictionary-maybe'.  This function should just check if the
BUFFER argument is `buffer-live-p'.  If it is not, it just has to cancel
`adict-timer'.


Regards,

Michael.



  parent reply	other threads:[~2013-02-13 19:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-13 18:21 Timer out of nowhere Lluís
2013-02-13 18:34 ` Michael Markert
2013-02-13 19:43 ` Michael Heerdegen [this message]
2013-02-13 20:42   ` Lluís
2013-02-13 20:42   ` Stefan Monnier
2013-02-13 19:53 ` Stefan Monnier

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

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

  git send-email \
    --in-reply-to=87boboatjy.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.