From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Flyspell difficult to configure, documentation not honest
Date: Fri, 13 Jul 2018 10:15:51 +0300 [thread overview]
Message-ID: <83a7qvehco.fsf@gnu.org> (raw)
In-Reply-To: <2e2b282a-4693-5bbb-3144-3899e455607b@posteo.net> (message from Brett Gilio on Thu, 12 Jul 2018 16:01:36 -0500)
> From: Brett Gilio <brettg@posteo.net>
> Date: Thu, 12 Jul 2018 16:01:36 -0500
>
> I completely second everything you said, Emanuel. Spell checking on the
> fly is not only extremely prone to false-errors, but it also poses a lot
> of issues with emacs performance and even some false errors with
> packages like helm (in my experience).
No one needs to use a feature they don't like.
I personally find Flyspell useful in text-mode buffers, like
ChangeLog, Texinfo mode, mail-mode, and other modes where I write
human-readable text. It keeps me from making stupid typos.
Performance is not an issue normally in these modes, where most of the
time I just think what to write next anyway.
I almost never turn on Flyspell in program source buffers. YMMV.
next prev parent reply other threads:[~2018-07-13 7:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <974173872.5393015.1531407541695.ref@mail.yahoo.com>
2018-07-12 14:59 ` Flyspell difficult to configure, documentation not honest R. Diez
2018-07-12 16:26 ` Eli Zaretskii
[not found] ` <mailman.3464.1531407559.1292.help-gnu-emacs@gnu.org>
2018-07-12 17:30 ` Emanuel Berg
2018-07-12 21:01 ` Brett Gilio
2018-07-13 7:15 ` Eli Zaretskii [this message]
2018-07-13 11:31 ` Gregor Zattler
2018-07-13 12:50 ` Devin Prater
2018-07-13 13:35 ` Teemu Likonen
[not found] ` <mailman.3518.1531488931.1292.help-gnu-emacs@gnu.org>
2018-07-13 14:42 ` Emanuel Berg
2018-07-13 7:41 ` Eric S Fraga
2018-07-13 17:08 ` Bob Newell
2018-07-14 8:58 ` Eric S Fraga
2018-07-14 9:15 ` tomas
2018-07-14 17:47 ` Bob Newell
2018-07-14 18:59 ` Devin Prater
2018-07-15 1:45 ` Brett Gilio
2018-07-15 2:42 ` Eli Zaretskii
[not found] ` <mailman.3502.1531467702.1292.help-gnu-emacs@gnu.org>
2018-07-13 10:22 ` Emanuel Berg
2018-07-13 17:04 ` Eric S Fraga
2018-07-13 19:02 ` Brett Gilio
2018-07-14 9:01 ` Eric S Fraga
[not found] ` <mailman.3536.1531501486.1292.help-gnu-emacs@gnu.org>
2018-07-13 18:41 ` Emanuel Berg
2018-07-13 19:06 ` Brett Gilio
2018-07-14 9:03 ` Eric S Fraga
2018-07-14 9:02 ` Eric S Fraga
[not found] <1186940967.5630978.1531432200575.ref@mail.yahoo.com>
2018-07-12 21:50 ` R. Diez
2018-07-13 6:35 ` Eli Zaretskii
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=83a7qvehco.fsf@gnu.org \
--to=eliz@gnu.org \
--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).