From: Eli Zaretskii <eliz@gnu.org>
To: sds@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: git tip: Error in winner-save-old-configurations (flyspell-post-command-hook): (wrong-type-argument stringp nil) [73 times]
Date: Wed, 07 Sep 2022 18:35:08 +0300 [thread overview]
Message-ID: <83r10ngpub.fsf@gnu.org> (raw)
In-Reply-To: <lzr10ntdcq.fsf@3c22fb11fdab.ant.amazon.com> (message from Sam Steingold on Wed, 07 Sep 2022 11:26:29 -0400)
> From: Sam Steingold <sds@gnu.org>
> Date: Wed, 07 Sep 2022 11:26:29 -0400
>
> > * Eli Zaretskii <ryvm@tah.bet> [2022-09-07 05:27:15 +0300]:
> >
> >> From: Sam Steingold <sds@gnu.org>
> >> Date: Tue, 06 Sep 2022 15:47:23 -0400
> >>
> >> Hi,
> >> With the fresh Emacs from yesterday, I get
> >>
> >> Error in winner-save-old-configurations (flyspell-post-command-hook): (wrong-type-argument stringp nil)
> >>
> >> in the Echo Area and *Messages* on every move in an Org-mode buffer.
> >>
> >> I don't know how to debug it (I tried stepping through
> >> `flyspell-post-command-hook' and got nothing), so I wonder if someone
> >> sees anything like that.
> >>
> >> Thank you.
> >>
> >> PS. The trivial sequence of
> >>
> >> emacs -Q
> >> C-x b foo RET
> >> M-x org-mode RET
> >> M-x winner-mode RET
> >> M-x flyspell-mode RET
> >> foo bar baz
> >>
> >> does not, alas, produce the described behavior...
> >
> > So what _is_ the recipe to reproduce it?
>
> I cannot reproduce it without my huge .emacs
Then I guess you will have to debug this on your system.
One way of doing that is to attach a debugger and put a breakpoint in
wrong_type_argument. When it breaks, collect both C and Lisp
backtraces, and post them.
next prev parent reply other threads:[~2022-09-07 15:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 19:47 git tip: Error in winner-save-old-configurations (flyspell-post-command-hook): (wrong-type-argument stringp nil) [73 times] Sam Steingold
2022-09-07 2:27 ` Eli Zaretskii
2022-09-07 15:26 ` Sam Steingold
2022-09-07 15:35 ` Eli Zaretskii [this message]
2022-09-07 16:45 ` Stefan Monnier
2022-09-07 18:17 ` Jose A Ortega Ruiz
2022-09-07 17:16 ` Jose A Ortega Ruiz
2022-09-07 17:57 ` Juri Linkov
2022-09-07 18:00 ` Stefan Monnier
2022-09-07 18:45 ` Sam Steingold
2022-09-07 19:43 ` Jose A Ortega Ruiz
2022-09-07 22:57 ` Jose A Ortega Ruiz
2022-09-07 23:51 ` Jose A Ortega Ruiz
2022-09-08 20:17 ` 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
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=83r10ngpub.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=sds@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).