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.bugs Subject: bug#40900: Add face for function params in info Date: Wed, 09 Sep 2020 18:03:11 +0300 Message-ID: <834ko7kn68.fsf@gnu.org> References: <83mu6x3r4k.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19555"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 40900@debbugs.gnu.org, ndame@protonmail.com To: Stefan Kangas Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Sep 09 17:04:12 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1kG1dr-0004nJ-JV for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 09 Sep 2020 17:04:11 +0200 Original-Received: from localhost ([::1]:34462 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kG1dq-0002qa-LU for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 09 Sep 2020 11:04:10 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:33514) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kG1di-0002p3-07 for bug-gnu-emacs@gnu.org; Wed, 09 Sep 2020 11:04:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:49579) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kG1dh-00024j-MZ for bug-gnu-emacs@gnu.org; Wed, 09 Sep 2020 11:04:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kG1dh-0002hB-Ij for bug-gnu-emacs@gnu.org; Wed, 09 Sep 2020 11:04:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 09 Sep 2020 15:04:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 40900 X-GNU-PR-Package: emacs Original-Received: via spool by 40900-submit@debbugs.gnu.org id=B40900.159966379710309 (code B ref 40900); Wed, 09 Sep 2020 15:04:01 +0000 Original-Received: (at 40900) by debbugs.gnu.org; 9 Sep 2020 15:03:17 +0000 Original-Received: from localhost ([127.0.0.1]:32892 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kG1cy-0002gD-MQ for submit@debbugs.gnu.org; Wed, 09 Sep 2020 11:03:17 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:51430) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kG1cw-0002fz-LN for 40900@debbugs.gnu.org; Wed, 09 Sep 2020 11:03:15 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:36106) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kG1cr-0001nB-Cd; Wed, 09 Sep 2020 11:03:09 -0400 Original-Received: from [176.228.60.248] (port=3756 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kG1cp-0007U9-Tq; Wed, 09 Sep 2020 11:03:08 -0400 In-Reply-To: (message from Stefan Kangas on Wed, 9 Sep 2020 06:22:25 -0700) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:187666 Archived-At: > From: Stefan Kangas > Date: Wed, 9 Sep 2020 06:22:25 -0700 > Cc: ndame , 40900@debbugs.gnu.org > > > I think the challenge is to reliably identify the strings that are > > function parameters. Info files lack the markup that identifies > > various symbols in the Texinfo sources, and the code which finds > > function arguments must not err too much, or users will complain. > > Isn't this therefore a limitation in Texinfo? We could of course hack > around it, but it sounds like it would risk being error-prone and hard > to maintain. It is a limitation of the Info format produced from Texinfo sources. For example, HTML format produced from Texinfo still has markup, which could be used for such features.