GNU bug report logs - #15721
24.3; Error in post-command-hook (flyspell-post-command-hook): (wrong-type-argument integer-or-marker-p nil)

Previous Next

Full log

Message #17 received at 15721-done <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefan <at> marxist.se>
To: Leo Liu <sdl.web <at> gmail.com>
Cc: 15721-done <at> debbugs.gnu.org
Subject: Re: bug#15721: 24.3; Error in post-command-hook
 (flyspell-post-command-hook): (wrong-type-argument integer-or-marker-p
 nil)
Date: Wed, 15 Jan 2020 06:35:35 +0100

Stefan Kangas <stefan <at> marxist.se> writes:

> tags 15721 + moreinfo
> quit
>
> Leo Liu <sdl.web <at> gmail.com> writes:
>
>> I got this from time to time:
>>
>>         Error in post-command-hook (flyspell-post-command-hook):
>>         (wrong-type-argument integer-or-marker-p nil)
>>
>> But I don't know how to reproduce it reliably. So I put in this form
>>
>>       (unless (numberp flyspell-pre-point)
>>                 (message "DEBUG-flyspell-pre-point: %S" flyspell-pre-point))
>>
>> before (goto-char flyspell-pre-point) in flyspell-post-command-hook.
>>
>> This is what is in *Messages* when the error happened:
>> DEBUG-flyspell-pre-point: nil
>>
>> So it seems flyspell-post-command-hook needs to check current buffer is
>> flyspell-pre-buffer. But I am not totally sure.
>
> Do you have a recipe for reproducing this, starting from "emacs -Q"?

More information was requested, but none was given within 15 weeks, so
I'm closing this bug.  If this is still an issue, please reply to this
email (use "Reply to all" in your email client) and we can reopen the
bug report.

Best regards,
Stefan Kangas

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.