From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Alan Mackenzie Newsgroups: gmane.emacs.devel Subject: Re: My usage of imenu is broken. Date: Tue, 28 May 2024 20:46:48 +0000 Message-ID: References: <86r0dmtbk2.fsf@gnu.org> <86h6ehu6w8.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18903"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Yuan Fu , monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue May 28 22:47:52 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 1sC3jc-0004fD-Fy for ged-emacs-devel@m.gmane-mx.org; Tue, 28 May 2024 22:47:52 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sC3im-0003HK-Qr; Tue, 28 May 2024 16:47:01 -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 1sC3il-0003H6-If for emacs-devel@gnu.org; Tue, 28 May 2024 16:46:59 -0400 Original-Received: from mail.muc.de ([193.149.48.3]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sC3ii-0005iF-6y for emacs-devel@gnu.org; Tue, 28 May 2024 16:46:59 -0400 Original-Received: (qmail 33321 invoked by uid 3782); 28 May 2024 22:46:52 +0200 Original-Received: from muc.de (p4fe15d2d.dip0.t-ipconnect.de [79.225.93.45]) (using STARTTLS) by colin.muc.de (tmda-ofmipd) with ESMTP; Tue, 28 May 2024 22:46:52 +0200 Original-Received: (qmail 25024 invoked by uid 1000); 28 May 2024 20:46:48 -0000 Content-Disposition: inline In-Reply-To: <86h6ehu6w8.fsf@gnu.org> X-Submission-Agent: TMDA/1.3.x (Ph3nix) X-Primary-Address: acm@muc.de Received-SPF: pass client-ip=193.149.48.3; envelope-from=acm@muc.de; helo=mail.muc.de X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=unavailable 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:319658 Archived-At: Hello, Eli On Tue, May 28, 2024 at 21:29:43 +0300, Eli Zaretskii wrote: > > Date: Tue, 28 May 2024 13:57:46 +0000 > > Cc: emacs-devel@gnu.org > > From: Alan Mackenzie > > So my problem was being in c-ts-mode, for which all these things I don't > > like about imenu are apparently normal. It's one more reason for me to > > carry on using CC Mode. > I just now tried "M-x imenu" in c-ts-mode, and I don't see such a > catastrophe. True, if you leave imenu-flatten at its default nil > value, you need to choose top-level "kind" of identifiers before you > can type the name. For C, these "kinds" are Function, Variable, and > Struct. Once you do select one of them, Imenu prompts you again, and > then you can type the identifiers, with completion, or type TAB to see > all of the names. > This is not very different from what you are used to. It's different enough to me to matter. It adds boilerplate entry to data entry, and would likely more than double the time to get to the target function. I'm not saying here that it's bad, just that it would be bad for me. I don't think anything like the CC Mode imenu style is available in the c-ts-mode etc. modes. > Yuan, why does c-ts-mode' Imenu support behave differently in this > regard from CC Mode? What was the rationale for the different > behavior? I'm not Yuan, but it could be a desire to support variables and structs as well as just functions. -- Alan Mackenzie (Nuremberg, Germany).