Bug 1690233 - ispell-word, ispell-region commands do not work
Summary: ispell-word, ispell-region commands do not work
Keywords:
Status: CLOSED DUPLICATE of bug 1696992
Alias: None
Product: Fedora
Classification: Fedora
Component: emacs
Version: 30
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jan Synacek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-19 05:46 UTC by Satish Balay
Modified: 2019-05-03 22:44 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-05-03 22:44:37 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Satish Balay 2019-03-19 05:46:49 UTC
Description of problem:

ispell-word or ispell-region does not work

Version-Release number of selected component (if applicable):

emacs-26.1-8.fc30.x86_64

How reproducible:

always

Steps to Reproduce:
1. emacs -q file
2. type in a word
3. M-x ispell-word

Actual results:

split-string: Wrong type argument: stringp, nil


Expected results:

correct ispell-word behavior

Additional info:

This machine is upgraded from F29 to F30 using 'dnf system-upgrade'. This worked fine before on F29

$ cat .emacs
(setq debug-on-error t)

With the above - I get:

Debugger entered--Lisp error: (wrong-type-argument stringp nil)
  string-match("," nil 0)
  split-string(nil "," t)
  ispell-parse-hunspell-affix-file(nil)
  ispell-find-hunspell-dictionaries()
  ispell-set-spellchecker-params()
  ispell-word(nil nil nil t)
  funcall-interactively(ispell-word nil nil nil t)
  call-interactively(ispell-word nil nil)
  command-execute(ispell-word)

Comment 1 Satish Balay 2019-03-19 22:11:48 UTC
The issue appears to be related to hunspell [related code in emacs].

I'm able to work around it by adding the following to my .emacs


 (defcustom ispell-program-name
   (executable-find "aspell")
   "ispell")

Comment 2 Glenn Morris 2019-04-04 21:52:25 UTC
See https://debbugs.gnu.org/33606

Comment 3 Jeremy Linton 2019-05-03 22:37:27 UTC
I just hit this too on aarch64.

Summary, its a bug in emacs 26.1, and is fixed in 26.2. There is a 26.2 koji build here:

https://koji.fedoraproject.org/koji/buildinfo?buildID=1260502

Which I applied to my machine and everything is working again.

Comment 4 Jeremy Linton 2019-05-03 22:41:17 UTC
Its also in update-testing https://bodhi.fedoraproject.org/updates/FEDORA-2019-b412767621.

Thanks!

Comment 5 Jeremy Linton 2019-05-03 22:44:37 UTC
I'm going to dupe this against 1696992 despite this one being older, because the fedora update is being made against that one.

*** This bug has been marked as a duplicate of bug 1696992 ***


Note You need to log in before you can comment on or make changes to this bug.