Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1690233 - ispell-word, ispell-region commands do not work
Summary: ispell-word, ispell-region commands do not work
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: emacs
Version: 30
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Jan Synacek
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2019-03-19 05:46 UTC by Satish Balay
Modified: 2019-04-04 21:52 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:

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):


How reproducible:


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-word(nil nil nil t)
  funcall-interactively(ispell-word nil nil nil t)
  call-interactively(ispell-word nil nil)

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")

Comment 2 Glenn Morris 2019-04-04 21:52:25 UTC

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