From: Alan Mackenzie <acm@muc.de>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Angelo Graziosi <angelo.g0@libero.it>, emacs-devel@gnu.org
Subject: Re: Error in C++ mode with Emacs 27.0.90
Date: Sun, 29 Mar 2020 11:50:56 +0000 [thread overview]
Message-ID: <20200329115056.GA5469@ACM> (raw)
In-Reply-To: <3d764ea5-0d60-1070-0d8a-f9820d013033@yandex.ru>
Hello, Dmitry.
On Sun, Mar 29, 2020 at 01:18:13 +0200, Dmitry Gutov wrote:
> Hi Alan,
> On 28.03.2020 22:10, Alan Mackenzie wrote:
> > I think the following patch fixes the trouble. Please try it out and
> > report on this list how well it works
> I wonder if we could rewrite the related code such as not to depend on
> whether a list has one element or several. That sounds ugly. Though the
> change would likely take a fair amount of rework.
It seems unlikely that we can get a nested list (in imenu--index-alist)
with only one element. I have tried creating a C++ buffer with 25
functions in it. This gives a simple list of 25 elements. With 26
functions, I get a nested alist with two elements.
However, in an emacs-lisp-mode buffer, we get things like "Variables"
and "*Rescan*", but I've not yet succeeded in causing a nested list with
just one element. I'm not convinced enough that it couldn't happen,
though.
The latter part of the function looks like this (before my patch):
(let* ((menu (imenu--split-menu index-alist
(buffer-name)))
(menu1 (imenu--create-keymap (car menu)
========> (cdr (if (< 1 (length (cdr menu)))
menu
(car (cdr menu))))
'imenu--menubar-select)))
(setcdr imenu--menubar-keymap (cdr menu1)))))))
That `if' form has been there since imenu-update-menubar was first
written by Karl Heuer in 1997 (commit 0a8e8bc63e3). Presumably, it
really was needed back then.
> In any case, imenu--create-keymap is also called from imenu--mouse-menu,
> which probably needs the same kind of fix.
Possibly. I've not managed to create the same error in
imenu--mouse-menu, but perhaps it could do with the same correction,
just in case. What do you think?
Incidentally, that patch from last night was a bit untidy. I think it
needs cleaning up a bit.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2020-03-29 11:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 20:50 Error in C++ mode with Emacs 27.0.90 Angelo Graziosi
2020-03-27 15:56 ` Angelo Graziosi
2020-03-28 15:19 ` Alan Mackenzie
2020-03-28 17:34 ` Angelo Graziosi
2020-03-28 20:10 ` Alan Mackenzie
2020-03-28 22:31 ` Angelo Graziosi
2020-03-29 11:58 ` Alan Mackenzie
2020-03-29 13:56 ` Eli Zaretskii
2020-03-30 17:49 ` Alan Mackenzie
2020-03-30 18:36 ` Eli Zaretskii
2020-03-30 19:46 ` Alan Mackenzie
2020-03-28 23:18 ` Dmitry Gutov
2020-03-29 11:50 ` Alan Mackenzie [this message]
2020-03-29 22:32 ` Dmitry Gutov
2020-04-04 11:46 ` Alan Mackenzie
2020-04-04 12:52 ` Dmitry Gutov
2023-02-18 17:52 ` Alan Mackenzie
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=20200329115056.GA5469@ACM \
--to=acm@muc.de \
--cc=angelo.g0@libero.it \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
/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).