summaryrefslogtreecommitdiffstats
path: root/usr.bin/file
diff options
context:
space:
mode:
authorsheldonh <sheldonh@FreeBSD.org>2000-03-01 12:20:22 +0000
committersheldonh <sheldonh@FreeBSD.org>2000-03-01 12:20:22 +0000
commit49c4458c80d7fc0c739164002a85966499593dbf (patch)
tree7324d2cb3e29b7c8220abd41fce86411f633eddc /usr.bin/file
parent56aefdcd1008df3702556867ce63eb3fc801508b (diff)
downloadFreeBSD-src-49c4458c80d7fc0c739164002a85966499593dbf.zip
FreeBSD-src-49c4458c80d7fc0c739164002a85966499593dbf.tar.gz
Remove single-space hard sentence breaks. These degrade the quality
of the typeset output, tend to make diffs harder to read and provide bad examples for new-comers to mdoc.
Diffstat (limited to 'usr.bin/file')
-rw-r--r--usr.bin/file/file.13
-rw-r--r--usr.bin/file/magic.521
2 files changed, 16 insertions, 8 deletions
diff --git a/usr.bin/file/file.1 b/usr.bin/file/file.1
index bff4b99..e4cef28 100644
--- a/usr.bin/file/file.1
+++ b/usr.bin/file/file.1
@@ -330,7 +330,8 @@ from his public-domain
program, and are not covered by the above restrictions.
.Sh BUGS
There must be a better way to automate the construction of the Magic
-file from all the glop in Magdir. What is it?
+file from all the glop in Magdir.
+What is it?
Better yet, the magic file should be compiled into binary (say,
.Xr ndbm 3
or, better yet, fixed-length
diff --git a/usr.bin/file/magic.5 b/usr.bin/file/magic.5
index 12923ac..30cfff1 100644
--- a/usr.bin/file/magic.5
+++ b/usr.bin/file/magic.5
@@ -96,7 +96,8 @@ that are set in the specified value,
to specify that the value from the file must have clear any of the bits
that are set in the specified value, or
.Em x ,
-to specify that any value will match. If the character is omitted,
+to specify that any value will match.
+If the character is omitted,
it is assumed to be
.Em = .
.It ""
@@ -158,21 +159,27 @@ is a
.Em (
then the string after the parenthesis is interpreted as an indirect offset.
That means that the number after the parenthesis is used as an offset in
-the file. The value at that offset is read, and is used again as an offset
-in the file. Indirect offsets are of the form:
+the file.
+The value at that offset is read, and is used again as an offset
+in the file.
+Indirect offsets are of the form:
.Em (x[.[bsl]][+-][y]) .
The value of
.Em x
-is used as an offset in the file. A byte, short or long is read at that offset
+is used as an offset in the file.
+A byte, short or long is read at that offset
depending on the
.Em [bsl]
-type specifier. To that number the value of
+type specifier.
+To that number the value of
.Em y
-is added and the result is used as an offset in the file. The default type
+is added and the result is used as an offset in the file.
+The default type
if one is not specified is long.
.Pp
Sometimes you do not know the exact offset as this depends on the length of
-preceding fields. You can specify an offset relative to the end of the
+preceding fields.
+You can specify an offset relative to the end of the
last uplevel field (of course this may only be done for sublevel tests, i.e.
test beginning with
.Em > Ns ).
OpenPOWER on IntegriCloud