unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Smith <psmith@gnu.org>
To: Alan Mackenzie <acm@muc.de>, Ergus <spacibba@aol.com>
Cc: 36678@debbugs.gnu.org
Subject: bug#36678: 27.0.50; imenu not working in C++ (maybe because of namespace)
Date: Fri, 02 Aug 2019 15:56:59 -0400	[thread overview]
Message-ID: <dba7a41398e9fe42d5f3869c1c1f85c407e88aa6.camel@gnu.org> (raw)
In-Reply-To: <20190802193315.GC11966@ACM>

I certainly don't want to discourage anyone from pursuing new features
and capabilities if they want to.

However, my personal opinion is that it's likely not the most
productive use of time.  IMHO cc-mode should continue to focus on
formatting (which is clearly no small task, but which it's very good
at!) and not attempt to also get involved with indexing.

The future (again IMO) for indexing and code introspection is in LSP:
there are very good LSP servers for C++ that are free (I use ccls
personally) and there are also very good LSP clients for Emacs (I use
lsp-mode).  And of course there are LSP servers for many languages
which can all be used with the same LSP client.  Since the servers are
external (ccls is based on clang) they are very fast and can do much,
MUCH more than imenu-type indexing.  I honestly can't imagine working
on a larger codebase without it, anymore.

I don't personally use imenu but a quick search shows that there are
integrations of imenu and lsp-mode available.

Just my $0.02!!







  parent reply	other threads:[~2019-08-02 19:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-15 20:33 bug#36678: 27.0.50; imenu not working in C++ (maybe because of namespace) Ergus
     [not found] ` <mailman.1463.1563222851.2688.bug-gnu-emacs@gnu.org>
2019-07-17 14:39   ` Alan Mackenzie
2019-07-17 16:34   ` Alan Mackenzie
2019-07-31 15:56     ` Ergus
2019-08-02 19:33       ` Alan Mackenzie
     [not found]       ` <20190802193315.GC11966@ACM>
2019-08-02 19:56         ` Paul Smith [this message]
2019-08-03  2:25           ` Richard Stallman
2019-08-03 11:27           ` Alan Mackenzie
2019-08-03 15:09             ` Paul Smith
2019-08-04  3:01               ` Richard Stallman
2019-08-04 13:56                 ` Paul Smith
2019-08-05  2:25                   ` Richard Stallman
2019-08-04  2:56             ` Richard Stallman
2019-08-04  8:51               ` Alan Mackenzie
2019-08-05  2:26                 ` Richard Stallman
     [not found]           ` <E1htjjb-0002eO-Fo@fencepost.gnu.org>
2019-08-03  7:20             ` Eli Zaretskii
2019-08-03 14:43             ` Paul Smith
2019-08-05  2:24               ` Richard Stallman

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=dba7a41398e9fe42d5f3869c1c1f85c407e88aa6.camel@gnu.org \
    --to=psmith@gnu.org \
    --cc=36678@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=spacibba@aol.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).