tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Svyatoslav Mishyn Crux <juef@openmailbox.org>
To: tech@mdocml.bsd.lv
Subject: Re: call for testing: mandoc-1.13.4 release candidate
Date: Sat, 9 Jul 2016 17:28:20 +0300	[thread overview]
Message-ID: <20160709142813.GA13260@k8> (raw)
In-Reply-To: <20160709131158.GA6629@athene.usta.de>


[-- Attachment #1.1: Type: text/plain, Size: 2887 bytes --]

(Sat, 09 Jul 15:11) Ingo Schwarze:
> Hi,
> 
> i'm planning to release mandoc-1.13.4 during the next week.
> 
> Since you are listed as downstream port/package maintainers
> and/or have sent in major contributions or many and/or important
> bug reports lately, i'm giving you the chance of testing
> the non-public release candidate on your favourite platform(s)
> in advance if you want to.  Please do not publicly update your
> ports/packages just yet.
> 
> To avoid flooding people's mailboxes, please don't reply to the
> full To: list, but rather publicly to <tech@mdocml.bsd.lv>
> (requires subscription) or privately to <devel@mdocml.bsd.lv>.
> 
> Both reports of successes and failures are welcome!
> 
> I already did some testing myself on OpenBSD-6.0-current,
> OpenBSD-5.9-stable, OpenBSD-5.8-stable, Debian GNU/Linux, and Solaris
> 9, 10, and 11, but tests on all other supported platforms are still
> missing, and of course nothing is wrong with giving OpenBSD and
> Solaris another try if you want to.  I'll do the public release as
> soon as i have test reports from a sufficiently diverse set of
> systems.
> 
> Mandoc 1.13.4 is a regular maintenance release and also introduces
> a small number of new features; here is an extract from the NEWS
> file in the release candidate tarball:
> 
>  * man.conf(5): Design and implement a simpler configuration file format.
>  * man(1): Leverage less(1) -T and :t in a way resembling ctags(1)
>    to jump to the definitions of various terms inside manual pages.
>  * soelim(1): New implementation by Baptiste Daroussin.
>  * pledge(2): Use the OpenBSD privilege limitation syscall when available.
>  * man.cgi(8): Support short URIs like http://man.openbsd.org/mdoc .
>  * mandoc.css: Use one unified stylesheet rather than three different ones.
> 
> For a detailed list of changes, see the NEWS file
> inside the release candidate tarball:
> 
>   http://mdocml.bsd.lv/snapshots/mdocml-1.13.4rc1.tar.gz
> 
> Thank you for your support!
>   Ingo
> 
> 
> P.S.
> It seems likely that this will be the last release needing SQLite
> for database support.  I have started work on removing the dependency
> on SQLite without loss of functionality and without needing any
> replacement, relying on POSIX interfaces only.  So it is likely
> that we will have a 1.14.1 release this autumn that no longer needs
> SQLite.
> 
> Then again, if there is substantial demand, i might maintain the
> 1.13 branch for some time in parallel.  In either case, it seems
> important to me to get 1.13.4 as good and stable as possible to
> have a solid foundation to build on.  The code base itself is
> definitely very solid, it is quite similar to what we will ship in
> the OpenBSD 6.0 release this fall.

more(1) doesn't have "-T" option.
Patch attached.


-- 
https://www.juef.tk/

[-- Attachment #1.2: mdocml-do_not_use_tag_file_more.patch --]
[-- Type: text/plain, Size: 579 bytes --]

diff -Naur mdocml-1.13.4-a/main.c mdocml-1.13.4-b/main.c
--- mdocml-1.13.4-a/main.c	2016-07-09 14:15:54.000000000 +0300
+++ mdocml-1.13.4-b/main.c	2016-07-09 17:19:16.138769535 +0300
@@ -1055,11 +1055,11 @@
 			break;
 	}
 
-	/* For more(1) and less(1), use the tag file. */
+	/* For less(1), use the tag file. */
 
 	if ((cmdlen = strlen(argv[0])) >= 4) {
 		cp = argv[0] + cmdlen - 4;
-		if (strcmp(cp, "less") == 0 || strcmp(cp, "more") == 0) {
+		if (strcmp(cp, "less") == 0) {
 			argv[argc++] = mandoc_strdup("-T");
 			argv[argc++] = tag_files->tfn;
 		}

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  parent reply	other threads:[~2016-07-09 14:28 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   ` Svyatoslav Mishyn Crux [this message]
2016-07-10 14:08     ` call for testing: mandoc-1.13.4 release candidate 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
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=20160709142813.GA13260@k8 \
    --to=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).