From: Lars Ingebrigtsen <larsi@gnus.org>
To: Marco Munari <mar21+dev.emacs.bugfix@allerta.it>
Cc: 46082@debbugs.gnu.org, "Kim F. Storm" <storm@cua.dk>
Subject: bug#46082: (texinfo) @ref says something lisp/info.el do not respect by default
Date: Mon, 01 Mar 2021 16:20:38 +0100 [thread overview]
Message-ID: <87ft1e6gu1.fsf@gnus.org> (raw)
In-Reply-To: <87im7jdr4b.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 27 Jan 2021 03:56:52 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Marco Munari <mar21+dev.emacs.bugfix@allerta.it> writes:
>
>> for example python info documentation was plenty of misplaced
>> ``See`` ... ``.`` (which is the reason I looked into the origin of the
>> problem) and found it: @ref should have not a processing for info that
>> add "See" as should while processing @xref, than the pxref is to
>> distinguish printed rendering.
>
> Do you have an example of how Emacs displays this Python documentation?
More information was requested, but no response was given within a
month, so I'm closing this bug report. If the problem still exists,
please respond to this email and we'll reopen the bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-03-01 15:20 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 [this message]
[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
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=87ft1e6gu1.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=46082@debbugs.gnu.org \
--cc=mar21+dev.emacs.bugfix@allerta.it \
--cc=storm@cua.dk \
/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.