unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: help-gnu-emacs@gnu.org
Subject: Re: Flyspell difficult to configure, documentation not honest
Date: Sat, 14 Jul 2018 11:01:37 +0200	[thread overview]
Message-ID: <87y3eejimm.fsf@delle7240.chemeng.ucl.ac.uk> (raw)
In-Reply-To: 47820a66-3f49-4d80-e0c1-c5d3391a7240@posteo.net

On Friday, 13 Jul 2018 at 14:02, Brett Gilio wrote:
> On 07/13/2018 12:04 PM, Eric S Fraga wrote:
> Simple: especially with emails, I forget to do so and I end up with less
>> than appealing results...  The auto-correct features of flyspell allow
>> me to continue writing and only correct when I pause.
>
> You could attach a method to auto-spell check at the time of sending,
> and will halt the send if any invalid spellings are detected. From
> there you either correct the spelling/syntax, or you ignore it and
> then the file will proceed to the recepient.

Yes, I could.  However, I find that these types of checks
proliferate.  I already have checks for encryption and for
attachments.  I find that I often ignore the prompts and simply say yes
to everything which kind of makes it all pointless...  But that's me.

Anyway, as noted in another post in this thread, the beauty of Emacs is
that everybody can have the system work the way they like.  For me,
spell-checking while writing is what I like and I'm very happy with
flyspell.

-- 
Eric S Fraga via Emacs 27.0.50 & org 9.1.13 on Debian buster/sid




  reply	other threads:[~2018-07-14  9:01 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
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 [this message]
     [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=87y3eejimm.fsf@delle7240.chemeng.ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --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).