unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: Corwin Brust <corwin@bru.st>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: A note about clang-format
Date: Tue, 22 Aug 2023 20:07:32 +0100	[thread overview]
Message-ID: <CALDnm53SzAjgruS5yF3gv9Wx3+c2Jh8fu5i4N3xP7mG1wPSzPQ@mail.gmail.com> (raw)
In-Reply-To: <m2ttsqzyx2.fsf@Mini.fritz.box>

[-- Attachment #1: Type: text/plain, Size: 913 bytes --]

On Tue, Aug 22, 2023, 19:59 Gerd Möllmann <gerd.moellmann@gmail.com> wrote:

> João Távora <joaotavora@gmail.com> writes:
>
> > But it can be ignored via 'eglot-ignored-server-capabilities', which see.
>
> Actually, I found that auto-formatting quite nice when I switched from
> lsp-mode to eglot today, so I didn't want to suppress this.  But the
> DEFUNs in Emacs' C code are something from another world.  I don't know
> if any formatter can cope with them.
>
> Might be good to start using this in the Emacs sources, too, if that's
> ok.  The existence of a .clang-format makes me think some users might
> appreciate it.
>

I think we (meaning you) should lobby Eli for compile_commands.json
generation first :)

M-x eglot in Emacs sources still doesn't work oob and there's little reason
for that (well, apart from some understandable llvm aversion, but there are
other servers...).

[-- Attachment #2: Type: text/html, Size: 1478 bytes --]

  reply	other threads:[~2023-08-22 19:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-22 14:55 A note about clang-format Gerd Möllmann
2023-08-22 18:29 ` Corwin Brust
2023-08-22 18:34   ` João Távora
2023-08-22 18:59     ` Gerd Möllmann
2023-08-22 19:07       ` João Távora [this message]
2023-08-22 19:44         ` Gerd Möllmann
2023-08-22 20:13           ` João Távora
2023-08-23  5:58             ` Gerd Möllmann
2023-08-23  2:27         ` Eli Zaretskii
2023-08-22 19:02   ` Gerd Möllmann

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=CALDnm53SzAjgruS5yF3gv9Wx3+c2Jh8fu5i4N3xP7mG1wPSzPQ@mail.gmail.com \
    --to=joaotavora@gmail.com \
    --cc=corwin@bru.st \
    --cc=emacs-devel@gnu.org \
    --cc=gerd.moellmann@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).