From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: C-x C-f, Tab (in)completion and visiting the wrong, new files Date: Mon, 13 Aug 2007 11:14:12 -0700 Message-ID: References: <64CC15CF-72D0-4765-8D7F-CE0DFBCF96EE@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1187029122 17611 80.91.229.12 (13 Aug 2007 18:18:42 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 13 Aug 2007 18:18:42 +0000 (UTC) Cc: Development of Aquamacs Emacs , Stefan Monnier , emacs- devel To: "David Reitter" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Aug 13 20:18:37 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 1IKeUv-0004Wy-Ek for ged-emacs-devel@m.gmane.org; Mon, 13 Aug 2007 20:18:37 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IKeUu-0001lO-Rr for ged-emacs-devel@m.gmane.org; Mon, 13 Aug 2007 14:18:36 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IKeUr-0001kQ-LH for emacs-devel@gnu.org; Mon, 13 Aug 2007 14:18:33 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IKeUp-0001kE-4d for emacs-devel@gnu.org; Mon, 13 Aug 2007 14:18:32 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IKeUp-0001kB-0s for emacs-devel@gnu.org; Mon, 13 Aug 2007 14:18:31 -0400 Original-Received: from rgminet01.oracle.com ([148.87.113.118]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1IKeUo-0006UJ-M5 for emacs-devel@gnu.org; Mon, 13 Aug 2007 14:18:30 -0400 Original-Received: from agmgw2.us.oracle.com (agmgw2.us.oracle.com [152.68.180.213]) by rgminet01.oracle.com (Switch-3.2.4/Switch-3.1.6) with ESMTP id l7DIF47Z012589; Mon, 13 Aug 2007 12:15:04 -0600 Original-Received: from acsmt350.oracle.com (acsmt350.oracle.com [141.146.40.150]) by agmgw2.us.oracle.com (Switch-3.2.0/Switch-3.2.0) with ESMTP id l7DEDdLb025530; Mon, 13 Aug 2007 12:15:03 -0600 Original-Received: from dhcp-4op11-4op12-west-130-35-178-179.us.oracle.com by acsmt350.oracle.com with ESMTP id 3119756621187028853; Mon, 13 Aug 2007 11:14:13 -0700 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <64CC15CF-72D0-4765-8D7F-CE0DFBCF96EE@gmail.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 Importance: Normal X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE X-Detected-Kernel: Linux 2.4-2.6 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:76471 Archived-At: > > Stefan's suggestion to allow an `only-after-completion' value for > > `find-file-confirm-nonexistent' makes the most sense. I think that > > would make everyone happy. (The default value of > > `find-file-confirm-nonexistent' should remain, nil, however, IMO.) > > Yes, Stefan's suggestion sounds doable. However, I would actually > prefer for it to be the default, as there I see benefits especially > for new users and little problems for others. We disagree about the default value. WDOT? > Secondly, I don't think we should go through the full confirmation > dialog. Instead, just a "ding" sound should be enough, and a second > RET would then act as confirmation. No special opinion on that, but what you say sounds reasonable to me. > Is this really a special case for file name completion, and really > only for `find-file'? Does it not apply to all kinds of completion? The same considerations apply, probably, but it's not clear that a given user would necessarily want the same behavior for all lax completion. Dunno if it might be good to have two such options, one for `read-file-name' and one for `completing-read'. BTW, I assume (and hope) that this `only-after-completion' behavior would apply only for TAB RET, not for TAB followed by some editing followed by RET. That is, it is not just "after completion"; it is "immediately after completion". It's important to be able to use completion to get a value that you then edit and enter with RET. In such a case, it would not make sense for `only-after-completion' to `ding' and require a second RET.