From: Agustin Martin <agustin.martin@hispalinux.es>
To: Nathaniel Cunningham <nathaniel.cunningham@gmail.com>,
emacs-pretest-bug@gnu.org
Cc: David Reitter <david.reitter@gmail.com>, Manuel.Serrano@unice.fr
Subject: Re: flyspell functions don't initialize aspell dicts
Date: Tue, 13 May 2008 12:19:48 +0200 [thread overview]
Message-ID: <20080513101948.GA4281@agmartin.aq.upm.es> (raw)
In-Reply-To: <20ecf6c70805121527y505e6bd5qabad4e401eeaffef@mail.gmail.com>
On Mon, May 12, 2008 at 05:27:46PM -0500, Nathaniel Cunningham wrote:
> Greetings,
> I've found that (flyspell-buffer) doesn't go through the same dictionary
> initialization steps as (ispell-buffer). Specifically, the flyspell
> functions (flyspell-word) and (flyspell-large-region) don't call
> (ispell-maybe-find-aspell-dictionaries), they way (ispell-region) and
> (flyspell-mode) do. The result: user's aspell setup (if present) doesn't
> get to inform `ispell-dictionary-alist', unless e.g. (ispell-buffer) or
> (flyspell-mode) is called first.
>
> I believe simply adding (ispell-maybe-find-aspell-dictionaries) near the top
> of `flyspell-word' and `flyspell-large-region' definitions, as it already is
> for `flyspell-mode-on', will take care of this.
(ispell-maybe-find-aspell-dictionaries) is no longer used in fsf emacs
ispell.el or flyspell.el. It has been recently replaced by a more generic
(ispell-set-spellchecker-params), which is also called from (flyspell-word)
and (flyspell-large-region).
flyspell.el: Revision 1.131
ispell.el: Revision 1.227
Regards,
--
Agustin
next prev parent reply other threads:[~2008-05-13 10:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87y73lrc8c.fsf@stupidchicken.com>
2008-05-12 22:27 ` flyspell functions don't initialize aspell dicts Nathaniel Cunningham
2008-05-13 10:19 ` Agustin Martin [this message]
2008-07-28 20:25 ` bug#232: marked as done (flyspell functions don't initialize aspell dicts) Emacs bug Tracking System
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080513101948.GA4281@agmartin.aq.upm.es \
--to=agustin.martin@hispalinux.es \
--cc=Manuel.Serrano@unice.fr \
--cc=david.reitter@gmail.com \
--cc=emacs-pretest-bug@gnu.org \
--cc=nathaniel.cunningham@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.