unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: flyspell-buffer add word keep higlighted errors
Date: Wed, 06 Jan 2016 07:02:43 +0100	[thread overview]
Message-ID: <871t9vckjg.fsf@debian.uxu> (raw)
In-Reply-To: n6frp6$4v4$1@ger.gmane.org

Thorsten Grothe <grothe_news@e.mail.de> writes:

> That checks only errors for the current session of
> course. So sometimes I need to flyspell-buffer my
> old text. When I add an unknown word to the user dic
> *all* other marked words vanish and I have to run
> flyspell-buffer again, this is very frustrating for
> me, what I'm doing wrong?

As I've said a couple of times, I don't think flyspell
is a good idea, instead I prefer to do spelling once
and have the write and spell processes separated in
time. (But that's me and not you.)

What you are doing wrong is most likely putting all
that code into itself and each other like
a glacier icefall!

Take a look at this file of code, which by accident is
what I use for spelling:

    http://user.it.uu.se/~embe8573/conf/emacs-init/spell.el

You see the variables clearly defined at base level -
the settings - then the functions to control behavior.
Without boasting, it is mostly short and isolated
stuff with clear purposes and intentions.

If you write code in that style this will in one
strike get you closer to solving your problem if
indeed it remains. Whatever future problems/wishes
will be much easier to detect/solve/do, as well.

-- 
underground experts united
http://user.it.uu.se/~embe8573




  reply	other threads:[~2016-01-06  6:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-05  7:36 flyspell-buffer add word keep higlighted errors Thorsten Grothe
2016-01-06  6:02 ` Emanuel Berg [this message]
2016-01-06  8:54   ` Thorsten Grothe
2016-01-06 16:53     ` Emanuel Berg

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=871t9vckjg.fsf@debian.uxu \
    --to=embe8573@student.uu.se \
    --cc=help-gnu-emacs@gnu.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.
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).