edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Chris Brannon <chris@the-brannons.com>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] imap
Date: Fri, 21 Mar 2014 20:22:03 +0000	[thread overview]
Message-ID: <20140321202203.GP18585@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <87eh1vif20.fsf@mushroom.PK5001Z>

[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]

On Fri, Mar 21, 2014 at 11:26:15AM -0700, Chris Brannon wrote:
> Adam Thompson <arthompson1990@gmail.com> writes:
> 
> > Given how many linux clients support imap (including a very ed-like email
> > client) I'd be very surprised and disapointed if a decent library isn't
> > available for this.
> 
> Do you mean heirloom-mailx (AKA nail)?
> It's quite ed-like, being based on Berkeley mail from the teletype era.
> The IMAP support is fine.  It handles multiple folders and multiple
> accounts.

Yeah that was the one. I admit, being a long-time mutt user,
I've not played with it that much but it looks kind of interesting.

Getting back to edbrowse though, we need to decide how much mail client support we want.
For example do we want to do maildir, mbox etc for local mailboxes as well as imap and pop3 (with their secure equivalents I hope) for remote ones?
What about pgp and the like for signing messages?
Or threads?

I only mention these because, just like with the browser element,
if we start adding things to the mail client, users will, quite rightly,
request more features.
Given the number of things edbrowse already does,
I guess I'm just concerned that it's going to become too big for its own good
by trying to do too many things.

Cheers,
Adam.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2014-03-21 20:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21 13:27 Karl Dahlke
2014-03-21 14:31 ` Chris Brannon
2014-03-21 17:11   ` Adam Thompson
2014-03-21 17:21     ` Adam Thompson
2014-03-21 18:26     ` Chris Brannon
2014-03-21 20:22       ` Adam Thompson [this message]
2014-03-22 10:04 Karl Dahlke
2014-03-22 21:28 ` 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=20140321202203.GP18585@toaster.adamthompson.me.uk \
    --to=arthompson1990@gmail.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=chris@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).