unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Bob Newell <bobnewell@bobnewell.net>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Debunking Emacs merits over GUI - Re: package for Email
Date: Sat, 21 Jan 2023 10:05:31 +0300	[thread overview]
Message-ID: <Y8uOu7fuxkDUrmAi@protected.localdomain> (raw)
In-Reply-To: <877cxgrc3e.mmmtqrm@thhcbmmmd.mijofcrcc.org>

* Bob Newell <bobnewell@bobnewell.net> [2023-01-21 03:08]:
> > Objectively, Emacs is not an option as e-mail client for anybody.
> 
> I must differ as I think "anybody" is too broad.  There are
> thousands of Gnus users, myself included.  Gnus enables me to
> do things--- things important to my work and pursuits--- that
> would be much more laborious or maybe not even possible with
> other clients.

You are right, it is generalization, which I did not intend. I have
expressed me in the way how I did not want. I am myself using Emacs to
start composing e-mails, and to manage e-mails in combination with
various tools, and sometimes I use Emacs e-mail package.

I wanted to say that objectively when somebody is looking for e-mail
client, it is not good to recommend Emacs in first place.

Any e-mail client enable people to do important tasks. So it is `mail'
too! 

I bet you do not use `mail' on command line. And me too, I do not use
it often on command line, but I may use it sometimes, and I use it
hundreds of thousands of times from within Emacs! 

However, that I use `mail' in that particular way is very specific to
me. We make thousands and thousands of dollars by using `mail' and the
packge 

Emacs Lisp: rcd-mail.el package as bindings to GNU Mailutils "mail" program:
https://hyperscope.link/3/8/3/0/3/rcd-mail-el-GNU-Mailutils-mail-program.html

My personal use is related to integration with other packages in
Emacs, for example, I don't like composing e-mails, and I prefer to
simply write e-mail, while everything else is handled for me: 

- e-mail subject, to be automatically handled (or customized when
  necessary)

- greetings, to be automatically handled,

- my identity towards recipient, to be automatically handled,

- my signature to be automatically handled

All of the messages are where? In the table `messages'. I can easily
find any message sent in that automated manner. And messages have
their types:

 1          E-mail
 2          SMS
 3          XMPP
 4          Call
 5          Talk

Now imagine a list of communication lines, like e-mail, SMS, XMPP:

Bob, e-mail, bob@example.com
Bob, SMS, +1234567890
bob, XMPP, bob@xmpp.example

I don't think of e-mails, I think of "Bob" and that I have to tell him
something, so I mark those above three lines, and write single
message. 

Single message is then sent to all of those communication lines,
alerting person on what we have to talk about.

Why think of invoking XMPP client?
Why think of getting phone in my hand and type?
Why think of invoking e-mail client?

What I think of is that what I have to communicate to person.

So in my environment I find myself efficient as I keep working on
integration of functions for human need.

It is very easy to teach staff member to:
-----------------------------------------

- find person among many people in Emacs or other tool (because there
  is universally accessible database in background)

- click on "l c" for "List Communication Lines"

- mark communication lines

- send message or prepared document


Instead of teaching people:
---------------------------

- to use Thunderbird, Emacs mail client, etc. too much of software and
  hand work

- to teach people how to use Gajim, Pidgin, Dino, Conversations, you
  name it, hand work

- to teach them how to enter one person's contacts in each of the
  above software as they do not have integrated access to contacts
  database 

- to teach them how to attach documents, upload files, etc. way too
  much

- then to give them task to send information to those people, all one
  by one.

I find that approach efficient.

Am I ever going to recommend it to acquaintance or person on mailing
list as the way of handling e-mails? Rather no, because that is not
the environment and need or demand by that person.

IMHO, Emacs is last environment I would recommend average person.

When person is let us say in GNU/Linux environment, than it becomes
closer to recommendation.

My staff members learned `mutt' and were using it properly. They have
installed Hyperbola GNU/Linux-libre by following my advise on a
Thinkpad computer. They however, were compelled into it. And they used
it fine, because they took little time to learn basic functions.

However, to recommend people to start with tools I am personally
using, I say rather no, as that would waste their time.

When person is willing to learn and wish to become efficient in some
specific areas of life, I would again try to find what is the best
fitting or best matching computing solution for that person. 

I am aware that my habits, experiences, skills, efficiency is all
personal. 

It is not universal and applicable to everybody.

> But that doesn't mean that some people find Gnus etc. to be a
> very powerful productivity tool.

Yes, I understand, sure. Me too, I was using it back in time, I don't
remember when, maybe before 20 years, who knows. I was reading `news'
with it.

> I would like to generalize "human" to "requirements" based on
> the job at hand, the capabilities and desires of the user, and
> so on, to create a wholistic solution.  Choosing software
> prior to understanding what is needed is folly.  Yet it is
> done very often.  (Queue entry of salespeople wearing suits
> who talk only to corporate executives and never to end-users
> about their multi-million dollar product.  Said conversations
> to take place on a private golf course.)

That is right.

Thanks for exchanging!

-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/



  parent reply	other threads:[~2023-01-21  7:05 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
2023-01-20  9:47         ` Jean Louis
     [not found]           ` <877cxgrc3e.mmmtqrm@thhcbmmmd.mijofcrcc.org>
2023-01-21  7:05             ` Jean Louis [this message]
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=Y8uOu7fuxkDUrmAi@protected.localdomain \
    --to=bugs@gnu.support \
    --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).