From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: "Dmitry Gutov" <dmitry@gutov.dev>, "João Távora" <joaotavora@gmail.com>
Cc: 65518@debbugs.gnu.org
Subject: bug#65518: 30.0.50; [FR Eglot] Completions over all workspace symbols
Date: Mon, 28 Aug 2023 13:10:09 +0200 [thread overview]
Message-ID: <1004e200-6a02-8836-626b-f84e58e9fba3@gmail.com> (raw)
In-Reply-To: <1d4ad1e8-65d9-d8f4-f1a6-df8ec0e16c5c@gutov.dev>
On 28.08.23 02:19, Dmitry Gutov wrote:
> On 25/08/2023 12:22, João Távora wrote:
>> You'll see Eglot sends the widest possible 'query' to the LSP server
>> which returns a limited number of names (clangd caps at exactly 100 by
>> default).
>
> Perhaps it's worth documenting how this value could be increased
> (argument --limit-results=, apparently).
I've tried that now, and it works pretty nicely for me. Apple clang
version 14.0.3 (clang-1403.0.22.14.1)
I now have
export CLANGD_FLAGS="--limit-results=1000 --limit-references=1000"
in my .zshenv, and I'm using exec-path-from-shell in Emacs to get
that setting into Emacs on macOS.
Also, and completely unrelatad, I found that one can add a .clangd,
which made post-processing the compile_commands.json generated by bear
unneccessary.
Put a .clangd in the toplevel directory of the Emacs tree with contents
---
If:
PathMatch: "src/.*\.c"
CompileFlags:
Add: [-include=config.h]
(Not sure if that first line is obligatory. I'm not a YAML user.)
prev parent reply other threads:[~2023-08-28 11:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 6:44 bug#65518: 30.0.50; [FR Eglot] Completions over all workspace symbols Gerd Möllmann
2023-08-25 9:22 ` João Távora
2023-08-26 5:09 ` Gerd Möllmann
2023-08-26 8:57 ` João Távora
2023-08-27 0:14 ` João Távora
2023-08-27 5:56 ` Gerd Möllmann
2023-08-27 6:06 ` João Távora
2023-08-27 6:38 ` Gerd Möllmann
2023-08-28 0:19 ` Dmitry Gutov
2023-08-28 11:10 ` Gerd Möllmann [this message]
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=1004e200-6a02-8836-626b-f84e58e9fba3@gmail.com \
--to=gerd.moellmann@gmail.com \
--cc=65518@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
--cc=joaotavora@gmail.com \
/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).