unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Petteri Hintsanen <petterih@iki.fi>
Cc: Eli Zaretskii <eliz@gnu.org>,
	theo@thornhill.no, casouri@gmail.com, spacibba@aol.com,
	emacs-devel@gnu.org
Subject: Re: c-ts-mode
Date: Fri, 8 Sep 2023 21:27:51 +0100	[thread overview]
Message-ID: <CALDnm50txGeyYg3dPwAMHCV8qVQk0EUN2xaRhvJa2P89dBByAg@mail.gmail.com> (raw)
In-Reply-To: <x2mzg1w4eu9.fsf@iki.fi>

On Fri, Sep 8, 2023 at 8:58 PM Petteri Hintsanen <petterih@iki.fi> wrote:

> It is great that Emacs is able to leverage the power of third party libs
> and tools, but I think this should not come at the expense of built in
> functionality.  Of course the rant above was a rhetoric exaggeration,
> but still it is perhaps something to keep in mind when designing for the
> future.

It was an interesting rant IMO :-)  I very much agree with some points,
such as this last one about keeping a clean Emacs functional (which
is also why I like having things in core).  I haven't made LSP-mandated
syntax highlighting a priority for Eglot precisely because Emacs does it
quite well already.

The point I definitely don't agree with is about the "editing experience".
Editing and comprehension of complex C++ code for example is hugely
augmented by LSP (not necessarily clangd).  These tools are here to
stay hopefully.  I can't go back to the days of cscope and grep
(as for CEDET, it never worked at all for me beyond toy tricks).

Other than that, I can see your point about clangd as a gateway
to external tools that Emacs already does very reasonably well, such
as formatting code.  But the reality is not everyone in the world
uses Emacs, and you have to work with them and their code.  Even
different Emacs users will have different C/C++ styles.

> [*] e.g. clangd eats regularly gigabytes of memory, has tons of
> dependencies, and needs tunings for the build and sysroot and whatnot

I built clangd from source the other day, didn't notice that
many dependencies (just LLVM which is pretty big I guess).  By the
way building from source is a sometimes a way to bypass "admin
rights" bothers.  I didn't install clang-format or clang-tidy
separately, they are already included.

As for huge size, you get what you pay for, IMO.  I think you can
tweak it down to just a code analyzer (but analyzing lots of code
code accurately takes a lot of resources yes -- look I didn't
invent templates ;-) ).

João



  reply	other threads:[~2023-09-08 20:27 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <r6t7xfcchagyl72ltdrcavncbpvba7badcoh4yimleoynmzfvb.ref@elkspm3vozuv>
2023-08-30 23:52 ` c-ts-mode Ergus
2023-09-01  4:14   ` c-ts-mode Yuan Fu
2023-09-07  9:25     ` c-ts-mode João Távora
2023-09-07  9:37       ` c-ts-mode Eli Zaretskii
2023-09-07 15:58         ` c-ts-mode João Távora
2023-09-07 17:10           ` c-ts-mode Eli Zaretskii
2023-09-07 17:53             ` c-ts-mode João Távora
2023-09-07 18:13               ` c-ts-mode Eli Zaretskii
2023-09-07 18:23                 ` c-ts-mode João Távora
2023-09-07 18:32                   ` c-ts-mode Eli Zaretskii
2023-09-07 22:01                     ` c-ts-mode João Távora
2023-09-08  6:14                       ` c-ts-mode Eli Zaretskii
2023-09-08  7:25                         ` c-ts-mode João Távora
2023-09-08 11:25                           ` c-ts-mode Eli Zaretskii
2023-09-08 12:38                             ` c-ts-mode João Távora
2023-09-08 13:11                               ` c-ts-mode Eli Zaretskii
2023-09-08 13:32                                 ` c-ts-mode Eli Zaretskii
2023-09-08 15:15                                   ` c-ts-mode João Távora
2023-09-08 15:34                                     ` c-ts-mode Eli Zaretskii
2023-09-08 15:56                                       ` c-ts-mode João Távora
2023-09-08 18:23                                         ` c-ts-mode Eli Zaretskii
2023-09-08 18:30                                           ` c-ts-mode João Távora
2023-09-08 18:54                                             ` c-ts-mode Eli Zaretskii
2023-09-08 19:42                                               ` c-ts-mode João Távora
2023-09-09  6:09                                                 ` c-ts-mode Eli Zaretskii
2023-09-08 19:58                               ` c-ts-mode Petteri Hintsanen
2023-09-08 20:27                                 ` João Távora [this message]
2023-09-09  6:19                                 ` c-ts-mode Eli Zaretskii
2023-09-13 16:15                                   ` c-ts-mode Petteri Hintsanen
2023-09-12  0:34                             ` c-ts-mode Yuan Fu
2023-09-12  7:45                               ` c-ts-mode João Távora
2023-09-12  8:00                                 ` c-ts-mode Po Lu
2023-09-12  9:51                                   ` c-ts-mode 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

  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=CALDnm50txGeyYg3dPwAMHCV8qVQk0EUN2xaRhvJa2P89dBByAg@mail.gmail.com \
    --to=joaotavora@gmail.com \
    --cc=casouri@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=petterih@iki.fi \
    --cc=spacibba@aol.com \
    --cc=theo@thornhill.no \
    /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).