edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev]  mailx
Date: Sun, 12 Apr 2015 12:00:47 -0400	[thread overview]
Message-ID: <20150312120047.eklhad@comcast.net> (raw)

> I think that the heirloom-mailx version can do all these things since it
> supports every mail protocol I can think of.

It's not the protocols, it's the user interface.

> we need ...  imap (with imaps and starttls support),

Handled by curl, to some degree.

> pop3 (with ssl and tls support),

Already done, mostly by curl.

> mbox and maildir support (for local mail),

I wouldn't use this; keep mail on the server or put mails
on your computer where they really belong.

> Correct threading header support (currently it doesn't work correctly,

It does, but you have to save email unformatted and browse and re.
I need to make this mechanism more convenient from a user perspective,
but it is implemented inside.
I had to do this a few years ago because people on one of the linux
lists yelled at me, each of my emails started a new thread
and confused them and I really meant it to be a reply on a current thread
so anyways yes I did some of this work.
It wasn't hard.
I think it's documented somewhere.

> Other stuff ...

Yes, not sure how vital the other stuff is.

> but I wonder if it's time for an edmail program?

We can certainly see the advantages of the separate eb js process,
now that it's done,
and ebmail ebspread etc could make a lot of sense, as long as it's all an integrated system.
Bill Gates found this out a long time ago.
Some web forms call up email client so you can send email,
or even submit form by email,
and from within email you can click on a link and go to your browser,
and (not speaking of windows but of edbrowse)
I can be in the editor and suddenly decide I want to send somebody email
and just put subject at the top and type sm and out it flies.
I really like that.
I really like the integratedness of it all,
but that certainly doesn't preclude modularizing the software more than it is today.

Karl Dahlke

             reply	other threads:[~2015-04-12 16:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-12 16:00 Karl Dahlke [this message]
2015-04-12 19:36 ` Adam Thompson
2015-04-12 20:46   ` [Edbrowse-dev] mailx, plugin commands, mime, new sourcefile Karl Dahlke
2015-04-13 20:16     ` Adam Thompson
2015-04-13 20:33       ` Karl Dahlke
2015-04-14  6:49         ` Adam Thompson
  -- strict thread matches above, loose matches on Subject: below --
2015-04-11 17:19 [Edbrowse-dev] mailx Karl Dahlke
2015-04-11 17:48 ` Chris Brannon
2015-04-12 13:08 ` Adam Thompson

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=20150312120047.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=Edbrowse-dev@lists.the-brannons.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.
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 NNTP newsgroup(s).