From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: make project--find-in-file generic, add interactive filename to project-find-file Date: Fri, 29 Jan 2016 09:03:55 -0500 Message-ID: References: <86wpqu8qf9.fsf@stephe-leake.org> <56A9DDA8.9080504@yandex.ru> <86si1i813n.fsf@stephe-leake.org> <56A9EF4B.7020406@yandex.ru> <56AA6CCA.10103@yandex.ru> <56AAC8E7.8090601@yandex.ru> <56AAE666.7010206@yandex.ru> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1454076330 15503 80.91.229.3 (29 Jan 2016 14:05:30 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 29 Jan 2016 14:05:30 +0000 (UTC) Cc: Stephen Leake , emacs-devel To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 29 15:05:22 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aP9fm-0003nK-DZ for ged-emacs-devel@m.gmane.org; Fri, 29 Jan 2016 15:05:14 +0100 Original-Received: from localhost ([::1]:34416 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aP9fl-0006VQ-Md for ged-emacs-devel@m.gmane.org; Fri, 29 Jan 2016 09:05:13 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45542) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aP9ec-0005CB-3l for emacs-devel@gnu.org; Fri, 29 Jan 2016 09:04:07 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aP9eX-0004gT-3h for emacs-devel@gnu.org; Fri, 29 Jan 2016 09:04:02 -0500 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:18453) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aP9eW-0004gM-Vs for emacs-devel@gnu.org; Fri, 29 Jan 2016 09:03:57 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0AyFgA731xV/3+SCkxcgxCEAoVVu0CHSwQCAoE8OxIBAQEBAQEBgQpBBYNdAQEDAVYjBQsLDiYSFBgNJIg3CM8jAQEBAQYBAQEBHos6hQUHhC0FjDCSZ4ZpjT+BRSOCChwVgVsggngBAQE X-IPAS-Result: A0AyFgA731xV/3+SCkxcgxCEAoVVu0CHSwQCAoE8OxIBAQEBAQEBgQpBBYNdAQEDAVYjBQsLDiYSFBgNJIg3CM8jAQEBAQYBAQEBHos6hQUHhC0FjDCSZ4ZpjT+BRSOCChwVgVsggngBAQE X-IronPort-AV: E=Sophos;i="5.13,465,1427774400"; d="scan'208";a="191863140" Original-Received: from 76-10-146-127.dsl.teksavvy.com (HELO pastel.home) ([76.10.146.127]) by ironport2-out.teksavvy.com with ESMTP; 29 Jan 2016 09:03:55 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id 2D846600A8; Fri, 29 Jan 2016 09:03:55 -0500 (EST) In-Reply-To: <56AAE666.7010206@yandex.ru> (Dmitry Gutov's message of "Fri, 29 Jan 2016 07:11:18 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.181 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:198991 Archived-At: >> I think you missed in the text you quoted above the fact that I said >> "allow users to replace this function". I do not intend this alternative >> behavior to be the default. > Maybe I missed it, yes. You said "introduce new functions", not "new > customization points", though. The main purpose of the new functions would be to improve the handing of DEFAULT and encourage coders to use it. IIUC the way we handle default didn't exist when completing-read was first defined, which is why it's hidden so far down the list of optional arguments. It so happens that it would also provide good customization points, yes. > But can't we already do that with completing-read-function? Its contract > imposes no conditions on the presentation. We can, yes, but completing-read will receive a prompt string which sometimes includes the default and would then have to try and find it to remove it from there (if the customized UI wants to put default as initial input instead). This can't be done cleanly and reliably currently. [ The same problem affects minibuffer-electric-default-mode, of course. ] Stefan