From: VanL <van@scratch.space>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 36927@debbugs.gnu.org
Subject: bug#36927: 26.2.90; include stdarg.h is without hyperlinking on vfprintf's manpage
Date: Tue, 6 Aug 2019 17:22:42 +1000 [thread overview]
Message-ID: <8D8ABD32-1634-4075-AEA1-A044BCE4823B@scratch.space> (raw)
In-Reply-To: <FC13E6F5-5CAB-4EEB-B2A3-B883A72818B1@gnu.org>
> On 6 Aug 2019, at 13:56, Eli Zaretskii <eliz@gnu.org> wrote:
>
>>> 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?
In this case, I mean the lines containing the 'include' preprocessing directive for C.
Where you make every word a button, possibly, leads to an inverted tree index for search engines to digest, perhaps 'C-h a' short for '(ask-emacs-anything)' is then possible.
>> 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.
line 11: .In stdio.h
line 24: .In stdarg.h
> 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.
2 matches for "Man-include-regexp" in buffer: man.el.gz
338:(defvar Man-include-regexp "#[ \t]*include[ \t]*"
348: (concat "\\(" Man-include-regexp "\\)"
14 matches in 12 lines for "include" in buffer: man.el.gz
231: (base '("/usr/include" "/usr/local/include")))
234: (append base (list (expand-file-name arch "/usr/include")))))
338:(defvar Man-include-regexp "#[ \t]*include[ \t]*"
339: "Regular expression describing the #include (directive of cpp).")
342: "Regular expression describing <> in #include line (directive of cpp).")
348: (concat "\\(" Man-include-regexp "\\)"
358:;; This includes the section as an optional part to catch hyphenated
794: ;; doesn't include a hyphen, we consider the hyphen to be
799: ;; Make sure the section number gets included by the code below.
812: ;; include the section number in the returned value.
1265:References include items in the SEE ALSO section,
1266:header file (#include <foo.h>), and files in FILES.
next prev parent reply other threads:[~2019-08-06 7:22 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8D8ABD32-1634-4075-AEA1-A044BCE4823B@scratch.space \
--to=van@scratch.space \
--cc=36927@debbugs.gnu.org \
--cc=eliz@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.