mirror of
https://codeberg.org/libreboot/lbmk.git
synced 2026-03-25 13:29:03 +02:00
e9a910b33c
i currently use the output of sha512sum in several places of xbmk, which is a bit unreliable in case output changes. other cases where i use util outputs in variables are probably reliable, because i'm using mostly posix utilities in those. to mitigate this, i now import suckless sbase, which has a reasonable sha512sum implementation. *every* binary it builds is being placed in build.list, because i'll probably start using more of them. for example, i may start modifying the "date" implementation, adding the GNU-specific options that i need as mentioned on init.sh i'm importing it in util/ because the sha512sum util is needed for verifying project sources, so if sbase itself is a "project source", that means we can into a chicken and egg bootstrapping problem. this is sbase at revision: 055cc1ae1b3a13c3d8f25af0a4a3316590efcd48 Signed-off-by: Leah Rowe <leah@libreboot.org>
57 lines
1.0 KiB
Groff
57 lines
1.0 KiB
Groff
.Dd October 8, 2015
|
|
.Dt COLS 1
|
|
.Os sbase
|
|
.Sh NAME
|
|
.Nm cols
|
|
.Nd columnize output
|
|
.Sh SYNOPSIS
|
|
.Nm
|
|
.Op Fl c Ar num
|
|
.Op Ar file ...
|
|
.Sh DESCRIPTION
|
|
.Nm
|
|
reads each
|
|
.Ar file
|
|
in sequence and writes them to stdout, in as many vertical
|
|
columns as will fit in
|
|
.Ar num
|
|
character columns.
|
|
If no
|
|
.Ar file
|
|
is given,
|
|
.Nm
|
|
reads from stdin.
|
|
.Pp
|
|
By default
|
|
.Nm cols
|
|
tries to figure out the width of the output device.
|
|
If that fails, it defaults to 65 chars.
|
|
.Sh OPTIONS
|
|
.Bl -tag -width Ds
|
|
.It Fl c Ar num
|
|
Set maximum number of character columns to
|
|
.Ar num ,
|
|
unless input lines exceed this limit.
|
|
.El
|
|
.Sh ENVIRONMENT
|
|
.Bl -tag -width Ds
|
|
.It COLUMNS
|
|
The width of the output device.
|
|
.El
|
|
.Sh HISTORY
|
|
.Nm
|
|
is similar to
|
|
.Xr mc 1
|
|
in Plan 9. It was renamed to
|
|
.Nm
|
|
to avoid the name collision with the popular file manager
|
|
Midnight Commander.
|
|
.Sh CAVEATS
|
|
This implementation of
|
|
.Nm
|
|
assumes that each UTF-8 code point occupies one character cell,
|
|
and thus mishandles TAB characters (among others).
|
|
.Pp
|
|
.Nm
|
|
currently mangles files which contain embedded NULs.
|