From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: bug-gnu-emacs-mXXj517/zsQ@public.gmane.org
Subject: Re: bug#13109: 24.1; flyspell highlights words containing curly quotes which ispell-buffer accepts
Date: Sat, 04 May 2013 21:26:30 +0200 [thread overview]
Message-ID: <86bo8qim1l.fsf@somewhere.org> (raw)
In-Reply-To: mailman.25084.1367614166.855.bug-gnu-emacs@gnu.org
Hello Reuben,
Reuben Thomas wrote:
>>> I've copied the default settings and added a curly single quote to the
>>> list of permitted "other characters". I imagine one can do the same for
>>> other languages. It's ugly (principally because it copies rather than
>>> overwriting information) but that information (the other entries in the
>>> record) doesn't change often, so it'll do until a more comprehensive
>>> solution is applied.
>>>
>>
>> Belay that, it doesn't work. It seems I have to type a new word for
>> flyspell to complain; merely passing the cursor over an old one (which
>> suffices to remove a highlight in a word that has been added to the
>> dictionary) does not suffice.
>>
>> If anyone can offer a functioning workaround, I'd be most grateful.
>>
>
> I read the documentation for ispell-dictionary-alist more carefully, and
> came up with:
>
> '(ispell-local-dictionary-alist (quote (("british" "[[:alpha:]]"
> "[^[:alpha:]]" "['’]" t ("-d" "en_GB") nil utf-8))))
>
> where I made the "others" character set a character class.
Not answering your questions, but commenting about this: it never has been
clear to me which var should really be edited...
`ispell-dictionary-base-alist', `ispell-base-dicts-override-alist' or
`ispell-local-dictionary-alist'...
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2013-05-04 19:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 23:59 bug#13109: 24.1; flyspell highlights words containing curly quotes which ispell-buffer accepts Reuben Thomas
2012-12-07 6:29 ` Eli Zaretskii
[not found] ` <CAOnWdoiiaW0gvHTEuunsZvkqn8a6A4tLsQC4WoF3jgy40onjMg@mail.gmail.com>
2012-12-07 13:57 ` Eli Zaretskii
2012-12-07 15:27 ` Reuben Thomas
2012-12-09 21:24 ` Reuben Thomas
2012-12-10 23:34 ` Juri Linkov
2012-12-11 16:20 ` Reuben Thomas
2012-12-11 23:07 ` Juri Linkov
2013-05-03 20:15 ` Reuben Thomas
2013-05-03 20:20 ` Reuben Thomas
2013-05-03 20:48 ` Reuben Thomas
[not found] ` <mailman.25084.1367614166.855.bug-gnu-emacs@gnu.org>
2013-05-04 19:26 ` Sebastien Vauban [this message]
2013-05-06 10:32 ` Agustin Martin
2015-06-26 11:46 ` bug#13109: Thanks Reuben Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86bo8qim1l.fsf@somewhere.org \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=bug-gnu-emacs-mXXj517/zsQ@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).