From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: Moving files from lisp/gnus/ to lisp/net/? Date: Sun, 11 Nov 2007 14:33:50 -0500 Message-ID: References: <87y7dd2e0f.fsf@mocca.josefsson.org> <54a15d860711060601s2d85f32o5942939270a7e59e@mail.gmail.com> <54a15d860711071646u2c200961y69e7d684c7418a7a@mail.gmail.com> <54a15d860711081633k364caf30r3b75464be8a060fa@mail.gmail.com> <87hcjtfy0s.fsf@broken.deisui.org> Reply-To: rms@gnu.org NNTP-Posting-Host: lo.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: ger.gmane.org 1194809807 18579 80.91.229.12 (11 Nov 2007 19:36:47 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 11 Nov 2007 19:36:47 +0000 (UTC) Cc: simon@josefsson.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Daiki Ueno Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Nov 11 20:36:51 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 1IrIbv-0007hL-K1 for ged-emacs-devel@m.gmane.org; Sun, 11 Nov 2007 20:36:47 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IrIbj-0003QP-Jb for ged-emacs-devel@m.gmane.org; Sun, 11 Nov 2007 14:36:35 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IrIZ7-0002LB-Sx for emacs-devel@gnu.org; Sun, 11 Nov 2007 14:33:53 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IrIZ6-0002KP-4s for emacs-devel@gnu.org; Sun, 11 Nov 2007 14:33:53 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IrIZ5-0002K7-MA for emacs-devel@gnu.org; Sun, 11 Nov 2007 14:33:51 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IrIZ4-00077K-Ta for emacs-devel@gnu.org; Sun, 11 Nov 2007 14:33:51 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.60) (envelope-from ) id 1IrIZ4-0002Bf-AG; Sun, 11 Nov 2007 14:33:50 -0500 In-reply-to: <87hcjtfy0s.fsf@broken.deisui.org> (message from Daiki Ueno on Sun, 11 Nov 2007 09:04:19 +0900) X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) 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:82958 Archived-At: Simon> Regarding naming, possibly `password-read-and-cache' should be removed. Simon> The problem with it is that it enters passwords into the cache without Simon> allowing applications to verify that the password is correct. However, Simon> applications could detect this and use `password-cache-remove', but it Simon> seems less reliable to me. I agree. Forgetting to remove a bad password is less friendly than forgetting to add a good one. Now that you mention it, I agree: it usually doesn't make sense to add the password to the cache when reading it. So I guess we don't really want `password-read-and-cache'. I agree that we should also mark `password-read-and-add' as obsolete. If the only desired operation is to read a password and see if it is in the cache, then I think we should give `read-passwd' an optional KEY argument and make it just check the cache, not add. That won't lead to the previously described code-copying problem, because the cache will not have passwords for the new application unless it also has calls to add to the cache.