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
Reported by: Leo Liu <sdl.web <at> gmail.com>
Date: Sat, 26 Oct 2013 07:14:02 UTC
Severity: normal
Tags: moreinfo
Found in version 24.3
Done: Stefan Kangas <stefan <at> marxist.se>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Wed, 15 Jan 2020 06:35:35 +0100
with message-id <8736chffiw.fsf <at> marxist.se>
and subject line Re: bug#15721: 24.3; Error in post-command-hook (flyspell-post-command-hook): (wrong-type-argument integer-or-marker-p nil)
has caused the debbugs.gnu.org bug report #15721,
regarding 24.3; Error in post-command-hook (flyspell-post-command-hook): (wrong-type-argument integer-or-marker-p nil)
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
15721: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15721
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
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.
Leo
[Message part 3 (message/rfc822, inline)]
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
This bug report was last modified 5 years and 130 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.