unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: John Mastro <john.b.mastro@gmail.com>
To: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: About how misspelled word are displayed
Date: Fri, 12 May 2017 17:22:22 -0700	[thread overview]
Message-ID: <CAOj2CQS7WwU2WaPVj728zOfwsceedM8k8th1dL_0eagLzV4vxA@mail.gmail.com> (raw)
In-Reply-To: <yw.86bmqxmylk.fsf@zoho.com>

Emanuel Berg <moasen@zoho.com> wrote:
> By the way flyspell isn't such a good idea.
> It is disruptive to do this as you type.
> Better to focus on typing (hands) and looking
> (eyes) and thinking (brain). When you are done
> writing, you can do ispell once. It also has
> different gears depending on what buffer you
> are in - for example, in a code buffer, only
> strings and comments are checked.

FWIW, flyspell also has that feature, `flyspell-prog-mode'.

I half-agree with you about on-the-fly spell checking, mostly because I
find the inevitable false positives somewhat distracting.

However, I still use it because, with both text and code, I find I'm
often editing things where "done" is not a clearly-defined state. Emails
are an exception, because eventually you send it and that's it. Most
documents I work with aren't like that. I prefer to see the errors and
fix them now, so they don't hang around in the document and/or my
subconscious longer than necessary.

        John



  reply	other threads:[~2017-05-13  0:22 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-12  9:49 About how misspelled word are displayed Angelo Graziosi
2017-05-12 13:09 ` Kaushal Modi
2017-05-12 14:07   ` Angelo Graziosi
2017-05-12 14:14     ` tomas
2017-05-12 14:27       ` Emanuel Berg
2017-05-12 15:16         ` Drew Adams
2017-05-12 16:27           ` Emanuel Berg
2017-05-12 17:32             ` Drew Adams
2017-05-12 18:00               ` Emanuel Berg
2017-05-12 21:15                 ` tomas
2017-05-12 21:28               ` N. Raghavendra
2017-05-12 22:08                 ` Drew Adams
2017-05-13 14:15                   ` N. Raghavendra
2017-05-13 14:59                     ` Emanuel Berg
2017-05-13 15:07                       ` Emanuel Berg
2017-05-13 15:22                         ` Emanuel Berg
2017-05-13 15:34                       ` N. Raghavendra
2017-05-13 15:54                         ` Emanuel Berg
2017-05-13 17:59                     ` Drew Adams
2017-05-14 13:07               ` N. Raghavendra
2017-05-12 19:30   ` Angelo Graziosi
2017-05-12 20:34     ` Drew Adams
2017-05-12 20:41       ` Drew Adams
2017-05-12 22:14         ` Angelo Graziosi
2017-05-12 23:42           ` Emanuel Berg
2017-05-13  0:22             ` John Mastro [this message]
2017-05-13  9:53               ` Emanuel Berg
2017-05-12 21:07       ` Emanuel Berg
2017-05-12 19:57   ` Angelo Graziosi
2017-05-12 20:56     ` 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=CAOj2CQS7WwU2WaPVj728zOfwsceedM8k8th1dL_0eagLzV4vxA@mail.gmail.com \
    --to=john.b.mastro@gmail.com \
    --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).