From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: Moving files from lisp/gnus/ to lisp/net/? Date: Mon, 01 Nov 2004 15:09:55 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <4nekjd9vqk.fsf@lifelogs.com> References: <2366.81.51.30.174.1098020712.squirrel@yxa.extundo.com> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1099339841 12907 80.91.229.6 (1 Nov 2004 20:10:41 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 1 Nov 2004 20:10:41 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 01 21:10:30 2004 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1COiVZ-00053Q-00 for ; Mon, 01 Nov 2004 21:10:30 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1COida-0004k2-C0 for ged-emacs-devel@m.gmane.org; Mon, 01 Nov 2004 15:18:46 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1COidR-0004ji-S9 for emacs-devel@gnu.org; Mon, 01 Nov 2004 15:18:37 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1COidR-0004jH-BT for emacs-devel@gnu.org; Mon, 01 Nov 2004 15:18:37 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1COidR-0004j9-8V for emacs-devel@gnu.org; Mon, 01 Nov 2004 15:18:37 -0500 Original-Received: from [80.91.229.2] (helo=main.gmane.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1COiV7-0008Jh-Fd for emacs-devel@gnu.org; Mon, 01 Nov 2004 15:10:01 -0500 Original-Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1COiV5-00030Q-00 for ; Mon, 01 Nov 2004 21:09:59 +0100 Original-Received: from asimov.bwh.harvard.edu ([134.174.9.63]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 01 Nov 2004 21:09:59 +0100 Original-Received: from tzz by asimov.bwh.harvard.edu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 01 Nov 2004 21:09:59 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-To: emacs-devel@gnu.org Original-Lines: 25 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: asimov.bwh.harvard.edu X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3.50 (gnu/linux) Cancel-Lock: sha1:pBuKvXd3K7e4PpAFEt8Ar0nBGnE= 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: main.gmane.org gmane.emacs.devel:29278 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:29278 On Fri, 29 Oct 2004, jas@extundo.com wrote: > It was added later on, not by me. I suppose he who added it might > argue that it is useful, though. I tend to think that there should > only be one worked out interface. (I'm not saying the current API, > without p-r-a-a is the best interface, only that it would be better > with only one interface.) I added it for the purpose of decrypting a file, which is a one-shot deal. If it fails, it fails - you don't try to reopen the file as you would a network connection, and you don't necessarily know that it failed (for example, the encrypt.el XOR cipher produces garbage with a bad password but otherwise there's no indication that there was an error). The only problem is that the password is then memorized, so if it was bad it will stay around. Either I should add an option to ask y/n if the decryption was OK after the first time a password is entered, or I will give the user a way to clear a bad password. Any other suggestions are welcome. Please note again that we don't necessarily know the decryption failed. Maybe we should not memorize encryption passwords at all? That would be tedious, though, if you encrypt a lot of files with the same cipher... Ted