sbase/cut.1

.Dd January 22, 2015
.Dt CUT 1 sbase\-VERSION
.Os
.Sh NAME
.Nm cut
.Nd extract columns of data
.Sh SYNOPSIS
.Nm
.Fl b Ar list
.Op Fl n
.Op Ar file ...
.Nm
.Fl c Ar list
.Op Ar file ...
.Nm
.Fl f Ar list
.Op Fl d Ar delim
.Op Fl s
.Op Ar file ...
.Sh DESCRIPTION
.Nm
out bytes, characters or delimited fields from each line of
.Ar file
and write to stdout.
.Pp
If no
.Ar file
is given or
.Ar file
is '-',
.Nm
reads from stdin.
.Pp
.Ar list
is a comma or space separated list of numbers and ranges starting
from 1. Ranges have the form 'N-M'. If N or M is missing,
beginning or end of line is assumed. Numbers and ranges
may be repeated, overlapping and in any order.
.Pp
Selected input is written in the same order it is read
and is written exactly once.
.Sh OPTIONS
.Bl -tag -width Ds
.It Fl b Ar list | Fl c Ar list
.Ar list
specifies byte | character positions.
.It Fl n
Do not split multibyte characters. A character is written when its
last byte is selected.
.It Fl f Ar list
.Ar list
specifies field numbers. Lines not containing field
delimiters are passed through, unless
.Fl s
is specified.
.It Fl d Ar delim
Use
.Ar delim
as field delimiter, which can be an arbitrary string. Default is '\et'.
.It Fl s
Suppress lines not containing field delimiters.
.El
.Sh STANDARDS
The
.Nm
utility is compliant with the
.St -p1003.1-2008
specification.
.Pp
The possibility of separating numbers and ranges with a space
and specifying multibyte delimiters of arbitrary length is an extension to that specification.
Add UTF-8-delimiter-support to cut(1) Now you can specify a multibyte-delimiter to cut, which should definitely be possible for the end-user (Fuck POSIX). Looking at GNU/coreutils' cut(1)[0], which basically ignores the difference between characters and bytes, the -n-option and which is bloated as hell, one has to wonder why they are still default. This is insane! Things like this personally keep me motivated to make sbase better every day. [0]: http://git.savannah.gnu.org/gitweb/?p=coreutils.git;a=blob;f=src/cut.c;hb=HEAD NSFW! You have been warned. 2015-01-22 06:32:50 -05:00			`.Dd January 22, 2015`
Add mandoc-manpage for cut(1) and clean up code and mark it as finished in README. 2015-01-18 05:30:31 -05:00			`.Dt CUT 1 sbase\-VERSION`
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			`.Os`
Add mandoc-manpage for cut(1) and clean up code and mark it as finished in README. 2015-01-18 05:30:31 -05:00			`.Sh NAME`
			`.Nm cut`
			`.Nd extract columns of data`
			`.Sh SYNOPSIS`
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			`.Nm`
Add mandoc-manpage for cut(1) and clean up code and mark it as finished in README. 2015-01-18 05:30:31 -05:00			`.Fl b Ar list`
			`.Op Fl n`
			`.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			`.Nm`
Add mandoc-manpage for cut(1) and clean up code and mark it as finished in README. 2015-01-18 05:30:31 -05:00			`.Fl c Ar list`
			`.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			`.Nm`
Add mandoc-manpage for cut(1) and clean up code and mark it as finished in README. 2015-01-18 05:30:31 -05:00			`.Fl f Ar list`
			`.Op Fl d Ar delim`
			`.Op Fl s`
			`.Op Ar file ...`
			`.Sh DESCRIPTION`
			`.Nm`
			`out bytes, characters or delimited fields from each line of`
			`.Ar file`
			`and write to stdout.`
			`.Pp`
			`If no`
			`.Ar file`
			`is given or`
			`.Ar file`
			`is '-',`
			`.Nm`
			`reads from stdin.`
			`.Pp`
			`.Ar list`
			`is a comma or space separated list of numbers and ranges starting`
			`from 1. Ranges have the form 'N-M'. If N or M is missing,`
			`beginning or end of line is assumed. Numbers and ranges`
			`may be repeated, overlapping and in any order.`
			`.Pp`
			`Selected input is written in the same order it is read`
			`and is written exactly once.`
			`.Sh OPTIONS`
			`.Bl -tag -width Ds`
			`.It Fl b Ar list \| Fl c Ar list`
			`.Ar list`
			`specifies byte \| character positions.`
			`.It Fl n`
			`Do not split multibyte characters. A character is written when its`
			`last byte is selected.`
			`.It Fl f Ar list`
			`.Ar list`
			`specifies field numbers. Lines not containing field`
			`delimiters are passed through, unless`
			`.Fl s`
			`is specified.`
			`.It Fl d Ar delim`
Refactor cut.1 and cut.c and reflect recent changes to the role of "delim". 2015-01-24 16:53:37 -05:00			`Use`
Add mandoc-manpage for cut(1) and clean up code and mark it as finished in README. 2015-01-18 05:30:31 -05:00			`.Ar delim`
Refactor cut.1 and cut.c and reflect recent changes to the role of "delim". 2015-01-24 16:53:37 -05:00			`as field delimiter, which can be an arbitrary string. Default is '\et'.`
Add mandoc-manpage for cut(1) and clean up code and mark it as finished in README. 2015-01-18 05:30:31 -05:00			`.It Fl s`
Add cut(1) 2013-10-08 15:39:08 -04:00			`Suppress lines not containing field delimiters.`
Add mandoc-manpage for cut(1) and clean up code and mark it as finished in README. 2015-01-18 05:30:31 -05:00			`.El`
			`.Sh STANDARDS`
			`The`
			`.Nm`
			`utility is compliant with the`
			`.St -p1003.1-2008`
			`specification.`
			`.Pp`
			`The possibility of separating numbers and ranges with a space`
Add support for arbitrary length delimiters in cut(1) Having multibyte delimiters is not enough. For full flexibility, the possiblity of cutting input lines with arbitrary length delimiters is the real deal. Given this functionality, it only sounds reasonable to also add support to resolve escapes. Thanks to Truls Becken for making the suggestion and designing such a flexible cut(1)-implementation! 2015-01-22 14:19:48 -05:00			`and specifying multibyte delimiters of arbitrary length is an extension to that specification.`