summaryrefslogtreecommitdiff
path: root/runtime/doc/xxd.1
diff options
context:
space:
mode:
authorBram Moolenaar <Bram@vim.org>2007-05-05 18:24:42 +0000
committerBram Moolenaar <Bram@vim.org>2007-05-05 18:24:42 +0000
commitc81e5e79a0f2f5c2ac1896fa51cbe47e2e2a8d97 (patch)
tree5211ea86daed8e43c3dd25458e808c3d32100097 /runtime/doc/xxd.1
parent9aae141a6bcfc26bcce352deb8bf34566a3e1be2 (diff)
downloadvim-git-c81e5e79a0f2f5c2ac1896fa51cbe47e2e2a8d97.tar.gz
updated for version 7.1a
Diffstat (limited to 'runtime/doc/xxd.1')
-rw-r--r--runtime/doc/xxd.114
1 files changed, 7 insertions, 7 deletions
diff --git a/runtime/doc/xxd.1 b/runtime/doc/xxd.1
index d6e782a4e..e8f735859 100644
--- a/runtime/doc/xxd.1
+++ b/runtime/doc/xxd.1
@@ -123,7 +123,7 @@ added to file positions found in hexdump.
start at
.RI < seek >
bytes abs. (or rel.) infile offset.
-\fI+ fRindicates that the seek is relative to the current stdin file position
+\fI+ \fRindicates that the seek is relative to the current stdin file position
(meaningless when not reading from stdin). \fI\- \fRindicates that the seek
should be that many characters from the end of the input (or if combined with
\fI+\fR: before the current stdin file position).
@@ -172,17 +172,17 @@ The following examples may help to clarify (or further confuse!)...
Rewind stdin before reading; needed because the `cat' has already read to the
end of stdin.
.br
-\fI% sh \-c "cat > plain_copy; xxd \-s 0 > hex_copy" < file
+\fI% sh \-c "cat > plain_copy; xxd \-s 0 > hex_copy" < file\fR
.PP
Hexdump from file position 0x480 (=1024+128) onwards.
The `+' sign means "relative to the current position", thus the `128' adds to
the 1k where dd left off.
.br
-\fI% sh \-c "dd of=plain_snippet bs=1k count=1; xxd \-s +128 > hex_snippet" < file
+\fI% sh \-c "dd of=plain_snippet bs=1k count=1; xxd \-s +128 > hex_snippet" < file\fR
.PP
Hexdump from file position 0x100 ( = 1024\-768) on.
.br
-\fI% sh \-c "dd of=plain_snippet bs=1k count=1; xxd \-s +\-768 > hex_snippet" < file
+\fI% sh \-c "dd of=plain_snippet bs=1k count=1; xxd \-s +\-768 > hex_snippet" < file\fR
.PP
However, this is a rare situation and the use of `+' is rarely needed.
The author prefers to monitor the effect of xxd with strace(1) or truss(1), whenever \-s is used.
@@ -192,16 +192,16 @@ The author prefers to monitor the effect of xxd with strace(1) or truss(1), when
Print everything but the first three lines (hex 0x30 bytes) of
.BR file .
.br
-\fI% xxd \-s 0x30 file
+\fI% xxd \-s 0x30 file\fR
.PP
.br
Print 3 lines (hex 0x30 bytes) from the end of
.BR file .
.br
-\fI% xxd \-s \-0x30 file
+\fI% xxd \-s \-0x30 file\fR
.PP
.br
-Print 120 bytes as continuous hexdump with 40 octets per line.
+Print 120 bytes as continuous hexdump with 20 octets per line.
.br
\fI% xxd \-l 120 \-ps \-c 20 xxd.1\fR
.br