flyspell has a mode for prog-mode, flyspell-prog-mode. It'd be great flycheck-aspell came with a flymake-diagnostic-function for prog-mode.

A concrete example.

Steps to reproduce

With (flymake-aspell-setup), write the following code:

package main

// I can't spell hipopopopoatmus.
func main() {

}

Expected

"hipopopopoatmus" should be the only flymake diagnostic.

Actual

"hipopopopoatmus" and "func" are displayed as flymake diagnostics.

This is a false positive, because "func" is a valid Go keyword.

Workaround

(add-hook 'prog-mode-hook 'flyspell-prog-mode)

Aspell can be called with a language flag (aspell --lang=de`) to tell it what language to look for.
It would be great if I could somehow tell flycheck-aspell which language to use in a given buffer.

I think aspell defaults to the current locale setting, but that might not be the right thing for each buffer.

On Ubuntu 20.04, I've aspell installed:

$ aspell --version
@(#) International Ispell Version 3.1.20 (but really Aspell 0.60.8)

And I installed flycheck-aspell:

(use-package flycheck-aspell)

But how to activate it and let it fix the misspelled words automatically?

Regards,
HY

Stock Emacs already has a package called "flyspell-mode". It is rather old and sometimes behaves weirdly, but I think it would still be nice to have a small introduction at the README, how flycheck-aspell is better.

Could that be added?

Would you be opposed to submitting this package (or packages?) to melpa?

I'm willing to submit the package on your behalf.

When checking a line with a curly quote (for example U+2019 ’ or U+201D ”) the call to string-match in flycheck-aspell--handle-and doesn't match the curly quotes because it checks for the word character class rather than the word syntax.

Changing wordchar to (syntax word) in the call to rx fixes this issue.

This issue also occurs in flymake-aspell--handle-and, flycheck-aspell--handle-hash, and flymake-aspell--handle-hash, and has the same fix.

Additionally, I think it might be worth opening a bug upstream since the elisp manual and the docstring of rx don't make the difference between (rx word) and (rx (syntax word)) clear at all.

When installing the package with quelpa, I meet the error "Package lacks a file header". It seems that a copyright line is expected.

For a reference, https://www.gnu.org/software/emacs/manual/html_node/elisp/Library-Headers.html

I'm trying to get the flymake-aspell backend going on emacs 27.1, but I am unable to get it working and I am not sure what is going wrong. Having installed it and using the following blurb in my config:

(use-package flymake-aspell
  :hook
  (text-mode-hook . flymake-aspell-setup)
  (prog-mode-hook . flymake-aspell-setup))

(use-package flymake
  :hook
  (prog-mode-hook . flymake-mode)
  (text-mode-hook . flymake-mode))

I am getting the following error-message in the flymake log buffer in files that should be supported such as tex files.

Warning [flymake init.el]: Disabling backend flymake-aspell--check because (wrong-type-argument stringp nil)

If I only have the first config block flymake doesn't activate and I see no error message at all, so at a loss what goes wrong. Do you have any idea what is going wrong here?

At the moment lazy loading flymake-aspell fails for me when adding flymake-aspell-setup to the text-mode-hook when byte-compiling; could you add the autoloading cookie

;;;###autoload

to the function to fix this?

The readme file states that the minimum required version of aspell is 0.68.8 which doesn't exist and should read 0.60.8 instead.

Thanks for putting together this nice interface to allow spell checking with flycheck!

I edit a bunch of markdown documents, and hooked in your existing checker via:

   (add-to-list 'flycheck-checkers 'markdown-aspell-dynamic)

It mostly works fine, but I noticed that sometimes it gets the wrong positions for misspelt words.

Now I'm on ubuntu 20.04, it uses a version of aspell that has built-in support for markdown, so I thought using that might fix the problem....

 (flycheck-aspell-define-checker "new-markdown" "Markdown using aspell markdown filter"
   ("--add-filter" "url" "--add-filter" "markdown") (markdown-mode))
 (add-to-list 'flycheck-checkers 'new-markdown-aspell-dynamic)

However, when I use it, I get an error message like:

Error from syntax checker new-markdown-aspell-dynamic: Args out of range: "    mkdir ./venv", 79, nil

(where " mkdir ./venv" is the entire contents of a line in the markdown file, but it is inside a preformatted block being ignored by aspell, the actual occurrence of "venv" being complained about is further down, on a much longer line). I don't think the inherent problem here is the new aspell mode, it looks like the spellcheck result parsing is getting out of sync with where the actual occurrences are.

Hi,

I'm on emacs 28.2 with the the latest flymake-aspell[1] from MELPA. I set up init.el per the doc[2].

When I run (flymake-aspell-setup), I get the following error:

funcall-interactively: Symbol’s value as variable is void: flymake-diagnostic-functions

Below is a back trace. Please let me know if any additional data is needed or if I've borked something on my end. :\

Thank you!

Debugger entered--Lisp error: (void-variable flymake-diagnostic-functions)
  flymake-aspell-setup()
  funcall-interactively(flymake-aspell-setup)
  apply(funcall-interactively flymake-aspell-setup nil)
  repeat-complex-command(1)
  funcall-interactively(repeat-complex-command 1)
  call-interactively(repeat-complex-command nil nil)
  command-execute(repeat-complex-command)

References

1. Version - flymake-aspell-20221025.1844
2. init.el settings:

(setq ispell-dictionary "en_US")
(setq ispell-program-name "aspell")
(setq ispell-silently-savep t)