sbase/tail.1

.Dd 2015-10-08
.Dt TAIL 1
.Os sbase
.Sh NAME
.Nm tail
.Nd display final lines of files
.Sh SYNOPSIS
.Nm
.Op Fl f
.Op Fl c Ar num | Fl m Ar num | Fl n Ar num | Fl Ns Ar num
.Op Ar file ...
.Sh DESCRIPTION
.Nm
writes the last 10 lines of each
.Ar file
to stdout. If no
.Ar file
is given,
.Nm
reads from stdin.
.Sh OPTIONS
.Bl -tag -width Ds
.It Fl c Ar num | Fl m Ar num | Fl n Ar num | Fl Ns Ar num
Display final
.Ar num
bytes | characters | lines |
lines. If
.Ar num
begins with '+'
it is an offset from the beginning of each
.Ar file .
If
.Ar num
begins with '-' it is as if no sign was given. The default is 10 lines.
.It Fl f
If one
.Ar file
is specified, append lines to output as
.Ar file
grows.
.El
.Sh SEE ALSO
.Xr head 1
.Sh STANDARDS
The
.Nm
utility is compliant with the
.St -p1003.1-2013
specification.
.Pp
The
.Op Fl Ns Ar num
syntax is an extension to that specification.
Use ISO-date-format in manpages The one specified by mdoc is hard to read for non-native speakers from countries which read the date day-first (like Germany, Greece, North-Korea, Swamp,...). This is also consistent with how we generally specify dates at suckless.org. 2015-10-08 11:15:08 -04:00			`.Dd 2015-10-08`
remove sbase-VERSION from man page, fix sponge.1 date 2015-01-31 08:20:02 -05:00			`.Dt TAIL 1`
Add .Os sbase and sed replace to .Os sbase $(VERSION) in make install 2015-01-31 14:37:03 -05:00			`.Os sbase`
add some mandoc pages and fix some warnings - add .Os, it is mandatory. - don't redeclare .Nm when it's not needed. - fix some warnings (checked with mandoc -Tlint). - remove some leftover old stuff. 2015-01-30 15:17:58 -05:00			`.Sh NAME`
			`.Nm tail`
			`.Nd display final lines of files`
			`.Sh SYNOPSIS`
			`.Nm`
Refactor tail(1) manpage and update README It's not finished yet. We still need the c-flag. 2015-02-09 10:26:17 -05:00			`.Op Fl f`
tail: Process bytes with -c option, and add -m option for runes POSIX says that -c specifies a number of bytes, not characters. This flag is commonly used by scripts that operate on binary files to things like extract a header. Treating the offsets as character offsets will break things in mysterious ways. Instead, add a -m option (chosen to match `wc -m`, which also operates on characters) to handle character offsets. 2017-07-03 17:58:52 -04:00			`.Op Fl c Ar num \| Fl m Ar num \| Fl n Ar num \| Fl Ns Ar num`
Refactor tail(1) manpage and update README It's not finished yet. We still need the c-flag. 2015-02-09 10:26:17 -05:00			`.Op Ar file ...`
add some mandoc pages and fix some warnings - add .Os, it is mandatory. - don't redeclare .Nm when it's not needed. - fix some warnings (checked with mandoc -Tlint). - remove some leftover old stuff. 2015-01-30 15:17:58 -05:00			`.Sh DESCRIPTION`
			`.Nm`
Refactor tail(1) manpage and update README It's not finished yet. We still need the c-flag. 2015-02-09 10:26:17 -05:00			`writes the last 10 lines of each`
			`.Ar file`
			`to stdout. If no`
fix mandoc warnings - sort references in SEE ALSO section to section number, name. - cols.1: proper order of sections. - wrap lines to max 79 column length. 2015-01-31 08:43:27 -05:00			`.Ar file`
			`is given,`
			`.Nm`
			`reads from stdin.`
add some mandoc pages and fix some warnings - add .Os, it is mandatory. - don't redeclare .Nm when it's not needed. - fix some warnings (checked with mandoc -Tlint). - remove some leftover old stuff. 2015-01-30 15:17:58 -05:00			`.Sh OPTIONS`
			`.Bl -tag -width Ds`
tail: Process bytes with -c option, and add -m option for runes POSIX says that -c specifies a number of bytes, not characters. This flag is commonly used by scripts that operate on binary files to things like extract a header. Treating the offsets as character offsets will break things in mysterious ways. Instead, add a -m option (chosen to match `wc -m`, which also operates on characters) to handle character offsets. 2017-07-03 17:58:52 -04:00			`.It Fl c Ar num \| Fl m Ar num \| Fl n Ar num \| Fl Ns Ar num`
Make wording more consistent in head.1 and tail.1 2015-02-09 14:04:54 -05:00			`Display final`
Add c-flag to tail(1) and refactor manpage and mark it as finished in README. 2015-02-09 12:38:41 -05:00			`.Ar num`
tail: Process bytes with -c option, and add -m option for runes POSIX says that -c specifies a number of bytes, not characters. This flag is commonly used by scripts that operate on binary files to things like extract a header. Treating the offsets as character offsets will break things in mysterious ways. Instead, add a -m option (chosen to match `wc -m`, which also operates on characters) to handle character offsets. 2017-07-03 17:58:52 -04:00			`bytes \| characters \| lines \|`
Small tail(1) manpage fix 2015-02-09 13:01:35 -05:00			`lines. If`
Add c-flag to tail(1) and refactor manpage and mark it as finished in README. 2015-02-09 12:38:41 -05:00			`.Ar num`
Small tail(1) manpage fix 2015-02-09 13:01:35 -05:00			`begins with '+'`
			`it is an offset from the beginning of each`
Add c-flag to tail(1) and refactor manpage and mark it as finished in README. 2015-02-09 12:38:41 -05:00			`.Ar file .`
			`If`
			`.Ar num`
Audit tail(1) 1) Specify default in manpage under flag. 2) Boolean and return value style fixes. 3) argv-argc-centric loop. 4) No need to check for argc == 1 before the fflag-subroutine. 5) Remove indentation. 6) Empty line before return. 2015-03-17 18:24:43 -04:00			`begins with '-' it is as if no sign was given. The default is 10 lines.`
Refactor tail(1) manpage and update README It's not finished yet. We still need the c-flag. 2015-02-09 10:26:17 -05:00			`.It Fl f`
			`If one`
			`.Ar file`
			`is specified, append lines to output as`
			`.Ar file`
			`grows.`
tail.1: fix list 2015-01-30 15:49:32 -05:00			`.El`
add some mandoc pages and fix some warnings - add .Os, it is mandatory. - don't redeclare .Nm when it's not needed. - fix some warnings (checked with mandoc -Tlint). - remove some leftover old stuff. 2015-01-30 15:17:58 -05:00			`.Sh SEE ALSO`
			`.Xr head 1`
Add c-flag to tail(1) and refactor manpage and mark it as finished in README. 2015-02-09 12:38:41 -05:00			`.Sh STANDARDS`
			`The`
			`.Nm`
			`utility is compliant with the`
POSIX 2013 audit Mostly manpage-shuffling according to the changes in the corrigendum, wording changes and more idiomatic expressions. All this is finished up by marking the POSIX 2013 conformant tools with .St -p1003.1-2013 which is not available in older mandoc builds or nroff, but which reflects what we actually did, so who cares? This is a huge step and it's not far until we can release sbase 0.1. 2015-03-27 12:22:48 -04:00			`.St -p1003.1-2013`
Add c-flag to tail(1) and refactor manpage and mark it as finished in README. 2015-02-09 12:38:41 -05:00			`specification.`
Amend STANDARDS section in tail.1 2015-02-09 13:02:39 -05:00			`.Pp`
Remove judging word from head.1 and tail.1 as well If it's obsolete, why include it? No, the point here is that the ARGNUM-syntax has it's place among us fellow neckbeards. Let's not degrade it. 2015-03-13 18:54:13 -04:00			`The`
tail: Add -num to usage and fix manpage to align with head.1 2015-03-05 03:13:42 -05:00			`.Op Fl Ns Ar num`
			`syntax is an extension to that specification.`