From: Casey Banner <kcbanner@gmail.com>
To: "João Távora" <joaotavora@gmail.com>
Cc: 62719-done@debbugs.gnu.org
Subject: bug#62719: 30.0.50; Eglot: `consult-imenu--normalize: Unknown imenu item: nil` caused by b1f8d98a119ab8845d25d80c480cde6e385d8749
Date: Fri, 7 Apr 2023 18:33:40 -0400 [thread overview]
Message-ID: <CAKHgf3CUTm=8m7K4QFtjf3FJQv7bW8QtLvNP6dY1UB9nC_M-Lg@mail.gmail.com> (raw)
In-Reply-To: <CALDnm50pXHOHTi+ywTjPLm9ui+bseLxOHRPm4m2V1AYCdE5Dng@mail.gmail.com>
Ok, no worries! I misspoke actually, I meant to say `consult-imenu`.
I think the new interface is good! I just thought maybe some metadata
had been unintentionally lost.
I used to say something like 'Function/Renderer dispatch` where now it
says `Renderer dispatch` (ie. a struct Renderer containing a function
dispatch). I agree that showing the type of the symbol in text was a
bit confusing.
Cheers,
Casey
On Fri, Apr 7, 2023 at 6:24 PM João Távora <joaotavora@gmail.com> wrote:
>
> On Fri, Apr 7, 2023 at 11:15 PM Casey Banner <kcbanner@gmail.com> wrote:
> >
> > Thanks for the quick fixes! I noticed my imenu contents somewhat
> > changed (lost the description if something is a function vs constant),
> > but this might be an issue with my consult-line config.
>
> This change is intentional. The previous implementation was confusing
> IMO, at least for the original imenu interface M-x imenu.
> I don't use consult-line, can you show visually what has changed? Were
> you very fond of the old layout? :-)
>
> João
prev parent reply other threads:[~2023-04-07 22:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 21:29 bug#62719: 30.0.50; Eglot: `consult-imenu--normalize: Unknown imenu item: nil` caused by b1f8d98a119ab8845d25d80c480cde6e385d8749 Casey Banner
2023-04-07 21:55 ` João Távora
2023-04-07 22:03 ` João Távora
2023-04-07 22:15 ` Casey Banner
2023-04-07 22:26 ` João Távora
2023-04-07 22:33 ` Casey Banner [this message]
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='CAKHgf3CUTm=8m7K4QFtjf3FJQv7bW8QtLvNP6dY1UB9nC_M-Lg@mail.gmail.com' \
--to=kcbanner@gmail.com \
--cc=62719-done@debbugs.gnu.org \
--cc=joaotavora@gmail.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.