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: Sun, 04 Aug 2019 09:56:13 -0400	[thread overview]
Message-ID: <660b8e7fc0ed45816f2a964871e13009ea574e12.camel@gnu.org> (raw)
In-Reply-To: <E1hu6lp-0006RP-WE@fencepost.gnu.org>

On Sat, 2019-08-03 at 23:01 -0400, Richard Stallman wrote:
>   > And then suggest that for users who have more
>   > complex requirements (for example their code cannot meet these
>   > simplifying assumptions) that they should investigate more
>   > sophisticated setups based on LSP (or whatever they like).
> 
> Instead of giving up, let's design additional simplifying conventions.

Simplifying conventions are only workable if they are used throughout
the codebase.  If you have a one-man development team that's fine but 
convincing a larger team to adjust their coding conventions to support
one editor is generally not feasible.

In any event as Eli mentioned this bug report is probably not the place
to have this discussion: I'm happy to move it to an FSF discussion list
if we want to have a deeper conversation.

And again I don't want to discourage anyone from working on what they
find enjoyable.  If cc-mode can be taught to handle namespaces
reasonably so much the better.  But if not, there are good (free
software) options available for Emacs so that's OK too.






  reply	other threads:[~2019-08-04 13: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
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 [this message]
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

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

  git send-email \
    --in-reply-to=660b8e7fc0ed45816f2a964871e13009ea574e12.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.