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#46082: acknowledged by developer (control message for bug #46082) Date: Thu, 11 Mar 2021 16:26:30 +0200 Message-ID: <83k0qdn4vd.fsf@gnu.org> References: <87eegy6gtv.fsf@gnus.org> <83pn0i7i04.fsf@gnu.org> 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="31723"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 46082@debbugs.gnu.org To: Marco Munari Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Mar 11 15:27:11 2021 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 1lKMHO-00087t-PP for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 11 Mar 2021 15:27:10 +0100 Original-Received: from localhost ([::1]:33688 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lKMHN-0007Pj-R1 for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 11 Mar 2021 09:27:09 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35522) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lKMHG-0007Ny-FA for bug-gnu-emacs@gnu.org; Thu, 11 Mar 2021 09:27:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:41356) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lKMHG-0006lB-86 for bug-gnu-emacs@gnu.org; Thu, 11 Mar 2021 09:27:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1lKMHG-0006hv-4G for bug-gnu-emacs@gnu.org; Thu, 11 Mar 2021 09:27:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 11 Mar 2021 14:27:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 46082 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 46082-submit@debbugs.gnu.org id=B46082.161547280325743 (code B ref 46082); Thu, 11 Mar 2021 14:27:02 +0000 Original-Received: (at 46082) by debbugs.gnu.org; 11 Mar 2021 14:26:43 +0000 Original-Received: from localhost ([127.0.0.1]:52896 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lKMGw-0006h2-HX for submit@debbugs.gnu.org; Thu, 11 Mar 2021 09:26:43 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:45748) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lKMGu-0006gl-K4; Thu, 11 Mar 2021 09:26:41 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:40282) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lKMGn-0006V1-C0; Thu, 11 Mar 2021 09:26:33 -0500 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:4941 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1lKMGk-0008G8-S8; Thu, 11 Mar 2021 09:26:31 -0500 In-Reply-To: (message from Marco Munari on Mon, 08 Mar 2021 07:37:33 +0100) 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:202061 Archived-At: tags 46082 notabug thanks > From: Marco Munari > Cc: 46082@debbugs.gnu.org > Date: Mon, 08 Mar 2021 07:37:33 +0100 > > I noticed that when I copy and yank from an info buffer to gnus > it keept showing what the info buffers shown, but it didn't remain > the same on sending the email, so I didn't send previously the intended > info rendering (which renders worse than what I sent out). > Instead of "*note" (sent in the previous email) info shows "see" and adds > a dot > > So for example (python)Expression input is rendered with info.el > in user reading phase as: > | See eval(). is used for expression input. It ignores leading > | whitespace. The string argument to see eval(). must have the > | following form: > > from the python.info source > > | *note eval(): ca8. is used for expression input. It ignores leading > | whitespace. The string argument to *note eval(): ca8. must have the > | following form: That's normal: info.el hides some of the text of the buffer or even displays replacement text instead of some of the text in the buffer, but when you copy/paste the text into another buffer, the hidden text and the replacements are undone, and you see what is actually in buffer text. > which is from the texi input from texinfo > > | @ref{ca8,,eval()} is used for expression input. It ignores leading whitespace. The > | string argument to @ref{ca8,,eval()} must have the following form: Btw, these two instances of @ref are invalid use of @ref, as I explain below. And that incorrect use of @ref is actually at the heart of the problem which bothers you. IOW, it isn't an Emacs problem, it's a problem with how the original Texinfo was written (or produced from some other markup, if that's its prodigy). More details below. > which is output of makeinfo from somehow the following (but the info > says discursively that @ref should not gegerate a 'see', and the > makeinfo output has @ref (right as intended), emacs info.el show a "see") > (I don't see in this case necesseray the following deeper texinfo source > describing ref from git.savannah.gnu.org/git/texinfo.git file doc/texinfo.texi): This is a partial misunderstanding. The "see" which the Texinfo manual says isn't generated is not the one you see in Emacs in Info mode. What the Texinfo manual alludes to is this: when you use @xref or @pxref in Texinfo, they produce "see *note REFERENCE" (@xref produces a capitalized "See" instead). By contrast, @ref produces just *note REFERENCE". That is the "see" which Texinfo alludes to when it says that @ref doesn't produce it. The "see" which you see in the Info buffers in Emacs is the replacement for "*note". So it's a different kind of "see". > Then the following correct use of @ref > > ============================================================================== > @node perlfunc Perl Functions by Category > @section Perl Functions by Category > @cindex function > > Here are Perl's functions (including things that look like > functions, like some keywords and named operators) > arranged by category. Some functions appear in more > than one place. Any warnings, including those produced by > keywords, are described in @ref{perldiag NAME} and @ref{,,, warnings}. > > @table @asis > @item Functions for SCALARs or strings > @anchor{perlfunc Functions for SCALARs or strings} > @cindex scalar > @cindex string > @cindex character > > @ref{perlfunc chomp VARIABLE, @code{chomp}, @code{chomp}}, @ref{perlfunc chop VARIABLE, @code{chop}, @code{chop}}, > @ref{perlfunc chr NUMBER, @code{chr}, @code{chr}}, @ref{perlfunc crypt PLAINTEXT@comma{}SALT, @code{crypt}, @code{crypt}}, > @ref{perlfunc fc EXPR, @code{fc}, @code{fc}}, @ref{perlfunc hex EXPR, @code{hex}, @code{hex}}, That isn't a correct use of @ref. @ref was never meant to be used like an HTML " produces with `makeinfo` the .info: > ... > | Functions for SCALARs or strings > | > | *note ‘chomp’: chomp VARIABLE, *note ‘chop’: chop VARIABLE, *note > | ‘chr’: chr NUMBER, *note ‘crypt’: crypt PLAINTEXT,SALT, *note ‘fc’: > | fc EXPR, *note ‘hex’: hex EXPR, *note ‘index’: index > | STR,SUBSTR,POSITION, *note ‘lc’: lc EXPR, *note ‘lcfirst’: lcfirst > | EXPR, *note ‘length’: length EXPR, *note ‘oct’: oct EXPR, *note > | ‘ord’: ord EXPR, *note ‘pack’: pack TEMPLATE,LIST, *note ‘q//’: > | q/STRING/, *note ‘qq//’: qq/STRING/, *note ‘reverse’: reverse LIST, > | *note ‘rindex’: rindex STR,SUBSTR,POSITION, *note ‘sprintf’: > | sprintf FORMAT, LIST, *note ‘substr’: substr > | EXPR,OFFSET,LENGTH,REPLACEMENT, *note ‘tr///’: tr///, *note ‘uc’: > | uc EXPR, *note ‘ucfirst’: ucfirst EXPR, *note ‘y///’: y///. > | > | *note ‘fc’: fc EXPR. is available only if the *note ‘"fc"’ feature: > | (feature)The 'fc' feature. is enabled or if it is prefixed with > | ‘CORE::’. The *note ‘"fc"’ feature: (feature)The 'fc' feature. is > | enabled automatically with a ‘use v5.16’ (or higher) declaration in > | the current scope. > > > which end up by default (before my change) being rendered in emacs as: > > | Here are Perl’s functions (including things that look like functions, > | like some keywords and named operators) arranged by category. Some > | functions appear in more than one place. Any warnings, including those > | produced by keywords, are described in see (perldiag) and see > | (warnings). > | > | Functions for SCALARs or strings > | > | See ‘chomp’ see ‘chop’ see > | ‘chr’ see ‘crypt’ see ‘fc’ > | see ‘hex’, see ‘index’ > | SUBSTR,POSIT, see ‘lc’ see ‘lcfirst’ > | see ‘length’ see ‘oct’ see > | ‘ord’, see ‘pack’ see ‘q//’ > | see ‘qq//’ see ‘reverse’ > | see ‘rindex’ see ‘sprintf’ > | see ‘substr’ > | OFFSET,LENGTH,REPLACEMENT, see ‘tr///’ see ‘uc’ > | see ‘ucfirst’ see ‘y///’. > | > | See ‘fc’. is available only if the see ‘"fc"’ feature > | (feature). is enabled or if it is prefixed with > | ‘CORE::’. The see ‘"fc"’ feature(feature). is > | enabled automatically with a ‘use v5.16’ (or higher) declaration in > | the current scope. That's expected. The problem is that whoever wrote that Texinfo expected to see just the names of the functions, displayed in a typeface suitable for hyperlinks. But that's not how @ref works. This is not a bug, not an Emacs bug, anyway.