unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: EBrowse obsolete?
Date: Thu, 21 Jul 2022 16:04:53 +0300	[thread overview]
Message-ID: <83sfmumxai.fsf@gnu.org> (raw)
In-Reply-To: <m2y1wmaahm.fsf@Mini.fritz.box> (message from Gerd Möllmann on Thu, 21 Jul 2022 14:58:13 +0200)

> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: emacs-devel@gnu.org
> Date: Thu, 21 Jul 2022 14:58:13 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Sheer luck, AFAIU.  I've seen many complaints about that (JSON
> > deserialization being the main issue, but not the only one), and the
> > need to install clangd is frowned upon by GNU.  Using LSP via the
> > network solves that part, but it's slower, AFAIU.
> 
> Let the Gnu frown.
> 
> Every language server for C/C++ I could find so far is based on Clang.
> I'd be grateful for pointers to a language server for C/C++ that's based
> on GCC.

This is a tangent.  No one expects a tool like Ebrowse to compete with
language servers.  OTOH, for such a simple job, a language server is
not really needed.

We _are_ working on getting a client for language servers into Emacs
(we decided to bring Eglot into core), it just takes time (patches are
welcome, btw).  But that's a much larger job, and will enable many
more features, than a tool for browsing C++ code.



  reply	other threads:[~2022-07-21 13:04 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
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 [this message]
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=83sfmumxai.fsf@gnu.org \
    --to=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).