From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <1c9f72654aa8dc055ee1c4b8319ea803@plan9.escet.urjc.es> From: "Fco. J. Ballesteros" Date: Fri, 1 Oct 2004 16:42:07 +0200 To: 9fans@cse.psu.edu Subject: Re: [9fans] acme mail "feature" In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-pwxpavezunbxkshakdpvmsnjov" Topicbox-Message-UUID: eb4b8f68-eacd-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-pwxpavezunbxkshakdpvmsnjov Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit It's the user interface that I cannot imagine. Otherwise, placing a `read' mark in the mail should not be hard. Either a new header or just in-memory while in upas/fs. But, how to handle it properly in /acme/mail/Mail ? Perhaps showing read messages after non-read ones? --upas-pwxpavezunbxkshakdpvmsnjov Content-Type: message/rfc822 Content-Disposition: inline X-Leches: 0 Received: from mail.cse.psu.edu ([130.203.4.6]) by aquamar; Fri Oct 1 16:40:08 MDT 2004 Received: from psuvax1.cse.psu.edu (localhost [127.0.0.1]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 0E2AD183B0 for ; Fri, 1 Oct 2004 10:40:03 -0400 (EDT) X-Original-To: 9fans@cse.psu.edu Delivered-To: 9fans@cse.psu.edu Received: from localhost (localhost [127.0.0.1]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 8B87A17743 for <9fans@cse.psu.edu>; Fri, 1 Oct 2004 10:39:56 -0400 (EDT) Received: from mail.cse.psu.edu ([127.0.0.1]) by localhost (psuvax1 [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 02628-01-43 for <9fans@cse.psu.edu>; Fri, 1 Oct 2004 10:39:55 -0400 (EDT) Received: from smtp.vitanuova.com (unknown [213.146.155.10]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id C4A641748D for <9fans@cse.psu.edu>; Fri, 1 Oct 2004 10:39:54 -0400 (EDT) Message-ID: To: 9fans@cse.psu.edu Subject: Re: [9fans] acme mail "feature" Date: Fri, 1 Oct 2004 15:45:55 +0100 From: rog@vitanuova.com In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: 9fans-bounces+nemo=lsub.org@cse.psu.edu Errors-To: 9fans-bounces+nemo=lsub.org@cse.psu.edu > How hard would it be to add a new command "Read" or "MarkRead" similar to > "Delmesg" that just marks the mail as (read)-? this facility would need to be added to upas/fs - that would probably be the main difficulty. of course, you'd have to change the mailbox interface too, and work out where you were going to store the extra data, and make sure that it couldn't become inconsistent. and given that upas/fs can look at different kinds of mailbox, it might not be possible for some mailbox kinds (e.g. pop3). basically it's not trivial, which is probably why no-one has put in the necessary comprehension and implementation effort, given that most people have higher priority items on their lists... --upas-pwxpavezunbxkshakdpvmsnjov--