From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id F4236431FAF for ; Wed, 18 Jan 2012 16:48:27 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.7 X-Spam-Level: X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jrzg0L1AZ7bV for ; Wed, 18 Jan 2012 16:48:27 -0800 (PST) Received: from dmz-mailsec-scanner-8.mit.edu (DMZ-MAILSEC-SCANNER-8.MIT.EDU [18.7.68.37]) by olra.theworths.org (Postfix) with ESMTP id 717B2431FAE for ; Wed, 18 Jan 2012 16:48:27 -0800 (PST) X-AuditID: 12074425-b7f4a6d0000008e0-f6-4f17685bf4b9 Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) by dmz-mailsec-scanner-8.mit.edu (Symantec Messaging Gateway) with SMTP id 91.C7.02272.B58671F4; Wed, 18 Jan 2012 19:48:27 -0500 (EST) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id q0J0mQIF015620; Wed, 18 Jan 2012 19:48:26 -0500 Received: from awakening.csail.mit.edu (awakening.csail.mit.edu [18.26.4.91]) (authenticated bits=0) (User authenticated as amdragon@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id q0J0mPS8017989 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 18 Jan 2012 19:48:25 -0500 (EST) Received: from amthrax by awakening.csail.mit.edu with local (Exim 4.77) (envelope-from ) id 1RngAk-0001yX-7R; Wed, 18 Jan 2012 19:48:10 -0500 Date: Wed, 18 Jan 2012 19:48:10 -0500 From: Austin Clements To: Aaron Ecay Subject: Re: [PATCH] v2 [RFC] emacs: merge overhauled `notmuch-cycle-notmuch-buffers' into `notmuch' Message-ID: <20120119004810.GI16740@mit.edu> References: <87r4yza95m.fsf@praet.org> <1326732415-21894-1-git-send-email-pieter@praet.org> <87fwfd8h0i.fsf@praet.org> <87obu19pfo.fsf@praet.org> <87sjjdp1f1.fsf@praet.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrDKsWRmVeSWpSXmKPExsUixCmqrRudIe5v8Pk/p8W05V/YLfbd2cJk cf3mTGaL369vMDuweOx6/pfJY+esu+wez1bdYvbo2HeZNYAlissmJTUnsyy1SN8ugStjW+dc 5oJu7oqJtztYGxi/cnQxcnJICJhInG98wgZhi0lcuLceyObiEBLYxygx7fIWZghnA5CzaymU c5JJYuGWfiYIZwmjxMGJ35hB+lkEVCWafy9nB7HZBDQktu1fzghiiwioSMyeNx/MZhYolrh3 8AJQDQeHsECaxPWPliBhXgEdiYMdV9ghZm5klvh65jk7REJQ4uTMJywQveoSf+ZdYgbpZRaQ llj+jwMiLC/RvHU22AmcAvYSU7+3g70jCrR2ysltbBMYhWchmTQLyaRZCJNmIZm0gJFlFaNs Sm6Vbm5iZk5xarJucXJiXl5qka6FXm5miV5qSukmRlDEsLuo7mCccEjpEKMAB6MSD2+EiLi/ EGtiWXFl7iFGSQ4mJVFe33SgEF9SfkplRmJxRnxRaU5q8SFGCQ5mJRHenSZAOd6UxMqq1KJ8 mJQ0B4uSOK+m1js/IYH0xJLU7NTUgtQimKwGB4fA3SW9GxilWPLy81KVJHj5QRYIFqWmp1ak ZeaUIJQycXCCLOIBWvQapIa3uCAxtzgzHSJ/ilFRSpz3PEhCACSRUZoH1wtLdK8YxYHeEub9 BFLFA0yScN2vgAYzAQ32aBIDGVySiJCSamBsufN6Q+PSBzsP53rxGbx4k6Lo9Zk5j2PlzsN/ QxlWWm2csz1nyZFWgbuWXc6TVbl2ZLjeehRZ1X13fnf5Go1Ph+6UJMpOnLWohXepQX/sqWUv e3PO+Pd+aJowUVpPQmyexdbEGuEl5zdukt330zWmUeiAg+u/u02ZcgJG3Xs27m6Nm67Ze+OX EktxRqKhFnNRcSIAaiXxq08DAAA= Cc: Notmuch Mail , Pieter Praet X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jan 2012 00:48:28 -0000 Quoth Aaron Ecay on Jan 18 at 5:18 pm: > Compile-time dependencies on ‘cl’ are absolutely not a problem. > Virtually every major elisp program depends on cl at compile time. > Runtime dependencies are not allowed in code distributed with emacs > because of RMS’s conservativism[1]. > > Since notmuch isn’t distributed with emacs and has no aspirations to > ever be, the project could decide to require cl at runtime. Many > elisp programs do. (A quick grep through my .emacs.d folder turns up > anything.el and clojure-mode as two large/“mainstream” projects that > do, as well as at least a dozen smaller utility files.) So many emacs > users have cl loaded all the time when they are using emacs. But > unless the project (i.e. us) decides explicitly “runtime cl is OK” (or > perhaps “it is not”), contributors will always go back and forth over > using it. To avoid patch and review churn, we ought to decide which > of these we pick (and I vote for allowing runtime use.) I agree with Aaron. There's no excuse for some of the functionality that can only be found in cl to be missing from core Emacs and it's ridiculous to re-implement it time and again (I count at least five obvious reimplementations of remove-if in code shipped with Emacs). There are a lot of compelling reasons to use cl and I'm not aware of any good technical reasons why notmuch shouldn't.