From: schwarze@mandoc.bsd.lv
To: source@mandoc.bsd.lv
Subject: mandoc: handle man3c/fopen.3c in main.c/fs_*()
Date: Tue, 21 Sep 2021 12:58:43 -0500 (EST) [thread overview]
Message-ID: <c2aacdc6b1534e2b@mandoc.bsd.lv> (raw)
Log Message:
-----------
handle man3c/fopen.3c in main.c/fs_*()
Modified Files:
--------------
mandoc:
TODO
Revision Data
-------------
Index: TODO
===================================================================
RCS file: /home/cvs/mandoc/mandoc/TODO,v
retrieving revision 1.318
retrieving revision 1.319
diff -LTODO -LTODO -u -p -r1.318 -r1.319
--- TODO
+++ TODO
@@ -292,6 +292,11 @@ are mere guesses, and some may be wrong.
--- missing misc features ----------------------------------------------
+- conisder whether man(1) fallback code in main.c/fs_*() can find files
+ like man3c/fopen.3c (illumos, Solaris) and man3p/fopen.3p (POSIX)
+ discussed with Robert Mustacchi 21 Sep 2021 10:39:40 -0700
+ loc * exist * algo ** size * imp **
+
- let makewhatis(8) follow symbolic links to dirs below READ_ALLOWED_PATH
this may be feasible using fts_set(FTS_FOLLOW)
mail to sternenseemann 19 Aug 2021 19:11:50 +0200
--
To unsubscribe send an email to source+unsubscribe@mandoc.bsd.lv
reply other threads:[~2021-09-21 17:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=c2aacdc6b1534e2b@mandoc.bsd.lv \
--to=schwarze@mandoc.bsd.lv \
--cc=source@mandoc.bsd.lv \
/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.
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 NNTP newsgroup(s).