From: Alan Mackenzie <acm@muc.de>
To: Paul Smith <psmith@gnu.org>
Cc: Ergus <spacibba@aol.com>, 36678@debbugs.gnu.org
Subject: bug#36678: 27.0.50; imenu not working in C++ (maybe because of namespace)
Date: Sat, 3 Aug 2019 11:27:34 +0000 [thread overview]
Message-ID: <20190803112734.GA5573@ACM> (raw)
In-Reply-To: <dba7a41398e9fe42d5f3869c1c1f85c407e88aa6.camel@gnu.org>
Hello, Paul.
On Fri, Aug 02, 2019 at 15:56:59 -0400, Paul Smith wrote:
> 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.
CC Mode has had imenu type indexing right from its inception. What is
changing is the increasing complexity of function definitions, in
particular, the slow demise of the convention of function names being in
column zero.
> The future (again IMO) for indexing and code introspection is in LSP:
> there are very good LSP servers for C++ that are free ....
Free as in speech (not beer)? (Just checking.)
> .... (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 ....
External to what? External to Emacs, or external to the machine running
Emacs? If the latter, that would restrict full Emacs functionality to
networked machines, which would be a big negative, possibly a decisive
one.
> .... (ccls is based on clang) ....
This makes it controversial, since clang isn't free software in the
copyleft sense of the term.
> .... they are very fast and can do much, MUCH more than imenu-type
> indexing.
Could you please give some idea of what you mean by "much more"?
> I honestly can't imagine working on a larger codebase without it,
> anymore.
Does the server you're using run on your own machine? (I'm guessing
yes.)
> 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!!
Thanks!
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2019-08-03 11:27 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
2019-08-03 2:25 ` Richard Stallman
2019-08-03 11:27 ` Alan Mackenzie [this message]
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=20190803112734.GA5573@ACM \
--to=acm@muc.de \
--cc=36678@debbugs.gnu.org \
--cc=psmith@gnu.org \
--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).