From: Morgon Kanter <morgon.kanter@gmail.com>
To: "João Távora" <joaotavora@gmail.com>
Cc: 67609@debbugs.gnu.org
Subject: bug#67609: 29.1; (eglot-inlay-hints-mode -1) behaves surprisingly, does not work in cc-mode hooks
Date: Sun, 3 Dec 2023 14:02:24 -0500 [thread overview]
Message-ID: <CAMGeJwn2nVdv4cS9sHHru+FFaJJLqhUD1qrFD1nULLHqVxe4TA@mail.gmail.com> (raw)
In-Reply-To: <CALDnm51asPT+L+TbAF75uzhGPbMZJ67b_VfM9pANg723LVrNwA@mail.gmail.com>
Hi João,
> Hi. Because you're using 'eglot-ensure' (hint, maybe you
> shoudn't, read the manual in the latest master for why)
> it means that after the eglot-ensure form executes,
> Eglot will not be setup yet, so the following form
> has no effect. You need to replace it with [snip]
I believe there is more to the story than this. I can remove the
eglot-ensure, load eglot so eglot-inlay-hints-mode is a valid symbol,
and replace my config with this:
(defun config:cc-defaults ()
;(setq c-require-final-newline t) ;; lol causes errors in cc-mode
(c-toggle-comment-style 1)
(subword-mode 1)
(diminish 'subword-mode)
(local-set-key (kbd "C-M-S-<backspace>") #'kill-outer-sexp-and-parens)
(eglot-inlay-hints-mode -1))
...and I will receive the same behavior. The eglot-ensure here is a red herring.
To reproduce, visit a C++ buffer in a project, run M-x eglot. Inlay
hints will appear. Kill and reopen the buffer. Inlay hints will
appear.
-- Morgon
next prev parent reply other threads:[~2023-12-03 19:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-03 18:28 bug#67609: 29.1; (eglot-inlay-hints-mode -1) behaves surprisingly, does not work in cc-mode hooks Morgon Kanter
2023-12-03 18:52 ` João Távora
2023-12-03 19:02 ` Morgon Kanter [this message]
2023-12-03 19:23 ` João Távora
2023-12-03 19:37 ` Morgon Kanter
2023-12-03 20:38 ` João Távora
2023-12-16 9:31 ` Eli Zaretskii
2023-12-16 11:55 ` João Távora
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMGeJwn2nVdv4cS9sHHru+FFaJJLqhUD1qrFD1nULLHqVxe4TA@mail.gmail.com \
--to=morgon.kanter@gmail.com \
--cc=67609@debbugs.gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.