From: Emanuel Berg <embe8573@student.uu.se>
To: info-gnus-english@gnu.org
Subject: Re: Trigger spell checking before sending [flyspell?]
Date: Fri, 12 Feb 2016 01:21:44 +0100 [thread overview]
Message-ID: <87ziv6bwx3.fsf@debian.uxu> (raw)
In-Reply-To: <anfi+dyccrxmhtf-g2c5@wp.eu>
"Andrzej A. Filip" <andrzej.filip@gmail.com> writes:
> Do you use flyspell? It may deliver what you want in
> another way.
Ispell is better. Write, then spell, then send. Do it
all at once you loose your mindfulness and the result
will suffer. Flyspell sounds good but in practice too
many words that should be there aren't, which means
correct words will pop up as incorrect or unknown all
the time while typing. This is when the brain should
not focus on spelling but on conveying a message from
one person to another. The fingers should do the
spelling and in time they will. For the occasional
mistake spellcheck just before send is a much
better idea.
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2016-02-12 0:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 22:47 Trigger spell checking before sending Pietro
2016-02-11 23:34 ` Emanuel Berg
2016-02-12 14:05 ` Pietro
2016-02-13 3:27 ` Emanuel Berg
2016-02-13 4:42 ` Emanuel Berg
2016-02-18 16:11 ` Pietro
2016-02-19 0:17 ` Emanuel Berg
2016-02-19 10:20 ` Pietro
2016-03-05 17:38 ` Pietro
2016-03-05 17:43 ` Pietro
2016-03-06 5:53 ` Emanuel Berg
2016-02-19 13:53 ` B.V. Raghav
2016-02-19 20:15 ` Emanuel Berg
2016-02-20 7:12 ` B.V. Raghav
2016-02-15 11:12 ` Peter Münster
2016-02-12 0:07 ` Trigger spell checking before sending [flyspell?] Andrzej A. Filip
2016-02-12 0:21 ` Emanuel Berg [this message]
2016-02-12 8:58 ` Andrzej A. Filip
2016-02-13 4:47 ` Emanuel Berg
[not found] ` <mailman.4442.1455236524.843.info-gnus-english@gnu.org>
2016-02-12 9:41 ` Loris Bennett
2016-02-13 5:00 ` Emanuel Berg
2016-02-12 7:31 ` Trigger spell checking before sending Eric S Fraga
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=87ziv6bwx3.fsf@debian.uxu \
--to=embe8573@student.uu.se \
--cc=info-gnus-english@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 NNTP newsgroup(s).