all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Brett Gilio <brettg@posteo.net>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Flyspell difficult to configure, documentation not honest
Date: Sat, 14 Jul 2018 20:45:43 -0500	[thread overview]
Message-ID: <874lh146go.fsf@posteo.net> (raw)
In-Reply-To: <8736wmkxbs.fsf@delle7240.chemeng.ucl.ac.uk>


Eric S Fraga writes:
> Exactly and that's one of its most important selling points: my 
> Emacs is
> not your Emacs or anybody else's.  It works the way *I* want it 
> and
> yours works how you want it.  Indication of a software system 
> done well
> in my view.

This is quite literally the privilege of not only GNU/Linux, but 
Emacs
as a whole, the ability to have a capacity for individual 
workflows to
an unprecedented level. There is no monolithic way to achieve a 
certain
task, to produce a specific outcome. While there are ways more 
custom to
be "correct" or traditional, Emacs (or anything derived from a 
Lisp) is
rarely included in this procedure the way other applications are.

The strength of Emacs lies in its community and its ability to 
perform
such a vast variety of tasks in a way that is simply uncomparable.

As far as Flyspell goes, the documentation in my opinion seems 
more or
less clear, and is not in any way intended to obfuscate the 
end-user
from its use with precision. However, there are parts of it that 
may be
dated.




-- 
Brett M. Gilio
Free Software Foundation, Member
https://parabola.nu | https://emacs.org



  parent reply	other threads:[~2018-07-15  1:45 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874lh146go.fsf@posteo.net \
    --to=brettg@posteo.net \
    --cc=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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.