From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.devel,gmane.emacs.orgmode Subject: Re: [FR] Allow flattened imenu index (was: [PATCH] Add new option 'org-imenu-flatten') Date: Sat, 09 Dec 2023 11:39:33 +0000 Message-ID: <874jgrsiyy.fsf@localhost> References: <87plzgbalt.fsf@localhost> <87msujskxg.fsf@localhost> <835y17y5qu.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="4644"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Morgan.J.Smith@outlook.com, emacs-orgmode@gnu.org, 58131@debbugs.gnu.org, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Dec 09 12:37:40 2023 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 1rBveO-00010I-6Z for ged-emacs-devel@m.gmane-mx.org; Sat, 09 Dec 2023 12:37:40 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rBvdK-0003xk-VF; Sat, 09 Dec 2023 06:36:34 -0500 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 1rBvdI-0003xS-NJ for emacs-devel@gnu.org; Sat, 09 Dec 2023 06:36:32 -0500 Original-Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rBvdE-0003WV-FG for emacs-devel@gnu.org; Sat, 09 Dec 2023 06:36:32 -0500 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 1DB27240028 for ; Sat, 9 Dec 2023 12:36:26 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1702121786; bh=legTLHJrPHfi4Gt/M2hp/VHdox05MCogs97Br2rYCzw=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:From; b=JL1rrlo4xemsoBFnBCedmp4gfzCpGGDP1VR1VXfXqDo1MIEt9+1uQci4QiR41ab+j RrPpnadbsIzQMYUS9IZFoI4gJv1pddsQy1tKlzQ1gz7YHQQJazbG7fHMxoSNcYB9BT szqgN5BoZIsP1GAav3EH0GBYbmcQD+TimUBMEbVth+iYlFitHcBDxaIsodA3dI9qbe 6LVrW28gaNL0c/hPRUz7HQHUHbQmH2jld56l3jm144t92NahSzptJVxQEKDSQAjvwr S8EcNYhJK5l0TgugdPltk3tt/uLeRGlCaP6mHChaIdB7C8o+K+MeQIQXlQR1MQ0DLf if9TNgasVlDZg== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4SnQvF42ytz9rxN; Sat, 9 Dec 2023 12:36:25 +0100 (CET) In-Reply-To: <835y17y5qu.fsf@gnu.org> Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=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:313633 gmane.emacs.orgmode:158506 Archived-At: Eli Zaretskii writes: >> I am wondering if it makes more sense to add this "flatten" option >> globally into imenu instead. > > I'm not sure I understand what you are asking. As we don't seem to > have an active maintainer of imenu on board, more details are needed > to understand the request. Of course, patches are even more welcome. Normally, `imenu' supports nested menus, when users select the target location in steps, like item3 -> item3.1 -> ... What is proposed is to list all the sub-menus together, as an option, so that the users can choose, for example, item.3.1 directly, without going through parent item3. > Also, should this be a new bug report? the one mentioned in the CC is > already closed and archived. Maybe. I was just not sure how I can create a new bug report, while still replying to Org mode feature request. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at