From: "Drew Adams" <drew.adams@oracle.com>
To: "'Tom Dye'" <tsd@tsdye.com>, <help-gnu-emacs@gnu.org>
Subject: RE: ispell-get-line: Wrong type argument: stringp, ni
Date: Sat, 26 Dec 2009 09:57:24 -0800 [thread overview]
Message-ID: <80ECA04CE05C4CFD86F8159D5A11DF4C@us.oracle.com> (raw)
In-Reply-To: <2009122606551416807-tsd@tsdyecom>
> This problem "went away" without any apparent intervention from me.
> Looking at the cocoAspell web site again, perhaps this was
> the culprit:
>
> > In some rare case the first time you spell check a
> > document, cocoAspell may fail to come up with a list
> > of suggestions. It happens because the spell server
> > needs some time to load the dictionary and initialize
> > itself. The client application simply times out on the
> > spell checking request and behaves as there were no
> > suggestions. This may not happen at all if you have a
> > fast machine.
>
> Apologies for the noise level.
My guess is that the text you quoted is irrelevant here.
A wrong-type arg error is a product bug, even if it is often only a minor
problem. Please try to reproduce it, starting with `emacs -Q', and then report
it using `M-x report-emacs-bug'.
Often, such a bug occurs because of a lack of proper initialization of something
(typically a variable that is supposed to be a string is nil by default).
The same code that raises the error often performs initialization, so after the
error has been raised once, initialization has occurred and the error is never
raised again. That can explain why it "went away without any apparent
intervention from you." There is nevertheless a bug.
next prev parent reply other threads:[~2009-12-26 17:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-26 4:23 ispell-get-line: Wrong type argument: stringp, ni Tom Dye
2009-12-26 16:55 ` Tom Dye
2009-12-26 17:57 ` Drew Adams [this message]
2009-12-26 19:10 ` Thomas S. Dye
2009-12-26 19:21 ` Drew Adams
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=80ECA04CE05C4CFD86F8159D5A11DF4C@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=tsd@tsdye.com \
/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.