From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Daiki Ueno" Newsgroups: gmane.emacs.devel,gmane.emacs.gnus.general Subject: Re: encrypt.el in No Gnus 0.7 Date: Thu, 1 Nov 2007 10:30:54 +0900 Message-ID: <54a15d860710311830s4fa203e3y53fbd6f51496f007@mail.gmail.com> References: <87zly3y4ru.fsf@catnip.gol.com> <87odejy30k.fsf@catnip.gol.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1193880673 23059 80.91.229.12 (1 Nov 2007 01:31:13 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 1 Nov 2007 01:31:13 +0000 (UTC) To: emacs-devel@gnu.org, ding@gnus.org, "Miles Bader" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 01 02:31:15 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1InOtv-0006uv-0D for ged-emacs-devel@m.gmane.org; Thu, 01 Nov 2007 02:31:15 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1InOtl-00044z-3I for ged-emacs-devel@m.gmane.org; Wed, 31 Oct 2007 21:31:05 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1InOth-00043r-9b for emacs-devel@gnu.org; Wed, 31 Oct 2007 21:31:01 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1InOtd-00041r-Rs for emacs-devel@gnu.org; Wed, 31 Oct 2007 21:31:00 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1InOtd-00041i-N4 for emacs-devel@gnu.org; Wed, 31 Oct 2007 21:30:57 -0400 Original-Received: from el-out-1112.google.com ([209.85.162.182]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1InOtd-0007mQ-FD for emacs-devel@gnu.org; Wed, 31 Oct 2007 21:30:57 -0400 Original-Received: by el-out-1112.google.com with SMTP id s27so102621ele for ; Wed, 31 Oct 2007 18:30:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=3o2L/1F5XSxnlpeiN5hQXdMknMid/FxTJ4YOTxi5gK8=; b=kpjYuuZsSeh9mW0Y+2sDwIjoYH6VpGErZs0oHqE16iCFvDWSTJ8+OUDgWvcyoLXJLoCPOgAkKIm6p5g+Qt+3Xzlqm+PEJWmhUFLm4u5RyJ6L3cJh9JtAcYJn4Am1e8qPBfdQRVmuiwKarWQh0LuwKg9D2E1636rCyILHZHv4/cg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=czubovPCXj5pVArD92oY9TipRRlk4KrBRvcz68xZ6GtEoq8+/Q9TUUUQhNeDIVJPN5FrjKXC8AnW0BxSWHegYvUhF7k2AdioGVaafsMlsFRR+op3X8a2e1hM0aJbkGT/4pcl/i3XqJn1HJg21lJq6gZCwrOJY6eJ2FJYSvf+IU4= Original-Received: by 10.142.125.5 with SMTP id x5mr3058wfc.1193880654643; Wed, 31 Oct 2007 18:30:54 -0700 (PDT) Original-Received: by 10.142.213.14 with HTTP; Wed, 31 Oct 2007 18:30:54 -0700 (PDT) In-Reply-To: Content-Disposition: inline X-Google-Sender-Auth: 966a3795dbaa92c7 X-detected-kernel: by monty-python.gnu.org: Linux 2.4-2.6 (Google crawlbot) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:82272 gmane.emacs.gnus.general:65511 Archived-At: 2007/11/1, Ted Zlatanov : > It definitely makes sense to move encrypt.el into Emacs as well then. > My main concern was that it overlaps with all the other *crypt*.el > packages, and I really think that encrypt.el's simplicity and > non-invasiveness justifies its existence. But it requires password.el. > I'm open to suggestions as to the best way to manage it. epa-file.el in EasyPG can also do that. Have you looked at it? I think it is much easier to use since it does not need elisp setup like encrypt-file-alist. Yes, EasyPG is a bit complex and invasive. But IMO sometimes usability should be given priority over simplicity & non-invasiveness. BTW, I just tried encrypt.el and I encountered a few issues. (1) It uses gnus-error to report errors so there is a dependency to gnus-util.el. (2) The instruction says M-x encrypt-file-contents but there is no such function (perhaps is it a typo of encrypt-write-file-contents?). (3) encrypt-find-model does not resolve path names. Regards, -- Daiki Ueno