From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: [Emacs-diffs] master 55ec674: * lisp/multifile.el: New file, extracted from etags.el Date: Thu, 27 Dec 2018 09:39:27 -0500 Message-ID: References: <20180922154639.23195.66360@vcs0.savannah.gnu.org> <20180922154640.9D58220310@vcs0.savannah.gnu.org> <54108dbc-9d12-06ff-3f1d-151118e9b234@yandex.ru> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1545922033 18272 195.159.176.226 (27 Dec 2018 14:47:13 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 27 Dec 2018 14:47:13 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Dec 27 15:47:09 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gcWwG-0004fN-Bl for ged-emacs-devel@m.gmane.org; Thu, 27 Dec 2018 15:47:08 +0100 Original-Received: from localhost ([127.0.0.1]:53396 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gcWyN-00014H-3t for ged-emacs-devel@m.gmane.org; Thu, 27 Dec 2018 09:49:19 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:52757) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gcWow-0003nd-Lr for emacs-devel@gnu.org; Thu, 27 Dec 2018 09:39:35 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gcWos-0007sn-N2 for emacs-devel@gnu.org; Thu, 27 Dec 2018 09:39:34 -0500 Original-Received: from chene.dit.umontreal.ca ([132.204.246.20]:46000) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gcWos-0007rn-IJ for emacs-devel@gnu.org; Thu, 27 Dec 2018 09:39:30 -0500 Original-Received: from pastel.home (lechon.iro.umontreal.ca [132.204.27.242]) by chene.dit.umontreal.ca (8.14.7/8.14.1) with ESMTP id wBREdSNC000643; Thu, 27 Dec 2018 09:39:28 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id C08826A9C6; Thu, 27 Dec 2018 09:39:27 -0500 (EST) In-Reply-To: <54108dbc-9d12-06ff-3f1d-151118e9b234@yandex.ru> (Dmitry Gutov's message of "Thu, 27 Dec 2018 03:49:26 +0200") X-NAI-Spam-Flag: NO X-NAI-Spam-Threshold: 5 X-NAI-Spam-Score: 0 X-NAI-Spam-Rules: 2 Rules triggered EDT_SA_DN_PASS=0, RV6448=0 X-NAI-Spam-Version: 2.3.0.9418 : core <6448> : inlines <6990> : streams <1808348> : uri <2770816> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 132.204.246.20 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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" Xref: news.gmane.org gmane.emacs.devel:231999 Archived-At: >> Not sure what you mean by "keep them in sync". > Making sure to implement them in a compatible fashion. My point is, it's > probably better to leave just one if the other can (almost?) always be > efficiently implemented in terms of it. Right. But I'm not sure which one should be the "canonical" one. Currently, the "canonical" one is the completion-table, and the files-list is defined based on it (while it's current definition only handles flat completion, that could be improved). > I wonder if we could efficiently implement project-find-regexp on top of > a sequence like that, i.e. pipe to Grep with little overhead. I can't see any reason why not. > And by streams you mean stream.el in ELPA, right? Indeed. Also known as lazy lists. >> I think TRT is to take the above common-prefix-directory, add it to the >> prompt, and remove it from each completion candidate: this will keep >> substring completion working correctly (and working even better since >> it won't uselessly find matches in the common prefix) and will also >> clarify where the search takes place. > > Makes sense. Should work as long as '/' is in > completion-pcm-word-delimiters. > > But this approach also needs the completion table to be flat, right? Not necessarily: we could accumulate the prefix as long as it's the sole completion. Stefan