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.
This commit is contained in:
FRIGN
2015-01-22 12:32:50 +01:00
parent dc70eb7976
commit 733b33f1c7
3 changed files with 40 additions and 18 deletions

4
cut.1
View File

@@ -1,4 +1,4 @@
.Dd January 18, 2015
.Dd January 22, 2015
.Dt CUT 1 sbase\-VERSION
.Sh NAME
.Nm cut
@@ -67,4 +67,4 @@ utility is compliant with the
specification.
.Pp
The possibility of separating numbers and ranges with a space
is an extension to that specification.
and specifying multibyte delimiters is an extension to that specification.