From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (75-164-228-9.ptld.qwest.net [75.164.228.9]) by hurricane.the-brannons.com (Postfix) with ESMTPSA id DBCD67ABE3 for ; Sat, 11 Apr 2015 10:49:25 -0700 (PDT) From: Chris Brannon To: Edbrowse-dev@lists.the-brannons.com References: <20150311131950.eklhad@comcast.net> Date: Sat, 11 Apr 2015 10:48:30 -0700 In-Reply-To: <20150311131950.eklhad@comcast.net> (Karl Dahlke's message of "Sat, 11 Apr 2015 13:19:50 -0400") Message-ID: <87wq1i8sk1.fsf@mushroom.localdomain> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Edbrowse-dev] mailx X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Apr 2015 17:49:26 -0000 Karl Dahlke writes: > but I would need to know where you get all this cool information about > curl development. It's probably a thick manual, hopefully with examples. Actually no. Much of the library is documented with manpages, and they are generally quite good. But the POP and IMAP stuff isn't so well-documented. There's some example source code, and that's about it. The problem with IMAP support in curl is that we have to manually parse a lot of responses that we get, for instance the response to a "list folders" or "list messages" command. We don't get the data in a form we can use directly. But I wonder if we couldn't borrow code from mailx. The version that supports IMAP is called "heirloom-mailx", formerly known as "nail", and it is licensed under a permissive BSD license. So it'd be fine to incorporate code from that project. -- Chris