unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Joel Reicher <joel.reicher@gmail.com>
To: Hunter Jozwiak <hunter.t.joz@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Working with Eglot and QMK
Date: Sun, 28 Jul 2024 16:32:07 +1000	[thread overview]
Message-ID: <86r0bexc0o.fsf@gmail.com> (raw)
In-Reply-To: <87ikws9df9.fsf@gmail.com> (Hunter Jozwiak's message of "Fri, 26 Jul 2024 15:11:06 -0400")

Hunter Jozwiak <hunter.t.joz@gmail.com> writes:

> What is the procedure for getting Eglot to work with my QMK 
> fork? I was trying to set it up last night, but not really sure 
> where to begin. To test, I opened up my keymap for the ZSA 
> Moonlander I got recently and ran eglot, which seemed to open 
> normally. Then, I went over to the layouts themselves and put 
> point over the LAYOUT macro usage, where I then ran 
> xref-find-definitions and got   nothing defined for that 
> identifier. A did a bit of digging and discovered the 
> generate-compilation-database command for making a 
> compile-commands.json which is supposed to fix these issues, but 
> eglot doesn't seem to be using it after I generated it and 
> restarted the LSP. Is there another step to get things working 
> with clangd?

I might be missing something, but I can't tell what language you 
are expecting support for here.

The clangd language server is for C/C++. Are you saying your 
keymap is written in one of those languages?

Cheers,

        - Joel



  reply	other threads:[~2024-07-28  6:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-26 19:11 Working with Eglot and QMK Hunter Jozwiak
2024-07-28  6:32 ` Joel Reicher [this message]
2024-07-28  8:35   ` Yuri Khan
2024-07-28 13:55 ` Arsen Arsenović

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=86r0bexc0o.fsf@gmail.com \
    --to=joel.reicher@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=hunter.t.joz@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.
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).