unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Jeff D. Hamann" <jeff.hamann@forestinformatics.com>
Subject: Re: ispell gives "Wrong type argument: stringp, nil"
Date: Thu, 29 Dec 2005 10:36:52 -0800	[thread overview]
Message-ID: <nZmdnecY7chZsSneRVn-oQ@scnresearch.com> (raw)
In-Reply-To: mailman.20694.1135794740.20277.help-gnu-emacs@gnu.org

So when I added (and I rarely mess with my .emacs file) the following line:

(add-hook 'tex-mode-hook (function (lambda () (setq ispell-parser 'tex))))
(setq ispell-dictionary "C:/ispell/dic/american.hash")
(add-hook 'text-mode-hook (lambda () (flyspell-mode 1)))

;; set something...
(assoc ispell-dictionary ispell-dictionary-alist)


I still got the same results...

Debugger entered--Lisp error: (wrong-type-argument stringp nil)
  looking-at(nil)
  ispell-get-word(nil)
  ispell-word(nil nil nil)
* call-interactively(ispell-word)

ugh..... am I doing something totally lame-o or is this a bug?

Jeff.


"Kevin Rodgers" <> wrote in message 
news:mailman.20694.1135794740.20277.help-gnu-emacs@gnu.org...
> Peter Dyballa wrote:
> > Am 27.12.2005 um 07:55 schrieb Jeff D. Hamann:
> >
> >> With ispell (3.2.02 from
> >> http://www.fsci.fuk.kindai.ac.jp/aftp/pub/ptex/utils/ ) yields,
> >>
> >> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
> >>   looking-at(nil)
> >>   ispell-get-word(nil)
> >>   ispell-word(nil nil nil)
> >>   call-interactively(ispell-word)
> >
> >
> > Here obviously the function looking-at() receives something bad:
> >
> >     looking-at is a built-in function in `C source code'.
> >     (looking-at regexp)
> >
> >     Return t if text after point matches regular expression regexp.
> >     This function modifies the match data that `match-beginning',
> >     `match-end' and `match-data' access; save and restore the match
> >     data if you want to preserve them.
> >
> > Could be you did not set up ispell-dictionary, ispell-program-name,
> > ispell-extra-args, or ispell-local-dictionary-alist in case
> > ispell-dictionary-alist is not sufficient?
>
> That seems likely: ispell-get-word calls looking-at several times, with
> the result of calling ispell-get-casechars and ispell-get-otherchars as
> the REGEXP.  Those functions in turn depend on ispell-dictionary having
> been set:  (assoc ispell-dictionary ispell-dictionary-alist)
>
> -- 
> Kevin
>
>
> 

  parent reply	other threads:[~2005-12-29 18:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-13  6:42 ispell gives "Wrong type argument: stringp, nil" Jeff D. Hamann
2005-10-13  8:50 ` Peter Dyballa
     [not found] ` <mailman.11175.1129195674.20277.help-gnu-emacs@gnu.org>
2005-10-13 16:42   ` Jeff D. Hamann
2005-10-13 23:11     ` Peter Dyballa
2005-12-27  6:55   ` Jeff D. Hamann
2005-12-27 12:26     ` Peter Dyballa
2005-12-28 18:30       ` Kevin Rodgers
     [not found]       ` <mailman.20694.1135794740.20277.help-gnu-emacs@gnu.org>
2005-12-29 18:36         ` Jeff D. Hamann [this message]
2005-12-29 23:03           ` Peter Dyballa
2005-12-30 22:16           ` Kevin Rodgers
  -- strict thread matches above, loose matches on Subject: below --
2005-12-27  6:49 Jeff D. Hamann

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=nZmdnecY7chZsSneRVn-oQ@scnresearch.com \
    --to=jeff.hamann@forestinformatics.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.
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).