all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Smith <psmith@gnu.org>
To: rms@gnu.org
Cc: acm@muc.de, spacibba@aol.com, 36678@debbugs.gnu.org
Subject: bug#36678: 27.0.50; imenu not working in C++ (maybe because of namespace)
Date: Sat, 03 Aug 2019 10:43:21 -0400	[thread overview]
Message-ID: <fa562743615e6f587d45665c7da89a9766a72593.camel@gnu.org> (raw)
In-Reply-To: <E1htjjb-0002eO-Fo@fencepost.gnu.org>

On Fri, 2019-08-02 at 22:25 -0400, Richard Stallman wrote:
>   > 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).
> 
> Using a server to do your ocmputing job is bad for your freedom
> (unless it's your own server).

Sorry, I guess I should have provided more details.  When I say
"server" I mean in the traditional sense, of a background process
running on your local system.  I don't mean "service", as in Internet
service.

LSP stands for "Language Server Protocol" and is a public protocol
(invented and driven by Microsoft, but a public effort).

The goal is to split the work of indexing source code and the work of
editing source code into two parts, and LSP is the protocol between
those two parts.  The protocol is language agnostic, so if you have a
client that speaks LSP, that same client can work for ANY language for
which you have an LSP server.  There are (free) LSP servers available
for most popular languages.

More info here: https://langserver.org/

An Internet service would be quite untenable since the server is used
to index your source code, and virtually no one would be interested in
uploading all of their source code to some third party for indexing.
Plus it's indexing your particular code so it would have to support
uploading every individual developers workspace, and uploading every
change to that workspace, etc.

There are many free software LSP server implementations.  The one I
mentioned, ccls, supports C and C++ and is licensed via Apache 2.0:

https://github.com/MaskRay/ccls

Of course the Emacs client implementations are all free software
(available on ELPA etc.)






  parent reply	other threads:[~2019-08-03 14:43 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fa562743615e6f587d45665c7da89a9766a72593.camel@gnu.org \
    --to=psmith@gnu.org \
    --cc=36678@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=rms@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.