From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: My usage of imenu is broken. Date: Wed, 29 May 2024 09:04:35 +0300 Organization: LINKOV.NET Message-ID: <86y17tnryx.fsf@mail.linkov.net> References: <86r0dmtbk2.fsf@gnu.org> <86h6ehu6w8.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23663"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/30.0.50 (x86_64-pc-linux-gnu) Cc: Alan Mackenzie , Eli Zaretskii , Yuan Fu , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed May 29 08:06:14 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1sCCRy-0005wX-0u for ged-emacs-devel@m.gmane-mx.org; Wed, 29 May 2024 08:06:14 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sCCR1-0007e2-54; Wed, 29 May 2024 02:05:15 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sCCQt-0007RX-V9 for emacs-devel@gnu.org; Wed, 29 May 2024 02:05:09 -0400 Original-Received: from relay3-d.mail.gandi.net ([217.70.183.195]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sCCQp-0002we-3D; Wed, 29 May 2024 02:05:05 -0400 Original-Received: by mail.gandi.net (Postfix) with ESMTPSA id AD1B260003; Wed, 29 May 2024 06:04:54 +0000 (UTC) In-Reply-To: (Stefan Monnier's message of "Tue, 28 May 2024 17:28:21 -0400") X-GND-Sasl: juri@linkov.net Received-SPF: pass client-ip=217.70.183.195; envelope-from=juri@linkov.net; helo=relay3-d.mail.gandi.net X-Spam_score_int: -25 X-Spam_score: -2.6 X-Spam_bar: -- X-Spam_report: (-2.6 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:319670 Archived-At: > FWIW, I think the problem partly lies on the side of `imenu`. > The API should let major modes provide the info once and for all, and > then the user should be able to choose whether they prefer to see it as > a few steps down a decision tree (e.g. first choose the category then > the identifier) or something else (e.g. completion of strings of the > form " ", or order-agnostic so you can write > either " " or " ", or ...). While using a deep hierarchy of subcategories, it's clear how to order them for the prefix option of 'imenu-flatten': " " But the suffix option of 'imenu-flatten' is ambiguous, with the choice of whether to prefer this order: " " or " " Probably there is no *-ts-mode with more nested levels than 2, but e.g. doc-view-imenu-index for a PDF with the hierarchical table of contents both suffix orders make sense.