[Bug 215528] vis(1) man page error in option usage
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Fri Dec 23 23:29:39 UTC 2016
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215528
Jamie Landeg-Jones <jamie at dyslexicfish.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jamie at dyslexicfish.net
--- Comment #1 from Jamie Landeg-Jones <jamie at dyslexicfish.net> ---
The -F and -f options are incorrectly specified, as detailed in the attached
fix patch to the manual pages source file.
For convenience, the diff from the resultant text is:
30,38c30,37
< -F foldwidth
< Causes vis to fold output lines to foldwidth columns (default
< 80), like fold(1), except that a hidden newline sequence is
used,
< (which is removed when inverting the file back to its original
< form with unvis(1)). If the last character in the encoded file
< does not end in a newline, a hidden newline sequence is appended
< to the output. This makes the output usable with various
editors
< and other utilities which typically don't work with partial
< lines.
---
> -f Causes vis to fold output lines at N columns (default 80, over‐
> ridden by -F.), like fold(1), except that a hidden newline
> sequence is used, (which is removed when inverting the file back
> to its original form with unvis(1)). If the last character in
> the encoded file does not end in a newline, a hidden newline
> sequence is appended to the output. This makes the output usable
> with various editors and other utilities which typically don't
> work with partial lines.
40c39,40
< -f Same as -F.
---
> -F foldwidth
> Set the column width to foldwidth when using -f.
51,52c51,52
< still doubled and hidden newline sequences inserted if -f or -F
< is selected. When combined with the -f flag, vis becomes like
an
---
> still doubled and hidden newline sequences inserted if -f is
> selected. When combined with the -f flag, vis becomes like an
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-doc
mailing list