From: Alan Mackenzie <acm@muc.de>
To: 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: 17 Jul 2019 14:39:49 -0000 [thread overview]
Message-ID: <20190717143949.87668.qmail@mail.muc.de> (raw)
In-Reply-To: <mailman.1463.1563222851.2688.bug-gnu-emacs@gnu.org>
Hello, Ergus.
In article <mailman.1463.1563222851.2688.bug-gnu-emacs@gnu.org> you wrote:
> [-- text/plain, encoding 7bit, charset: us-ascii, 91 lines --]
> --text follows this line--
> In the example code (attachement) imenu does not recognizes the
> functions. So it shows that there are not candidates when there are.
OK. I'll look into this.
> In GNU Emacs 27.0.50 (build 5, x86_64-pc-linux-gnu, GTK+ Version 3.24.10)
> of 2019-07-14 built on Ergus
> Repository revision: 783eca57159065ea575622b74e1446853f31621a
> Repository branch: master
> System Description: Arch Linux
[ .... ]
> Major mode: C++//l
> Minor modes in effect:
> tooltip-mode: t
> global-eldoc-mode: t
> electric-indent-mode: t
> mouse-wheel-mode: t
> tool-bar-mode: t
> menu-bar-mode: t
> file-name-shadow-mode: t
> global-font-lock-mode: t
> font-lock-mode: t
> auto-composition-mode: t
> auto-encryption-mode: t
> auto-compression-mode: t
> line-number-mode: t
> transient-mark-mode: t
> abbrev-mode: t
[ .... ]
> #ifndef _make_local_matrix_hpp_
> #define _make_local_matrix_hpp_
> #include <vector>
> #include <map>
> #include <cassert>
> #include <cstdio>
> #include <fstream>
> namespace miniFE {
> void get_recv_info_task(CSRMatrix *A, size_t id, size_t numboxes
> const size_t *nrows_array,
> size_t Annz, size_t Anrows)
> {
> }
> void get_send_info_task(CSRMatrix *A, size_t id,
> size_t numboxes,
> int *send_length_local)
> {
> }
> void set_send_info_task(CSRMatrix *A_array, size_t id,
> size_t numboxes,
> int nelements_to_send_local,
> int *elements_to_send_local)
> {
> }
> void make_local_matrix(CSRMatrix *A_array, singleton *sing, size_t numboxes)
> {
> }
> }//namespace miniFE
> #endif
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2019-07-17 14:39 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 [this message]
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
[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
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
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=20190717143949.87668.qmail@mail.muc.de \
--to=acm@muc.de \
--cc=36678@debbugs.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).