From: Eli Zaretskii <eliz@gnu.org>
To: VanL <van@scratch.space>
Cc: 36927@debbugs.gnu.org
Subject: bug#36927: 26.2.90; include stdarg.h is without hyperlinking on vfprintf's manpage
Date: Tue, 06 Aug 2019 06:56:46 +0300 [thread overview]
Message-ID: <FC13E6F5-5CAB-4EEB-B2A3-B883A72818B1@gnu.org> (raw)
In-Reply-To: <64EC7182-5090-4A27-A21E-9203A7845B76@scratch.space>
On August 6, 2019 5:36:17 AM GMT+03:00, VanL <van@scratch.space> wrote:
>
> > On 6 Aug 2019, at 02:10, Eli Zaretskii <eliz@gnu.org> wrote:
> >
> >> 1. M-x man RET vfprintf
> >> 2. on line 32 see #include <stdarg.h> which is without hyperlinking
> >
> > For some reason, we don't put a button on the second #include.
>
> The buttoning needs to be more aggressive.
You mean, like making every word a button?
> > Interestingly enough, I can reproduce this on GNU/Linux, but not on
> > MS-Windows, even if I produce the formatted man page on GNU/Linux
> and
> > then display it on Windows. So I guess the problem is somehow
> related
> > to the slightly different scripts we use to massage the man page
> for
> > display.
>
> Three variants of bsd platform reproduces this like GNU/Linux.
All Posix platforms use the same script to massage the 'man' output, so this is hardly surprising.
Do you actually see what causes the failure to put a button on the second include?
next prev parent reply other threads:[~2019-08-06 3:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 1:51 bug#36927: 26.2.90; include stdarg.h is without hyperlinking on vfprintf's manpage VanL
2019-08-05 16:10 ` Eli Zaretskii
2019-08-06 2:36 ` VanL
2019-08-06 3:56 ` Eli Zaretskii [this message]
2019-08-06 7:22 ` VanL
2019-08-06 14:36 ` Eli Zaretskii
2019-08-07 8:57 ` VanL
2019-08-09 13:58 ` Eli Zaretskii
2019-08-10 5:05 ` VanL
2019-08-10 7:48 ` Eli Zaretskii
2019-08-11 5:26 ` VanL
2019-08-11 14:09 ` Eli Zaretskii
2019-08-18 22:37 ` Noam Postavsky
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=FC13E6F5-5CAB-4EEB-B2A3-B883A72818B1@gnu.org \
--to=eliz@gnu.org \
--cc=36927@debbugs.gnu.org \
--cc=van@scratch.space \
/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).