Flyspell using hunspell cannot detect apostrophe in words

[xuan-w]

Description :octocat:

flyspell using hunspell cannot detect apostrophe in words

Reproduction guide :beetle:

• Start Emacs (must be Linux, Windows doesn't have this problem)
• configure ispell-program-name to be hunspell (aspell and ispell doesn't have this problem)
• use flyspell in any buffer (no matter text mode, markdown mode or org mode)

Observed behaviour: :eyes: :broken_heart: Words like "isn't" "didn't" "I've" were marked as wrong words because they were separated by apostrophe.

Expected behaviour: :heart: :smile: Emacs should send "isn't" as a whole to hunspell, not "isn" and "t".

System Info :computer:

• OS: gnu/linux
• Emacs: 28.1
• Spacemacs: 0.999.0
• Spacemacs branch: develop (rev. dc85616df)
• Graphic display: t
• Distribution: spacemacs
• Editing style: vim
• Completion: helm
• Layers:

  (emacs-lisp helm multiple-cursors treemacs git org python markdown html javascript auto-completion deft spell-checking latex bibtex syntax-checking csv
          (chinese :variables pyim-default-scheme 'wubi pyim-dicts
                   '((:name "zhengma" :file "~/.local/share/zhengma.pyim")))
          shell)

• System configuration features: ACL CAIRO DBUS FREETYPE GIF GLIB GMP GNUTLS GPM GSETTINGS HARFBUZZ JPEG JSON LCMS2 LIBOTF LIBSELINUX LIBSYSTEMD LIBXML2 M17N_FLT MODULES NATIVE_COMP NOTIFY INOTIFY PDUMPER PNG RSVG SECCOMP SOUND THREADS TIFF TOOLKIT_SCROLL_BARS X11 XDBE XIM XPM GTK3 ZLIB

Backtrace :paw_prints:

<<BACKTRACE IF RELEVANT>>

[xuan-w]

After some more tests, I think it might not be shell layer caused this. So I changed the title and content.

It seems that even vanilla Emacs has this problem with hunspell. So I think it might be related to flyspell/ispell itself.

So actually this is not a spacemacs bug, but something spacemacs can do better than vanilla Emacs?

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!