Subject: bug#2654 closed by Agustin Martin <[email-masked]> (Re: bug#2654: ispell-complete-word fails)

From: [email-masked] (Emacs bug Tracking System)
Date: Fri, 13 Mar 2009 16:30:07 +0000

This is an automatic notification regarding your bug report
which was filed against the emacs package:

#2654: ispell-complete-word fails

It has been closed by Agustin Martin <[email-masked]>.

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Agustin Martin <[email-masked]> by
replying to this email.

-- 
2654: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=2654
Emacs Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#2654: ispell-complete-word fails
From: Agustin Martin <[email-masked]>
To: [email-masked]
Date: Fri, 13 Mar 2009 17:21:13 +0100

On Fri, Mar 13, 2009 at 12:21:43AM -0400, Glenn Morris wrote:
> 
> emacs -Q
> 
> Type "foo", followed by M-x ispell-complete-word:
> 
> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
>   looking-at(nil)
>   ispell-get-word(nil "\\*")
>   ispell-complete-word(nil)
>   call-interactively(ispell-complete-word t nil)
>   execute-extended-command(nil)
>   call-interactively(execute-extended-command nil nil)
> 
> This happens because in ispell-get-word
> 
> (if (not (looking-at ispell-casechars))
> 
> has ispell-casechars = nil. This is because (ispell-get-casechars)
> returns nil; and this is because ispell-dictionary-alist is now nil by
> default.

Thanks for noticing and debugging,

Committed a fix that initializes spellchecker parameters also from
(ispell-get-word)

-- 
Agustin

Subject: ispell-complete-word fails
From: Glenn Morris <[email-masked]>
To: [email-masked]
Date: Fri, 13 Mar 2009 00:21:43 -0400

emacs -Q

Type "foo", followed by M-x ispell-complete-word:

Debugger entered--Lisp error: (wrong-type-argument stringp nil)
  looking-at(nil)
  ispell-get-word(nil "\\*")
  ispell-complete-word(nil)
  call-interactively(ispell-complete-word t nil)
  execute-extended-command(nil)
  call-interactively(execute-extended-command nil nil)

This happens because in ispell-get-word

(if (not (looking-at ispell-casechars))

has ispell-casechars = nil. This is because (ispell-get-casechars)
returns nil; and this is because ispell-dictionary-alist is now nil by
default.