tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: Svyatoslav Mishyn <juef@openmailbox.org>
Cc: tech@mdocml.bsd.lv
Subject: Re: call for testing: mandoc-1.13.4 release candidate
Date: Sun, 10 Jul 2016 15:39:49 +0200	[thread overview]
Message-ID: <20160710133949.GC14535@athene.usta.de> (raw)
In-Reply-To: <20160710104557.GA1748@k8>

Hi Svyatoslav,

Svyatoslav Mishyn Crux wrote on Sun, Jul 10, 2016 at 01:46:00PM +0300:
> (Sat, 09 Jul 21:55) Svyatoslav Mishyn:

>> Also some manual pages I cannot open.
>> 
>> /home/juef: man 2 open > tmp/e
>> man: man2/open.2: ERROR: No such file or directory
>> 
>> /home/juef: cat tmp/e
>> ()                                                               ()
>> 
>> See the file man2/open.2.
>> 
>>                           July 9, 2016                           ()

> If I remove openat.2.gz and creat.2.gz, it works.
> 
> /home/juef: zcat /usr/share/man/man2/openat.2.gz
> .so man2/open.2
> 
> There wasn't such problem in v1.13.3.

Whoa, good catch, thanks!
Fixed by the commit below.

Yours,
  Ingo


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 tech+unsubscribe@mdocml.bsd.lv

  reply	other threads:[~2016-07-10 13:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <sfid-H20160709-151232-+015.17-1@spamfilter.osbf.lua>
     [not found] ` <20160709131158.GA6629@athene.usta.de>
2016-07-09 13:18   ` Thomas Klausner
2016-07-09 15:30     ` Ingo Schwarze
2016-07-09 13:39   ` Baptiste Daroussin FreeBSD
2016-07-09 14:31     ` Anthony J. Bentley
2016-07-09 15:29       ` New db format (was Re: call for testing: mandoc-1.13.4 release candidate) Baptiste Daroussin
2016-07-09 16:12         ` New db format Ingo Schwarze
2016-08-05 20:26           ` Baptiste Daroussin
2016-07-09 14:28   ` call for testing: mandoc-1.13.4 release candidate Svyatoslav Mishyn Crux
2016-07-10 14:08     ` Ingo Schwarze
2016-07-09 18:21   ` Svyatoslav Mishyn
2016-07-09 21:13     ` Ingo Schwarze
2016-07-09 18:55   ` Svyatoslav Mishyn Crux
2016-07-10 10:46     ` Svyatoslav Mishyn
2016-07-10 13:39       ` Ingo Schwarze [this message]
2016-07-10 14:27   ` Christian Neukirchen
2016-07-10 16:36     ` Ingo Schwarze
2016-07-10 16:48       ` Christian Neukirchen
2016-07-10 18:34         ` Ingo Schwarze

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=20160710133949.GC14535@athene.usta.de \
    --to=schwarze@usta.de \
    --cc=juef@openmailbox.org \
    --cc=tech@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).