跳至主要内容

Emacs 26.2 windows Hunspell setup

 Hunspell failed with default setup

With my shining new emacs26.2 setup, I am happy until trying to `M-$’ on a word.

I got following error message, it used to be work by just set ispell program to hunspell.

Starting new Ispell process hunspell with default dictionary...
split-string: Wrong type argument: stringp, nil

After some check in my customization setting. nothing found.

install a copy of hunspell dictionary

At first I think it was caused by no hunspell dictionary. I downloaded enUS and enCA hunspell dictionary from wordlist.sf.net project.

After put the .aff and .dic files into C:directory

I’ve also made a symbolic link from enUS ones by running the `mklink’ tool:

mklink default.aff en_US.aff
mklink default.dic en_US.dic

Err… hunspell does not work, still.

Time to read code

Dig into ispell.el I suprisingly find there’re lots of hunspell specific logic. Originally I was thinking hunspell support involves no elisp work.

Acturally ispell did many work to determind dictionary list for hunspell. And it seemed that my recently installed, shining new, chocolatey managed hunspell.portable is causing problem.

with azwinport, the hunspell command will determind installed dictionary correctly as shown bellow:

# bin\hunspell.exe -D
SEARCH PATH:
.;;C:\Hunspell\;c:\opt\nobody\.openoffice.org\3\user\wordbook;C:\Users\nobody\Downloads\hunspell-1.3.2-3-w32-bin\bin\..\share\hunspell;C:\Program files\OpenOffice.org 2.4\share\dict\ooo\;C:\Program files\OpenOffice.org 2.3\share\dict\ooo\;C:\Program files\OpenOffice.org 2.2\share\dict\ooo\;C:\Program files\OpenOffice.org 2.1\share\dict\ooo\;C:\Program files\OpenOffice.org 2.0\share\dict\ooo\
AVAILABLE DICTIONARIES (path is not mandatory for -d option):
C:\Hunspell\default
C:\Hunspell\en_CA
C:\Hunspell\en_US
C:\Users\nobody\Downloads\hunspell-1.3.2-3-w32-bin\bin\..\share\hunspell\default
C:\Users\nobody\Downloads\hunspell-1.3.2-3-w32-bin\bin\..\share\hunspell\en_GB
C:\Users\nobody\Downloads\hunspell-1.3.2-3-w32-bin\bin\..\share\hunspell\en_US
LOADED DICTIONARY:
C:\Hunspell\\default.aff
C:\Hunspell\\default.dic
Hunspell 1.3.2

With chocolatey managed hunspell, nothing but the default loaded one is reported.

# hunspell.exe -D -a .viminfo
SEARCH PATH:
.;;C:\Hunspell\;%USERPROFILE%\Application Data\OpenOffice.org 2\user\wordbook;C:\Program files\OpenOffice.org 2.4\share\dict\ooo\;C:\Program files\OpenOffice.org 2.3\share\dict\ooo\;C:\Program files\OpenOffice.org 2.2\share\dict\ooo\;C:\Program files\OpenOffice.org 2.1\share\dict\ooo\;C:\Program files\OpenOffice.org 2.0\share\dict\ooo\
AVAILABLE DICTIONARIES (path is not mandatory for -d option):
LOADED DICTIONARY:
C:\Hunspell\\default.aff
C:\Hunspell\\default.dic
@(#) International Ispell Version 3.2.06 (but really Hunspell 1.7.0)

fix it by provide the hunspell dict paths alist

finally I managed to run the hunspell spellchecker by add following lisp code into my .emacs.

(setq-default ispell-hunspell-dict-paths-alist
          '(
        ("default" "C:\\Hunspell\\default.aff")
        ("en_US" "C:\\Hunspell\\en_US.aff")
        ("en_CA" "C:\\Hunspell\\en_CA.aff")
        ))

评论

此博客中的热门博文

Use MobaDiff with git difftool

Recently there's an activity in IT that forces the deletion of all unauthorized softwares from all work machines. Unfortunately, kdiff3 is one in the list. As it is generally okay to use vimdiff as an alternative for kdiff3, A gui tool is better suited for desktop workflows. Known that MobaXterm is shipping a gui diff tool named MobaDiff. But it only appears in the windows right click context menu. Find the real application name takes me some time to search in the windows registry. "MobaRTE.exe", which is the one invoked by HKCR\*\shell\MobaDiff. And it was invoked with "-contextdiff" switch to show MobaDiff UI, while when the switch is "-contextedit" it shows MobaTextEditor. Too bad that the "-contextdiff" switch do not support pre-image post-image as other diff tool did, which effectively made it unable to be used as a command line diff utility. Also MobaTech did not mention anything in their document of this Mob...

XEmacs 21.5 beta 35 "kohlrabi" has been released.

If you are an old XEmacs user, you may feel happy to see this from https://www.xemacs.org/.    After ten years, XEmacs released a new version 21.5. So there's still many people cares about XEmacs. The XEmacs' source repo have been moved from altassian Bitbucket to https://heptapod.net/. As Bitbucket have been dropped Mercurial support many years ago.