From: Po Lu <luangruo@yahoo.com>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: EBrowse obsolete?
Date: Thu, 21 Jul 2022 19:44:39 +0800 [thread overview]
Message-ID: <874jza8zbs.fsf@yahoo.com> (raw)
In-Reply-To: <m28romvhx9.fsf@Mini.fritz.box> ("Gerd Möllmann"'s message of "Thu, 21 Jul 2022 13:12:02 +0200")
Gerd Möllmann <gerd.moellmann@gmail.com> writes:
> Okay, I'm not sure I wnat to know details, after searching for a GCC
> language server, finding patches from 2017, and son on.
>
> BTW. I happened to try lsp-mode instead of eglot a week or two ago. It
> worked OOTB with Emacs' sources and clangd, which was already installed
> on my system. The only thing one needs is a tool for extracting a
> compile_commands.json. The first I tried, 'bear', also worked OOTB
> ("make clean; bear -- make" was enough).
>
> No performance problems here, also.
I guess you're using a Mac. Macs have clangd preinstalled and set up
for Mac OS development.
It isn't so easy to use clangd on GNU/Linux. The first thing it does is
to make my two-processor machine very slow. Then I have to struggle
with include paths to make it find stddef.h in the right place.
next prev parent reply other threads:[~2022-07-21 11:44 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 6:16 EBrowse obsolete? Gerd Möllmann
2022-07-21 6:44 ` Akib Azmain Turja
2022-07-21 12:46 ` CEDET obsolete? (was: Re: EBrowse obsolete?) Stefan Kangas
2022-07-21 13:00 ` CEDET obsolete? Po Lu
2022-07-22 10:26 ` Jose E. Marchesi
2022-07-22 13:26 ` Stefan Kangas
2022-07-23 11:44 ` CEDET obsolete? (was: Re: EBrowse obsolete?) Lynn Winebarger
2022-07-21 6:49 ` EBrowse obsolete? Po Lu
2022-07-21 7:26 ` Eli Zaretskii
2022-07-21 7:56 ` Bozhidar Batsov
2022-07-21 12:16 ` Zhiwei Chen
2022-07-21 8:16 ` Po Lu
2022-07-21 11:12 ` Gerd Möllmann
2022-07-21 11:44 ` Po Lu [this message]
2022-07-21 12:21 ` Dmitry Gutov
2022-07-21 12:28 ` Gerd Möllmann
2022-07-21 12:33 ` Akib Azmain Turja
2022-07-21 17:02 ` Yuri Khan
2022-07-21 12:15 ` Eli Zaretskii
2022-07-21 12:19 ` Dmitry Gutov
2022-07-21 12:28 ` Eli Zaretskii
2022-07-21 15:21 ` Stefan Monnier
2022-07-21 16:16 ` Visuwesh
2022-07-21 16:51 ` Stefan Monnier
2022-07-21 17:07 ` Visuwesh
2022-07-21 17:16 ` Jim Porter
2022-07-21 17:39 ` Stefan Monnier
2022-07-21 21:26 ` Jim Porter
2022-07-22 2:01 ` Tim Cross
2022-07-23 10:18 ` Michael Albinus
2022-07-24 23:25 ` Tim Cross
2022-07-22 14:29 ` Brian Cully via Emacs development discussions.
2022-07-22 17:22 ` Jim Porter
2022-07-23 10:35 ` Michael Albinus
2022-07-23 10:28 ` Michael Albinus
2022-07-23 10:13 ` Michael Albinus
2022-07-23 9:57 ` Michael Albinus
2022-07-23 14:36 ` Stefan Monnier
2022-07-23 15:04 ` Michael Albinus
2022-07-23 9:51 ` Michael Albinus
2022-07-22 1:06 ` Po Lu
2022-07-22 4:55 ` Gerd Möllmann
2022-07-22 5:15 ` tomas
2022-07-22 6:52 ` Eli Zaretskii
2022-07-22 1:35 ` Tim Cross
2022-07-21 12:58 ` Gerd Möllmann
2022-07-21 13:04 ` Eli Zaretskii
2022-07-21 13:16 ` Po Lu
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=874jza8zbs.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=eliz@gnu.org \
--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).