From owner-freebsd-hackers Thu Jun 20 12:27:40 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from tesla.distributel.net (nat.MTL.distributel.NET [66.38.181.24]) by hub.freebsd.org (Postfix) with ESMTP id 41F5637B411 for ; Thu, 20 Jun 2002 12:27:13 -0700 (PDT) Received: (from bmilekic@localhost) by tesla.distributel.net (8.11.6/8.11.6) id g5KJOs523647 for freebsd-hackers@freebsd.org; Thu, 20 Jun 2002 15:24:54 -0400 (EDT) (envelope-from bmilekic@unixdaemons.com) Date: Thu, 20 Jun 2002 15:24:54 -0400 From: Bosko Milekic To: freebsd-hackers@freebsd.org Subject: Some small projects for mutt(1) Message-ID: <20020620152454.A23499@unixdaemons.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Two ideas have come up recently to extend the features of the mutt(1) Email client. I'm not one who has hacked on mutt, nor who really intends to (if I can avoid it, I will), so hence the reason for this post. So this post is directed at those people who have some extra time on their hands and are looking to make some sort of contribution to FreeBSD, but aren't prepared (or don't want to) muck in the kernel source. 1) The first feature is a persistent-thread-delete. This idea was given by Jonathan Mini at Usenix. I'm not aware of any client that supports this right now, but such a client may exist (in any case, it would be cool if mutt did it). What this does is pretty straightforward: I see a thread with subject "foo." I don't like it. I really don't like it. I hit a key combination such as, I don't know, CTRL+B (or something not bound yet), and not only is the entire thread instantly marked for deletion, but a carefully crafted rule is also dropped into a sh*tlist file (that can be handled by procmail?) which will ensure that all _future_ mailings that are in response to said thread will immediately be marked for deletion, or merely filtered. Hence, "persistent thread suppression/deletion." 2) An optional feature that would, when you hit 'y' to send that Email off, attempt to roughly analyze your message and present an "Are you sure you want to send this Email, it contains potentially inflammatory content?" confirmation request, based on the content of the message. I believe Eudora Lite has this sort of thing where if you key in something that looks offensive/like a flame, it will generate a popup with a warning like "Warning: this Email may offend the average reader, are you sure you went to send it?" I think this would help some of us out with controlling our tempers. If you want to make this extra cool, you could have a system where Email can be classified as "INFLAMMATORY" and "REALLY INFLAMMATORY," and the "REALLY INFLAMMATORY" Email would not only generate the warning, but would also set off a timer and only blast the Email away in N minutes, unless it is cancelled prior to the blastoff time. Anyway, I really think that (1) would be extremely useful. As for (2), well, it's kind of funny. :-) Cheers, -- Bosko Milekic bmilekic@unixdaemons.com bmilekic@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message