From: Jean Louis <bugs@gnu.support>
To: Milan Glacier <news@milanglacier.com>
Cc: John Haman <mail@johnhaman.org>, help-gnu-emacs@gnu.org
Subject: Re: package for Email
Date: Fri, 20 Jan 2023 13:26:30 +0300 [thread overview]
Message-ID: <Y8psVouhti2YfHmW@protected.localdomain> (raw)
In-Reply-To: <20230120040921.n2r2llvbry4li4g2@zoho.com>
* Milan Glacier <news@milanglacier.com> [2023-01-20 07:11]:
> On 01/19/23 01:08, John Haman wrote:
> >
> > I use Gnus, and like others have said, with some configuration, it is
> > very nice. I use nnimap backend with fastmail accounts, and it is indeed
> > fast. I like that I don't have to download all my email on every
> > computer. And I like reading my mails, nntp, web feeds in one place. My
> > gnus settings are more portable than my tbird settings.
> >
> > I don't recommend Gnus unless you have a lot of time to configure Emacs
> > and don't do any business/HTML email.
>
> I think reading business email is okay for plain text based MUA.
Definitely. Just that majority of businessmen on this world can't
agree with me.
First in business, we may get a lot of spam, and lot of
tracking. Coincidentallyand due to lack of HTML in text based mail
user agents, we are spared of tracking and surveillance.
On the other hand, one percentage of businessmen do not have text
e-mails, and thy arrive as HTML, we have to somehow read that.
And speedy writing, parsing, searching, manipulating, bouncing,
forwarding, it is all there and very useful.
And yet, it is not objectively real to recommend such program to
modern business people.
The time to tell that it is useful is when it really can make some
money out of that usefulness.
> Usually business email has alternative plain text form which is
> readable. And if you want to compose HTML email, you can write
> orgmode emails and then converted it to HTML (this is done by
> package: org-msg).
Okay, I do understand. And Org mode allows easy writing, hyperlinks,
images, tables and pretty easy conversions to HTML or other formats.
And at this point I like to give you something for thinking:
TECHNOLOGY TEMPLATE PROJECT OHS Framework :
https://www.dougengelbart.org/content/view/110/460/
where it says:
| From | To |
|---------------------+-------------------------|
| Tool-centric system | Document-centric system |
Let's think of the workflow:
----------------------------
1. Launch tool program (like Mutt, or any)
2. Find recipient's contact
3. Write document
4. Send it.
5. Realize after some time you may be writing same markup documents or
same documents, or having repetition, like attaching files numerous
times, and so on.
How about this workflow:
------------------------
1. Write document once and all attachments.
2. Relate person to document.
3. Press key, choose person, dispatch.
In this way user does not really deal with e-mail program directly,
only decides that some information shall be sent to specific people.
E-mail is multi part by MIME standard.
Instead of giving to user to put this picture, that audio, and
presentation, and PDF file, e-mail introduction and cover letter, and
letting user do all that work with e-mail and attachments, it is more
useful to have document centric system where user prepares documents,
and only decides to which people to send it, without bothing how to
attach it, how to prepare e-mail, etc.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
prev parent reply other threads:[~2023-01-20 10:26 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
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 [this message]
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=Y8psVouhti2YfHmW@protected.localdomain \
--to=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.org \
--cc=mail@johnhaman.org \
--cc=news@milanglacier.com \
/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.