Bug 471085
Summary: | emacs-22.x hangs on spellchecking when hunspell set as ispell helper application | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Doug Maxey <dwm> |
Component: | hunspell | Assignee: | Caolan McNamara <caolanm> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 10 | CC: | bugzilla, caolanm, dcantrell, dwm |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-11-26 15:11:41 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Doug Maxey
2008-11-11 18:03:42 UTC
It appears that forcing ispell (hunspell) to re-read the buffer for spell checking also triggers the same hang. Ok. Have confirmed that the hanging app is indeed hunspell. I get the same behaviour with an MUA that has nothing to do with emacs, other than both use hunspell. Raising to high as this completely blocks any MUA or editor that attempts to use. Are you 100% sure it is hunspell. You say "forcing ispell (hunspell) to..." and the hunspell rpm does not provide an ispell alias, aspell does that. That said, I'm not an emacs user, so if you give an idiots guide to reproducing this I can have a look. (In reply to comment #3) > Are you 100% sure it is hunspell. You say "forcing ispell (hunspell) to..." and > the hunspell rpm does not provide an ispell alias, aspell does that. Thanks for looking into this. Yes. 100%. I have to declare hunspell in emacs as the 'ispell' program name. Once I got emacs to work, I took the args it was run with and use that in exmh (prefered MUA). > > That said, I'm not an emacs user, so if you give an idiots guide to reproducing > this I can have a look. heh. It gets started as 'hunspell -a -m -B'. That's about as far as I can take you. That apparently gets it to read in the entire buffer. ++doug Aha, F-9 hunspell didn't have a -m option, but it does now. Unfortunately it does something quite different to the ispell -m option, so the responses aren't as expected as it kicks hunspell into a different mode So to workaround in emacs spellchecking options, if you set the ispell extra arg to "-a" then hunspell will be invoked as hunspell -a -m -B -a and the second -a will override the -m which triggers a different mode in hunspell. That'll get you back to the F-9 situation. Patch to fix properly filed upstream as http://sourceforge.net/tracker/?func=detail&atid=756397&aid=2314461&group_id=143754 and checked into devel and F-10 and built to f10-updates-candidates There is a workaround, (extra -a) and its not the out-of-box configuration so I don't see it as a F-10 blocker Hm. Interesting. My config neither adds or deletes any flags that I can discern. Looking into how to add the extra -a. Give this a go... (custom-set-variables '(ispell-extra-args (quote ("-a"))) '(ispell-program-name "/usr/bin/hunspell")) Thanks. This does stop the hangs. This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Done in rawhide, will be in F-11 |