From c8c7d0edaa834d7ca474c422447ec3dd1a9c1e59 Mon Sep 17 00:00:00 2001 From: Joerg Sonnenberger Date: Tue, 24 Mar 2009 00:17:25 +0000 Subject: [PATCH] Remove physical markup. --- usr.bin/indent/indent.1 | 9 +-------- 1 file changed, 1 insertion(+), 8 deletions(-) diff --git a/usr.bin/indent/indent.1 b/usr.bin/indent/indent.1 index a7019748d3e..d577c76b0de 100644 --- a/usr.bin/indent/indent.1 +++ b/usr.bin/indent/indent.1 @@ -1,4 +1,4 @@ -.\" $NetBSD: indent.1,v 1.17 2003/08/07 11:14:08 agc Exp $ +.\" $NetBSD: indent.1,v 1.18 2005/09/11 23:17:34 wiz Exp $ .\" .\" Copyright (c) 1980, 1990, 1993 .\" The Regents of the University of California. All rights reserved. @@ -210,7 +210,6 @@ Default: Specifying .Fl \&bl lines up compound statements like this: -.ne 4 .Bd -literal -offset indent if (...) { @@ -221,7 +220,6 @@ if (...) Specifying .Fl \&br (the default) makes them look like this: -.ne 3 .Bd -literal -offset indent if (...) { code @@ -246,7 +244,6 @@ is for these comments to start in the same column as those on code. .It Fl cdb , ncdb Enables (disables) the placement of comment delimiters on blank lines. With this option enabled, comments look like this: -.ne 3 .Bd -literal -offset indent /* * this is a comment @@ -365,13 +362,11 @@ position just after the left paren. For example, here is how a piece of continued code looks with .Fl nlp in effect: -.ne 2 .Bd -literal -offset indent p1 = first_procedure(second_procedure(p2, p3), \ \ third_procedure(p4,p5)); .Ed .Pp -.ne 5 With .Fl lp in effect (the default) the code looks somewhat clearer: @@ -380,7 +375,6 @@ p1\ =\ first_procedure(second_procedure(p2,\ p3), \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ third_procedure(p4,p5)); .Ed .Pp -.ne 5 Inserting two more newlines we get: .Bd -literal -offset indent p1\ =\ first_procedure(second_procedure(p2, @@ -558,7 +552,6 @@ command appeared in has even more switches than .Xr ls 1 . .Pp -.ne 5 A common mistake that often causes grief is typing: .Pp .Dl indent *.c -- 2.11.4.GIT