source@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: schwarze@mandoc.bsd.lv
To: source@mandoc.bsd.lv
Subject: mandoc: Check that .In is callable and parsed.
Date: Sat, 21 Sep 2024 12:00:28 +0000 (UTC)	[thread overview]
Message-ID: <94fe37e7df1977a7@mandoc.bsd.lv> (raw)

Log Message:
-----------
Check that .In is callable and parsed.
Triggered by a documentation patch from Evan Silberman <evan at jklol dot net>.

I'm not testing yet whether the same applies in the SYNOPSIS section
because there are multiple parsing and formatting differences with groff
in that section.

Modified Files:
--------------
    mandoc/regress/mdoc/In:
        Makefile

Added Files:
-----------
    mandoc/regress/mdoc/In:
        parse.in
        parse.out_ascii
        parse.out_markdown

Revision Data
-------------
Index: Makefile
===================================================================
RCS file: /home/cvs/mandoc/mandoc/regress/mdoc/In/Makefile,v
diff -Lregress/mdoc/In/Makefile -Lregress/mdoc/In/Makefile -u -p -r1.4 -r1.5
--- regress/mdoc/In/Makefile
+++ regress/mdoc/In/Makefile
@@ -1,6 +1,6 @@
-# $OpenBSD: Makefile,v 1.6 2015/02/06 01:07:07 schwarze Exp $
+# $OpenBSD: Makefile,v 1.10 2024/09/21 11:56:36 schwarze Exp $
 
-REGRESS_TARGETS	 = break eos font noarg
+REGRESS_TARGETS	 = break eos font noarg parse
 LINT_TARGETS	 = noarg
 
 .include <bsd.regress.mk>
--- /dev/null
+++ regress/mdoc/In/parse.out_ascii
@@ -0,0 +1,9 @@
+IN-PARSE(2)                   System Calls Manual                  IN-PARSE(2)
+
+N\bNA\bAM\bME\bE
+     I\bIn\bn-\b-p\bpa\bar\brs\bse\be - parsing of include file macros
+
+D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
+     first line p\bpa\bar\bre\ben\bnt\bt <_\ba_\br_\bg_\b1> arg2 c\bch\bhi\bil\bld\bd middle line (<_\ba_\br_\bg>) last line
+
+OpenBSD                       September 21, 2024                       OpenBSD
--- /dev/null
+++ regress/mdoc/In/parse.in
@@ -0,0 +1,13 @@
+.\" $OpenBSD: parse.in,v 1.1 2024/09/21 11:56:36 schwarze Exp $
+.Dd $Mdocdate: September 21 2024 $
+.Dt IN-PARSE 2
+.Os
+.Sh NAME
+.Nm In-parse
+.Nd parsing of include file macros
+.Sh DESCRIPTION
+first line
+.Sy parent In arg1 arg2 Sy child
+middle line
+.In ( arg )
+last line
--- /dev/null
+++ regress/mdoc/In/parse.out_markdown
@@ -0,0 +1,15 @@
+IN-PARSE(2) - System Calls Manual
+
+# NAME
+
+**In-parse** - parsing of include file macros
+
+# DESCRIPTION
+
+first line
+**parent** &lt;*arg1*> arg2 **child**
+middle line
+(&lt;*arg*>)
+last line
+
+OpenBSD - September 21, 2024
--
 To unsubscribe send an email to source+unsubscribe@mandoc.bsd.lv


                 reply	other threads:[~2024-09-21 12:00 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=94fe37e7df1977a7@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).