From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Integration of Info manuals in programming modes Date: Thu, 05 Dec 2024 14:01:39 +0200 Message-ID: <86a5damj8c.fsf@gnu.org> References: <87ser8c230.fsf@jeremybryant.net> <86ser87rut.fsf@gnu.org> <87cyicuk25.fsf@melete.silentflame.com> <86jzcj6e4h.fsf@gnu.org> <87y10u6174.fsf@web.de> <86ldwuy3lu.fsf@gnu.org> <877c8ey0iu.fsf@gmail.com> <86ed2mxzj4.fsf@gnu.org> <87y10uwjc6.fsf@gmail.com> <865xnyxtsv.fsf@gnu.org> <87ttbiweqx.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="37020"; mail-complaints-to="usenet@ciao.gmane.io" Cc: arne_bab@web.de, rms@gnu.org, spwhitton@spwhitton.name, jb@jeremybryant.net, emacs-devel@gnu.org To: Visuwesh Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Dec 05 13:02:56 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 1tJAZL-0009Oc-C2 for ged-emacs-devel@m.gmane-mx.org; Thu, 05 Dec 2024 13:02:55 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tJAYU-0002sd-HV; Thu, 05 Dec 2024 07:02:02 -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 1tJAYR-0002sD-SG for emacs-devel@gnu.org; Thu, 05 Dec 2024 07:02:00 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tJAYQ-0002z0-19; Thu, 05 Dec 2024 07:01:58 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=PYSTnGpJh0oC1w8TEuGe9vh5ek2X8LnT5cbSv9cwfDQ=; b=kUTD4ynPN1wfXLHSZ+1N Rp720kzQLxxPE7Dor+MCc1SEbitoNft8TZzKfRJyIveJ/ThfK9xFWpEBkN8VUoUmzb4dtwyRqfgx+ f5wxd5Q3NVpn/OFtd2DFOL8nZsd1B4woctSH8pO8F3tnOWA9Ixk6KfnaSGh4blFKeEC3agFYFIUNk f6cjWhaIUOkfXVt1DwORaGeCiJtArLb3qrz1r+aqO/he9xdsjNIrCxqE1+MVwg/ZYJnHWMAUf5cvA I4ceqVoNFRSWuq+hwwI2iySquMCLhiqPWYQOBYyKW/GI/VSUMGD8FK42FNC3jqQV2CA5SQVtVAzCq ok5fLv6cRVWozg==; In-Reply-To: <87ttbiweqx.fsf@gmail.com> (message from Visuwesh on Thu, 05 Dec 2024 16:58:22 +0530) 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:326086 Archived-At: > From: Visuwesh > Cc: arne_bab@web.de, rms@gnu.org, spwhitton@spwhitton.name, > jb@jeremybryant.net, emacs-devel@gnu.org > Date: Thu, 05 Dec 2024 16:58:22 +0530 > > [வியாழன் டிசம்பர் 05, 2024] Eli Zaretskii wrote: > > >> From: Visuwesh > >> Cc: arne_bab@web.de, rms@gnu.org, spwhitton@spwhitton.name, > >> jb@jeremybryant.net, emacs-devel@gnu.org > >> Date: Thu, 05 Dec 2024 15:19:13 +0530 > >> > >> [வியாழன் டிசம்பர் 05, 2024] Eli Zaretskii wrote: > >> > >> >> but I do not understand how info-lookup works really. C-h S RET on > >> >> 'read' jumps to the FGET page which is not we want. > >> > > >> > Look at the index node you mentioned: what other menu item that > >> > matches "read" there is more appropriate? And what did you expect to > >> > see instead? > >> > >> I would rather see a complain about no matches. If someone could figure > >> out how to reject non-exact matches, that would be do the job. > > > > That's a double-edge sword: rejecting non-exact matches could miss > > valid hits. > > I agree, dismissing a invalid match is not too much trouble. > > > However, maybe the regexp should only match keywords in upper-case, > > and ignore-case should not be used? > > But Fortran is a case-insensitive language and recent style-guides ask > you to use lower case lettering for everything. Other code that I've > seen use upper case lettering for keywords, not for functions and > subroutines so we cannot opt for this route unfortunately. What is important in this context is not whether Fortran is case-insensitive, but how the index of the manual spells the keywords.