From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: xenodasein--- via "Emacs development discussions." Newsgroups: gmane.emacs.devel Subject: Re: Collecting completion candidates from multiple files Date: Thu, 13 Jan 2022 15:47:12 +0100 (CET) Message-ID: References: <5330eba5-a863-3061-250b-850a46c042fd@grinta.net> <5fef94c1-c05e-4cb3-6022-0ba8ca86698d@grinta.net> Reply-To: xenodasein@tutanota.de Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="34530"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: monnier@iro.umontreal.ca Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Jan 13 15:51:48 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n81S5-0008k3-6g for ged-emacs-devel@m.gmane-mx.org; Thu, 13 Jan 2022 15:51:45 +0100 Original-Received: from localhost ([::1]:50352 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n81S3-0000E9-Kn for ged-emacs-devel@m.gmane-mx.org; Thu, 13 Jan 2022 09:51:43 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:43928) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n81Nm-0005je-G8 for emacs-devel@gnu.org; Thu, 13 Jan 2022 09:47:18 -0500 Original-Received: from w4.tutanota.de ([81.3.6.165]:49390) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n81Nk-0001ZL-Or for emacs-devel@gnu.org; Thu, 13 Jan 2022 09:47:18 -0500 Original-Received: from w3.tutanota.de (unknown [192.168.1.164]) by w4.tutanota.de (Postfix) with ESMTP id CA97F106030B; Thu, 13 Jan 2022 14:47:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1642085232; s=s1; d=tutanota.de; h=From:From:To:To:Subject:Subject:Content-Description:Content-ID:Content-Type:Content-Type:Content-Transfer-Encoding:Content-Transfer-Encoding:Cc:Cc:Date:Date:In-Reply-To:In-Reply-To:MIME-Version:MIME-Version:Message-ID:Message-ID:Reply-To:References:References:Sender; bh=P3DEtp5oSlLa6Lx98hrNWC0Uz3u4K9lZSByxL9MeZ9I=; b=fWfI1ul4vIcoWgnICA7rhQrt1bl2OQRflvJufGuaiQRmQSLiUdV3kTaZaJcFfmw/ XC4m8eLdFqFQ3xinQ2bERHBM5tTWEzyw6DmWXrSFJIY9LNjW0lfyv1aPTjKFVwQR62R 4lp1x7fiLDGL5cZNf1isL4P9/UA1U9audAW0v7NJMGkEzz5Hh1NV7TSFdkLtVfdp+TO VQXSLvww1RSgzIPZgX/4t1ooZW3xxtUj5nxBenxz74+sJXfAHnQQzPLskoWidSJXot6 UYLtzwl6fkU2FqPhMlHaWym/7dHH5BehGcCOCZ6bSjTCe2o4uHddLrsjluYsc4ZFDVJ aGBs6G8QaA== In-Reply-To: Received-SPF: pass client-ip=81.3.6.165; envelope-from=xenodasein@tutanota.de; helo=w4.tutanota.de X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:284717 Archived-At: >> What I'm inquiring about is how to implement the collection of >> completion candidates from multiple buffers. >> > > It's a rather vague question. Usually completion data either comes from > Emacs itself (e.g. lists of commands, or elements of a hash-table, ...), > or from a buffer, or from external info (e.g. files or subprocesses) but > rarely from several buffers. This said, I'm not sure what kind of > difficulty you're facing nor what kind of help you expect to find from > other examples. It'd likely depend a lot on what the actual collection > work looks like. > > If you're thinking of completion data along the lines of `imenu` but not > limited to the current buffer/file, then I suspect you're not looking > for "multiple buffers" but "multiple files", in which case examples may > be Eglot and CEDET? > > > Stefan > I wondered about this also; is there built-in completion functionality that can collect all words or symbols from existing buffers of the same mode, or all existing buffers?