From: Agustin Martin <agustin.martin@hispalinux.es>
Subject: Re: More problems with flyspell
Date: Tue, 10 Jan 2006 15:46:24 +0100 [thread overview]
Message-ID: <20060110144624.GA1966@agmartin.aq.upm.es> (raw)
In-Reply-To: <87psn0k9h4.fsf-monnier+emacs@gnu.org>
On Mon, Jan 09, 2006 at 11:16:05PM -0500, Stefan Monnier wrote:
>
> ispell.el is not just an end-user package: it's also a library that provides
> services for flyspell. The flyspell-last-buffer variable was introduced to
> optimize a particular operation because flyspell needs that optimization,
> but the right place to put that optimization is in the ispell.el library,
> even if the ispell.el end-user commands don't directly benefit from it.
>
> >> PS: Maybe the same should be done with flyspell-word-cache-word, of course,
> >> but I'm not familiar enough with it.
>
> I wrote:
>
> > That is flyspell only, stores last word checked by (flyspell-word), so
> > flyspell-word is not called again unless cursor goes to a different word.
> > However is good to have it cleared when dict is changed to force re-checking
> > of current word, and the dict change is done from ispell.el. I think this
> > one should not be moved.
>
> Then maybe rather than move flyspell-last-buffer and
> flyspell-word-cache-word to ispell.el, ispell.el should provide an
> ispell-start-process-hook or ispell-change-dict-hook that flyspell could use
> to reset those vars.
This sounds good to me. What others think?
> Doing a (featurep 'flyspell) test is just really ugly.
I admit that even visually, seeing explicit "flyspell" strings and code in
ispell.el is something I dislike too.
--
Agustin
prev parent reply other threads:[~2006-01-10 14:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 13:37 More problems with flyspell Piet van Oostrum
2006-01-05 21:52 ` Stefan Monnier
2006-01-06 0:11 ` Agustin Martin
2006-01-08 14:47 ` Richard M. Stallman
2006-01-09 12:53 ` Agustin Martin
2006-01-09 18:26 ` Agustin Martin
2006-01-09 21:53 ` Stefan Monnier
2006-01-09 22:56 ` Agustin Martin
2006-01-10 4:16 ` Stefan Monnier
2006-01-10 14:46 ` Agustin Martin [this message]
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=20060110144624.GA1966@agmartin.aq.upm.es \
--to=agustin.martin@hispalinux.es \
/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).