unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: xenodasein--- via "Emacs development discussions." <emacs-devel@gnu.org>
To: monnier@iro.umontreal.ca
Cc: emacs-devel@gnu.org
Subject: Re: Collecting completion candidates from multiple files
Date: Thu, 13 Jan 2022 15:47:12 +0100 (CET)	[thread overview]
Message-ID: <MtIu1vk--3-2@tutanota.de> (raw)
In-Reply-To: <jwvtue7vi2t.fsf-monnier+emacs@gnu.org>



>> 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?




  reply	other threads:[~2022-01-13 14:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12 20:48 Collecting completion candidates from multiple files Daniele Nicolodi
2022-01-12 23:19 ` Daniel Martín
2022-01-13  8:53   ` Daniele Nicolodi
2022-01-13 14:19     ` Stefan Monnier
2022-01-13 14:47       ` xenodasein--- via Emacs development discussions. [this message]
2022-01-13 15:14         ` Daniel Martín
2022-01-13 15:32           ` xenodasein--- via Emacs development discussions.
2022-01-13 17:37             ` Stefan Monnier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=MtIu1vk--3-2@tutanota.de \
    --to=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=xenodasein@tutanota.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).