From: Marco Munari <mar21@allerta.it>
To: 46082@debbugs.gnu.org
Subject: bug#46082: acknowledged by developer (control message for bug #46082)
Date: Mon, 01 Mar 2021 20:22:58 +0100 [thread overview]
Message-ID: <ywm35xe8yr1.fsf@nb.mm.homeunix.org.valid> (raw)
In-Reply-To: <ywmwnw2fgha.fsf@nb.mm.homeunix.org.valid>
I noticed only the bug close notification now,
the mention of python info example was secondary,
the rendering difform to specification emerges precisely
with (texinfo) manual itself
Repro steps:
1. launch emacs info C-h i
2. go to node g (texinfo)@ref
read the rendered manual page with attention
(I described at the beginning of the initial bug report
the problem in the line marked with (*))
python and even perl info manuals uses a lot of @ref (according
to the way texinfo does and describe its functionality)
resulting a lot of inappropriate See making the references surrounded
by nonsense "see ... dot(.)", but the problem emerges in the exact page
of texinfo describing how @ref should work, showing that it doesnt.
Anyway as required an example on how python manual looks,
here there is a random section (Note the "see" are simply misleading.
My fix removes the default misbehaviour for "see",
but the dot(.) after the node description remains):
========================================================================
File: python.info, Node: Expression input, Prev: Interactive input, Up: Top-level components
4.9.4 Expression input
----------------------
*note eval(). is used for expression input. It ignores leading
whitespace. The string argument to *note eval(). must have the
following form:
eval_input ::= expression_list NEWLINE*
========================================================================
And here is an extract of `perlfunc` info manual:
========================================================================
File: perlfunc.info, Node: Top, Up: (dir)
1 NAME
******
perlfunc - Perl builtin functions
2 DESCRIPTION
*************
...
2.1 Perl Functions by Category
==============================
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 *note (perldiag):: and *note
(warnings)::.
Functions for SCALARs or strings
*note ‘chomp’, *note ‘chop’, *note
‘chr’, *note ‘crypt’ *note ‘fc’, *note ‘hex’, *note ‘index’,
*note ‘lc’, *note ‘lcfirst’, *note ‘length’, *note ‘oct’, *note
‘ord’, *note ‘pack’, *note ‘q//’, *note ‘qq//’, *note ‘reverse’,
*note ‘rindex’, *note ‘sprintf’, *note ‘substr’, *note ‘tr///’,
*note ‘uc’, *note ‘ucfirst’, *note ‘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.
Regular expressions and pattern matching
*note ‘m//’: m//, *note ‘pos’: pos SCALAR, *note ‘qr//’:
qr/STRING/, *note ‘quotemeta’: quotemeta EXPR, *note ‘s///’: s///,
*note ‘split’: split /PATTERN/,EXPR,LIMIT, *note ‘study’: study
SCALAR.
...
break
Break out of a ‘given’ block.
*note ‘break’. is available only if the *note ‘"switch"’
feature(feature). is enabled or if it is
prefixed with ‘CORE::’. The *note ‘"switch"’ feature(feature).
. is enabled automatically with a ‘use v5.10’ (or
higher) declaration in the current scope.
...
========================================================================
next prev parent reply other threads:[~2021-03-01 19:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87eegy6gtv.fsf@gnus.org>
2021-01-24 16:26 ` bug#46082: (texinfo) @ref says something lisp/info.el do not respect by default Marco Munari
2021-01-27 2:56 ` Lars Ingebrigtsen
2021-03-01 15:20 ` Lars Ingebrigtsen
[not found] ` <handler.46082.C.161461205518066.notifdonectrl.0@debbugs.gnu.org>
2021-03-01 19:22 ` Marco Munari [this message]
2021-03-01 20:10 ` bug#46082: acknowledged by developer (control message for bug #46082) Eli Zaretskii
2021-03-08 6:37 ` Marco Munari
2021-03-11 14:26 ` Eli Zaretskii
2021-04-09 16:59 ` bug#46082: (texinfo) @ref says something lisp/info.el do not respect by default Stefan Kangas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ywm35xe8yr1.fsf@nb.mm.homeunix.org.valid \
--to=mar21@allerta.it \
--cc=46082@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.