From: Devin Prater <r.d.t.prater@gmail.com>
To: Bob Newell <bobnewell@bobnewell.net>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Flyspell difficult to configure, documentation not honest
Date: Sat, 14 Jul 2018 13:59:09 -0500 [thread overview]
Message-ID: <CAGJxbF6pemmiokk=h4dYyXTefsGwENR2yoVOUGaLpuRmUqVT9A@mail.gmail.com> (raw)
In-Reply-To: <CADoYgq-j40_a3-y8MpYsVcQ9p_B2Qzke+8_COgrrMuoj0_mMmg@mail.gmail.com>
I agree, but there is only so much one can do with Emacs, but I do believe
Emacs does more with every brave coder that provides packages. Sure, not
everything works well with Emacspeak, but besides using Braille, Emacspeak
is the best program I use to read novels, email, write code, and browse
simple sites, with nov-mode, python-mode, gnus, org-mode, and eww, that I
have. For people that cannot use many of the mainstream programs, the TUI
of Emacs is a way for visually impaired, and those who have probably
visually seen it all and just want to get things done, to access computing.
This is why I always look for Emacs to take on more connectivity tasks:
accessing forums, social networks besides Twitter and Mastodon,
JavaScript+HTML5+web-app support, all that, because Emacs is the best
interface that blind users, with Emacspeak of course, have, well until a
Braille computing system that is modern is created.
--
Sent from Gmail Mobile
next prev parent reply other threads:[~2018-07-14 18:59 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 [this message]
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='CAGJxbF6pemmiokk=h4dYyXTefsGwENR2yoVOUGaLpuRmUqVT9A@mail.gmail.com' \
--to=r.d.t.prater@gmail.com \
--cc=bobnewell@bobnewell.net \
--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).