unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Marco Munari <mar21@allerta.it>
Cc: 46082@debbugs.gnu.org
Subject: bug#46082: acknowledged by developer (control message for bug #46082)
Date: Mon, 01 Mar 2021 22:10:03 +0200	[thread overview]
Message-ID: <83pn0i7i04.fsf@gnu.org> (raw)
In-Reply-To: <ywm35xe8yr1.fsf@nb.mm.homeunix.org.valid> (message from Marco Munari on Mon, 01 Mar 2021 20:22:58 +0100)

> From: Marco Munari <mar21@allerta.it>
> Date: Mon, 01 Mar 2021 20:22:58 +0100
> 
> 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):

I have difficulty understanding the problem, and thus the proposed
solution.  I think the difficulty stems from the fact that you didn't
show the Texinfo source of the Info output which you posted.  Without
that, it's hard to decide whether the problem is with Emacs, or with
Texinfo's 'makeinfo', or with the original Texinfo source as authored
by whoever wrote those manuals (which are not Emacs manuals).

So please show the Texinfo sources of these snippets.

Thanks.





  reply	other threads:[~2021-03-01 20:10 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     ` bug#46082: acknowledged by developer (control message for bug #46082) Marco Munari
2021-03-01 20:10       ` Eli Zaretskii [this message]
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83pn0i7i04.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=46082@debbugs.gnu.org \
    --cc=mar21@allerta.it \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).