ispell no longer working in mu4e:compose buffer

[Jeff Kowalczyk]

Recently I noticed that M-x ispell calling aspell is no longer working in the mu4e compose *draft* buffer:

Spell-checking *draft* using aspell with default dictionary...done

hangs until C-g to cancel. There is no additional info written to *Messages*.

The command works in buffers using other modes.

Any ideas what might be causing this?

Using mu4e @ ab5830 (0.9.9.6).

Thanks,

Jeff

[Dirk-Jan C. Binnema]

On Tuesday Jul 15 2014, Jeff Kowalczyk wrote:

> Recently I noticed that M-x ispell calling aspell is no longer working in
> the mu4e compose *draft* buffer:
>
> Spell-checking *draft* using aspell with default dictionary...done
>
> hangs until C-g to cancel. There is no additional info written to
> *Messages*.
>
> The command works in buffers using other modes.
>
> Any ideas what might be causing this?

Hmm.... can you try with `M-x toggle-debug-on-quit' to get a stack trace
from the C-g?

Cheers,
Dirk.

--
Dirk-Jan C. Binnema Helsinki, Finland
e:dj...@djcbsoftware.nl w:www.djcbsoftware.nl
pgp: D09C E664 897D 7D39 5047 A178 E96A C7A1 017D DA3C

[Jeff Kowalczyk]

On Tuesday, July 15, 2014 1:10:41 PM UTC-7, djcb wrote:

Hmm.... can you try with `M-x toggle-debug-on-quit' to get a stack trace
from the C-g?

Interestingly, the behavior is different with the compose new message (ispell hangs) vs. a reply message buffer (ispell works normally).

The stack trace from a compose new buffer:

 Debugger entered--Lisp error: (quit)

  accept-process-output(#<process ispell> nil nil)

  ispell-accept-output()

  ispell-process-line("^--text follows this line\n" nil)

  ispell-region(47 342)

  ispell-buffer()

  ispell()

  funcall-interactively(ispell)

  call-interactively(ispell record nil)

  command-execute(ispell record)

  smex-read-and-run(("ispell" "toggle-debug-on-quit" "mu4e"

  "org-clock-jump-to-current-clock" "flush-lines" "keep-lines"

  "mu4e-view-save-attachment" "simple-quote-characters"

  "delete-trailing-whitespace" "qrr" "insert-date" "org-sort"

  "org-narrow-to-subtree" "customize-themes" "sort-lines" "delete-frame"

  "org-mode" "el-get-list-packages" "ediff" "org-insert-link"

  "column-number-mode" "date-mmddyyyy-to-iso" "ispell-word" "org-table-export"

  "rectangle-number-lines" "org-store-link" "org-clock-in-last" "goto-char"

  "goto-line" "ein:connect-to-notebook" "org-table-import" "inferior-lisp"

  "org-clock-cancel" "org-open-at-point" "ein:notebooklist-open" "calc"

  "kill-line" "ledger-mode" "python-mode" "insert-date-and-time"

  "menu-bar-showhide-tool-bar-menu-customize-enable-top" "emacs-version"

  "el-get-reinstall" "eww" "sql-mode" "text-mode" "set-variable"

  "mu4e-view-refresh" "mu4e-view-save-attachment-multi" "kill-region" ...))

  smex()

  funcall-interactively(smex)

  call-interactively(smex nil nil)

  command-execute(smex)

[Dirk-Jan C. Binnema]

On Tuesday Jul 15 2014, Jeff Kowalczyk wrote:

Hmmm.... seems like something you should ask the ispell people. for some
reason the 'text-follows-this-line' thing seems to trip it up.

[Gustavo]

Hello.
I seem to have a similar problem: when composing a message, spell checking makes Emacs "hang". I get the following backtrace:

Debugger entered--Lisp error: (quit)
  flyspell-small-region(39 139)
  flyspell-region(39 139)
  flyspell-buffer()
  call-interactively(flyspell-buffer nil nil)
  command-execute(flyspell-buffer)

I don't know even know where to file a bug report.
However, this seems to occur only when I try to spellcheck a message that was never saved to disk. Once saved, it works fine.

Does anyone have any idea of what is happening?

Thank you.
--
Gustavo

e:d...@djcbsoftware.nl           w:www.djcbsoftware.nl

[Dirk-Jan C. Binnema]

On Tuesday May 31 2016, Gustavo wrote:

> Hello.
> I seem to have a similar problem: when composing a message, spell checking
> makes Emacs "hang". I get the following backtrace:
>
> Debugger entered--Lisp error: (quit)
> flyspell-small-region(39 139)
> flyspell-region(39 139)
> flyspell-buffer()
> call-interactively(flyspell-buffer nil nil)
> command-execute(flyspell-buffer)
>
> I don't know even know where to file a bug report.
> However, this seems to occur only when I try to spellcheck a message that
> was never saved to disk. Once saved, it works fine.
>
> Does anyone have any idea of what is happening?

This seems like an issue with flyspell -- probably best to file a bug --
M-x report-emacs-bug.

Kind regards,

Dirk.

--
Dirk-Jan C. Binnema Helsinki, Finland

e:dj...@djcbsoftware.nl w:www.djcbsoftware.nl