From: Ingo Schwarze <schwarze@usta.de>
To: tech@mdocml.bsd.lv
Subject: Re: mdocml: Make -man -Tascii not break within literal lines
Date: Sun, 16 Jan 2011 04:53:42 +0100 [thread overview]
Message-ID: <20110116035342.GE28336@iris.usta.de> (raw)
In-Reply-To: <201101121523.p0CFNQNx028921@krisdoz.my.domain>
Hi Kristaps,
this one caused my regression test suite to segfault - specifically
the test having a blank line inside literal context died.
kristaps@mdocml.bsd.lv wrote on Wed, Jan 12, 2011 at 10:23:26AM -0500:
> Log Message:
> -----------
> Make -man -Tascii not break within literal lines, e.g.,
>
> .nf
> .B hello world
> .fi
>
> Also, clean up the print_man_node() function a little bit. This problem
> has long since been in the TODO and was recently noted again by Brad
> Smith. The -T[x]html fix will follow...
>
> Modified Files:
> --------------
> mdocml:
> man_term.c
>
> Revision Data
> -------------
> Index: man_term.c
> ===================================================================
> RCS file: /usr/vhosts/mdocml.bsd.lv/cvs/mdocml/man_term.c,v
> retrieving revision 1.96
> retrieving revision 1.97
> diff -Lman_term.c -Lman_term.c -u -p -r1.96 -r1.97
> --- man_term.c
> +++ man_term.c
> @@ -855,23 +855,31 @@ print_man_node(DECL_ARGS)
> size_t rm, rmax;
> int c;
>
> - c = 1;
> -
> switch (n->type) {
> case(MAN_TEXT):
> + /*
> + * If we have a blank line, output a vertical space.
> + * If we have a space as the first character, break
> + * before printing the line's data.
> + */
> if ('\0' == *n->string) {
> term_vspace(p);
> break;
Here is the problem.
After your refactoring, this should now read "return".
OK?
Index: man_term.c
===================================================================
RCS file: /usr/vhosts/mdocml.bsd.lv/cvs/mdocml/man_term.c,v
retrieving revision 1.97
diff -u -p -r1.97 man_term.c
--- man_term.c 12 Jan 2011 15:23:25 -0000 1.97
+++ man_term.c 16 Jan 2011 03:49:36 -0000
@@ -1,6 +1,6 @@
/* $Id: man_term.c,v 1.97 2011/01/12 15:23:25 kristaps Exp $ */
/*
- * Copyright (c) 2008, 2009, 2010 Kristaps Dzonsons <kristaps@bsd.lv>
+ * Copyright (c) 2008, 2009, 2010, 2011 Kristaps Dzonsons <kristaps@bsd.lv>
* Copyright (c) 2010, 2011 Ingo Schwarze <schwarze@openbsd.org>
*
* Permission to use, copy, modify, and distribute this software for any
@@ -864,7 +864,7 @@ print_man_node(DECL_ARGS)
*/
if ('\0' == *n->string) {
term_vspace(p);
- break;
+ return;
} else if (' ' == *n->string && MAN_LINE & n->flags)
term_newln(p);
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
next parent reply other threads:[~2011-01-16 3:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201101121523.p0CFNQNx028921@krisdoz.my.domain>
2011-01-16 3:53 ` Ingo Schwarze [this message]
2011-01-16 9:56 ` Kristaps Dzonsons
2011-01-16 20:02 ` 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=20110116035342.GE28336@iris.usta.de \
--to=schwarze@usta.de \
--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).