From: schwarze@mandoc.bsd.lv
To: source@mandoc.bsd.lv
Subject: mandoc: already an old idea: abbreviate pathnames for -M
Date: Fri, 24 Nov 2023 04:39:21 +0000 (UTC) [thread overview]
Message-ID: <d679f04d5d167023@mandoc.bsd.lv> (raw)
Log Message:
-----------
already an old idea: abbreviate pathnames for -M
Modified Files:
--------------
mandoc:
TODO
Revision Data
-------------
Index: TODO
===================================================================
RCS file: /home/cvs/mandoc/mandoc/TODO,v
retrieving revision 1.332
retrieving revision 1.333
diff -LTODO -LTODO -u -p -r1.332 -r1.333
--- TODO
+++ TODO
@@ -314,7 +314,7 @@ are mere guesses, and some may be wrong.
certainly affects man(7); possibly mdoc(7)?; and also groff(1)
Alejandro Colomar 21 Aug 2022
-- conisder whether man(1) fallback code in main.c/fs_*() can find files
+- consider 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 **
@@ -357,6 +357,10 @@ are mere guesses, and some may be wrong.
see textproc/mgdiff(1) for nice examples
(3) undefined, just output the character -> perhaps WARNING
loc *** exist ** algo ** size ** imp *** (parser reorg helps)
+
+- man.conf(5) alias aliasname dirname or just -Mb -Mx -Mp
+ mail to jmc@ Mar 23, 2015 03:53:14PM +0100
+ loc * exist * algo * size * imp **
- kettenis wants base roff, ms, and me Fri, 1 Jan 2010 22:13:15 +0100 (CET)
loc ** exist ** algo ** size *** imp *
--
To unsubscribe send an email to source+unsubscribe@mandoc.bsd.lv
reply other threads:[~2023-11-24 4:39 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=d679f04d5d167023@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).