unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 17:36:08 +0300	[thread overview]
Message-ID: <838ss6cqef.fsf@gnu.org> (raw)
In-Reply-To: <8D8ABD32-1634-4075-AEA1-A044BCE4823B@scratch.space> (message from VanL on Tue, 6 Aug 2019 17:22:42 +1000)

> From: VanL <van@scratch.space>
> Date: Tue, 6 Aug 2019 17:22:42 +1000
> Cc: 36927@debbugs.gnu.org
> 
> >> 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.
> 
> The script to massage by 'M-x woman RET vfprintf' produces pure, unadulterated formatting in text-mode.

"M-x woman" uses an entirely different implementation: it actually
formats the man page by itself, and thus doesn't need any script for
massaging the output of 'man'.

> > Do you actually see what causes the failure to put a button on the second include?
> 
> There's that below but lisp/button.el.gz doesn't have any Man variable I can see.

Thanks.





  reply	other threads:[~2019-08-06 14:36 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
2019-08-06  7:22       ` VanL
2019-08-06 14:36         ` Eli Zaretskii [this message]
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=838ss6cqef.fsf@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).