From: schwarze@mdocml.bsd.lv
To: source@mdocml.bsd.lv
Subject: mdocml: Fix a nasty typo that prevented .so links to gziped manuals
Date: Sun, 10 Jul 2016 08:35:00 -0500 (EST) [thread overview]
Message-ID: <14120487462497294871.enqueue@fantadrom.bsd.lv> (raw)
Log Message:
-----------
Fix a nasty typo that prevented .so links to gziped manuals
from working in the absence of a mandoc.db(5) database.
Found the hard way by Svyatoslav Mishyn on Crux Linux.
Modified Files:
--------------
mdocml:
read.c
Revision Data
-------------
Index: read.c
===================================================================
RCS file: /home/cvs/mdocml/mdocml/read.c,v
retrieving revision 1.148
retrieving revision 1.149
diff -Lread.c -Lread.c -u -p -r1.148 -r1.149
--- read.c
+++ read.c
@@ -798,7 +798,7 @@ mparse_open(struct mparse *curp, const c
if ( ! curp->gzip) {
mandoc_asprintf(&cp, "%s.gz", file);
- fd = open(file, O_RDONLY);
+ fd = open(cp, O_RDONLY);
free(cp);
if (fd != -1) {
curp->gzip = 1;
--
To unsubscribe send an email to source+unsubscribe@mdocml.bsd.lv
reply other threads:[~2016-07-10 13:35 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=14120487462497294871.enqueue@fantadrom.bsd.lv \
--to=schwarze@mdocml.bsd.lv \
--cc=source@mdocml.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).