unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Bob Newell <bobnewell@bobnewell.net>
To: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: Debunking Emacs merits over GUI - Re: package for Email
Date: Thu, 19 Jan 2023 11:10:51 -1000	[thread overview]
Message-ID: <CADoYgq-f9wuRagRe+b4wpmWmHKM-uWd2UzW9MXryCtfLkb1oYA@mail.gmail.com> (raw)
In-Reply-To: <20230119161030.vt4muwcdvuwdqmj7@zoho.com>

> >Doug Engelbart invented mouse device for people to speed up with
> >work. Using mouse is just fine.

Certainly it is.  But remember it is a matter of choice and user
preference.  I find having to reach for the mouse and remove hands
from keyboard very disruptive.

> Yes you are right. I am biased here. Keyboard-centric is not merit, it
> is just a feature.

Again, depending on the point of vue of the user.

> >> - You can manipulate emails buffers just like normal text buffers.

Well, actually you can in GNUS and probably other Emacs clients.

Not to say Thunderbird isn't good.  I actually think it's a very good
client.  It is just not what I prefer as I like to stay within Emacs.

> >It is way too exaggerated and generalized statement. The "powerful
> >way" in any software comes with experience. To learn what you think is
> >powerful requires maybe decades.

This is something I've stressed before.  Serious tools for craftsmen
require serious effort.  No one starts out as a master craftsman.
Everyone starts as a novice.  Does that mean that the tools of the
master are inferior because the novice is not yet skilled with them?
Hardly.

> But an average user won't use emacs as its text editor. An average user
> writes proses use MS Word.

And that's fine.  To each his own.

> >About writing in "Org mode", there is no special advantage for people
> >who use e-mail unless those people are Emacs users. To draw somebody
> >to be Emacs user into Org mode is getting person in trouble.

I will again say something I've said before.  Emacs is not for
everyone, and I don't mean that in an elitist sense.  For many of us
it is an indispensible tool, which we've spent a long while learning
how to use to best advantage.  For others it may just be a big bother
when simpler and easier tools may work just fine for their needs.

I am not out there telling people "learn Emacs" without first knowing
what their interests and inclinations may be.  That indeed could be
unproductive.  I think people who can make use of Emacs find their way
to it eventually.

-- 
Bob Newell
Honolulu, Hawai`i

Via Linux/Emacs/Gnus/BBDB.



  parent reply	other threads:[~2023-01-19 21:10 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18 13:56 package for Email Gottfried
2023-01-18 14:44 ` Eric Brown
2023-01-18 15:15 ` Jean Louis
2023-01-19  7:31   ` Tomas Hlavaty
2023-01-19  7:55     ` Jean Louis
2023-01-18 15:51 ` Tassilo Horn
2023-01-18 17:17   ` Eli Zaretskii
2023-01-18 17:58     ` andrés ramírez
2023-01-19  3:55       ` Jean Louis
2023-01-18 16:28 ` Andreas Eder
2023-01-18 18:03 ` Milan Glacier
2023-01-19  4:02   ` Jean Louis
2023-01-19  5:06   ` Debunking Emacs merits over GUI - " Jean Louis
2023-01-19  5:41     ` Emanuel Berg
2023-01-19 13:00       ` Jean Louis
2023-01-19 15:34         ` Marcin Borkowski
2023-01-20  8:27           ` Jean Louis
2023-01-19 16:10     ` Milan Glacier
2023-01-19 16:52       ` Jude DaShiell
2023-01-20  9:32         ` Jean Louis
2023-01-19 21:10       ` Bob Newell [this message]
2023-01-20  9:47         ` Jean Louis
     [not found]           ` <877cxgrc3e.mmmtqrm@thhcbmmmd.mijofcrcc.org>
2023-01-21  7:05             ` Jean Louis
2023-01-21  7:20               ` Emanuel Berg
2023-01-21  7:21               ` Eli Zaretskii
2023-01-21  7:28                 ` Emanuel Berg
2023-01-21 14:29                   ` Jean Louis
2023-01-21 14:28                 ` Jean Louis
2023-01-21 15:31                   ` Eli Zaretskii
2023-01-21 17:30                     ` Bob Newell
2023-01-22 15:40                       ` Jean Louis
2023-01-20  9:07       ` Jean Louis
2023-01-20 15:52         ` Milan Glacier
2023-01-21  6:04     ` History " David Masterson
2023-01-21  7:10       ` Eli Zaretskii
2023-01-21  7:21         ` Emanuel Berg
2023-01-21  7:34         ` tomas
2023-01-21 17:38         ` Bob Newell
2023-01-22  3:16           ` David Masterson
2023-01-22 15:48           ` Jean Louis
2023-01-22  3:08         ` David Masterson
2023-01-22  6:23           ` Eli Zaretskii
2023-01-22 19:33             ` David Masterson
2023-01-22 19:57               ` Eli Zaretskii
2023-01-22  7:45           ` Po Lu
2023-01-22 19:35             ` David Masterson
2023-01-21 14:35       ` Jean Louis
2023-01-22  3:33         ` David Masterson
2023-03-10 17:16       ` Emanuel Berg
2023-03-13  8:32         ` Po Lu
2023-01-18 18:10 ` Filipp Gunbin
2023-01-19  2:15 ` Emanuel Berg
2023-01-19 12:40   ` Jean Louis
2023-01-19 14:10   ` Martin Steffen
2023-01-19 16:20     ` Eric S Fraga
2023-01-19 16:39       ` Jude DaShiell
2023-01-20 10:05         ` Jean Louis
2023-01-19 17:00       ` Leo Butler
2023-01-19 17:35         ` Eric S Fraga
2023-01-20  6:48       ` Milan Glacier
2023-01-19  3:53 ` Jean Louis
2023-01-19  6:08 ` John Haman
2023-01-19 11:52   ` Emanuel Berg
2023-01-21 13:57     ` Jean Louis
2023-01-21 15:08       ` Jude DaShiell
2023-01-21 17:47       ` Bob Newell
2023-01-22  3:46         ` David Masterson
2023-01-22 19:52           ` Bob Newell
2023-01-22  3:34     ` David Masterson
2023-01-31  5:46       ` Emanuel Berg
2023-01-20  4:09   ` Milan Glacier
2023-01-20  7:31     ` Emanuel Berg
2023-01-20 10:26     ` Jean Louis

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=CADoYgq-f9wuRagRe+b4wpmWmHKM-uWd2UzW9MXryCtfLkb1oYA@mail.gmail.com \
    --to=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).