sbase/env.1

.Dd 2015-10-08
.Dt ENV 1
.Os sbase
.Sh NAME
.Nm env
.Nd modify the environment, then print it or run a command
.Sh SYNOPSIS
.Nm
.Op Fl i
.Oo Fl u Ar var Oc ...
.Oo Ar var Ns = Ns Ar value Oc ...
.Oo Ar cmd Oo arg ... Oc Oc
.Sh DESCRIPTION
.Nm
unsets each
.Ar var ,
then adds or sets each
.Ar ( var , value )
tuple in the environment.
.Pp
If
.Ar cmd
is given, it is executed in this new environment;
otherwise, the modified environment is printed to stdout.
.Sh OPTIONS
.Bl -tag -width Ds
.It Fl i
Completely ignore the existing environment and execute
.Ar cmd
only with each
.Ar ( var , value )
tuple specified.
.It Fl u Ar var
Unset
.Ar var
in the environment.
.El
.Sh SEE ALSO
.Xr printenv 1 ,
.Xr putenv 3 ,
.Xr environ 7
.Sh STANDARDS
The
.Nm
utility is compliant with the
.St -p1003.1-2013
specification.
.Pp
The
.Op Fl u
flag 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 ENV 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 mandoc-manpage for env(1) and mark it as finished in the README. 2015-01-23 18:22:06 -05:00			`.Sh NAME`
			`.Nm env`
			`.Nd modify the environment, then print it or run a command`
			`.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 env(1) and mark it as finished in the README. 2015-01-23 18:22:06 -05:00			`.Op Fl i`
Audit env(1) 1) Shorten synopsis and reflect this in the manual 2) Use argv0 in usage() 3) Decrement argc in argv-loop for consistency 4) Make it clearer which error-code results from which errno in enprintf 5) Use idiomatic for-loop also for environ. Don't increment these pointers in the loop itself! 2015-03-02 08:50:43 -05:00			`.Oo Fl u Ar var Oc ...`
			`.Oo Ar var Ns = Ns Ar value Oc ...`
Add mandoc-manpage for env(1) and mark it as finished in the README. 2015-01-23 18:22:06 -05:00			`.Oo Ar cmd Oo arg ... Oc Oc`
			`.Sh DESCRIPTION`
			`.Nm`
			`unsets each`
Audit env(1) 1) Shorten synopsis and reflect this in the manual 2) Use argv0 in usage() 3) Decrement argc in argv-loop for consistency 4) Make it clearer which error-code results from which errno in enprintf 5) Use idiomatic for-loop also for environ. Don't increment these pointers in the loop itself! 2015-03-02 08:50:43 -05:00			`.Ar var ,`
Add mandoc-manpage for env(1) and mark it as finished in the README. 2015-01-23 18:22:06 -05:00			`then adds or sets each`
Audit env(1) 1) Shorten synopsis and reflect this in the manual 2) Use argv0 in usage() 3) Decrement argc in argv-loop for consistency 4) Make it clearer which error-code results from which errno in enprintf 5) Use idiomatic for-loop also for environ. Don't increment these pointers in the loop itself! 2015-03-02 08:50:43 -05:00			`.Ar ( var , value )`
Add mandoc-manpage for env(1) and mark it as finished in the README. 2015-01-23 18:22:06 -05:00			`tuple in the environment.`
			`.Pp`
Tar compiles on BSD, thanks Roberto E. Vargas Caballero. Also remove tons of trailing whitespace. 2013-07-20 01:27:42 -04:00			`If`
Add mandoc-manpage for env(1) and mark it as finished in the README. 2015-01-23 18:22:06 -05:00			`.Ar cmd`
			`is given, it is executed in this new environment;`
			`otherwise, the modified environment is printed to stdout.`
			`.Sh OPTIONS`
			`.Bl -tag -width Ds`
			`.It Fl i`
			`Completely ignore the existing environment and execute`
			`.Ar cmd`
			`only with each`
Audit env(1) 1) Shorten synopsis and reflect this in the manual 2) Use argv0 in usage() 3) Decrement argc in argv-loop for consistency 4) Make it clearer which error-code results from which errno in enprintf 5) Use idiomatic for-loop also for environ. Don't increment these pointers in the loop itself! 2015-03-02 08:50:43 -05:00			`.Ar ( var , value )`
Be more consistent in env.1 2015-01-23 18:24:42 -05:00			`tuple specified.`
Audit env(1) 1) Shorten synopsis and reflect this in the manual 2) Use argv0 in usage() 3) Decrement argc in argv-loop for consistency 4) Make it clearer which error-code results from which errno in enprintf 5) Use idiomatic for-loop also for environ. Don't increment these pointers in the loop itself! 2015-03-02 08:50:43 -05:00			`.It Fl u Ar var`
Add -u-flag to env.1-manpage which I forgot to add earlier. 2015-01-24 17:04:40 -05:00			`Unset`
Audit env(1) 1) Shorten synopsis and reflect this in the manual 2) Use argv0 in usage() 3) Decrement argc in argv-loop for consistency 4) Make it clearer which error-code results from which errno in enprintf 5) Use idiomatic for-loop also for environ. Don't increment these pointers in the loop itself! 2015-03-02 08:50:43 -05:00			`.Ar var`
Add -u-flag to env.1-manpage which I forgot to add earlier. 2015-01-24 17:04:40 -05:00			`in the environment.`
Add mandoc-manpage for env(1) and mark it as finished in the README. 2015-01-23 18:22:06 -05:00			`.El`
			`.Sh SEE ALSO`
			`.Xr printenv 1 ,`
			`.Xr putenv 3 ,`
			`.Xr environ 7`
			`.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 mandoc-manpage for env(1) and mark it as finished in the README. 2015-01-23 18:22:06 -05:00			`specification.`
			`.Pp`
			`The`
			`.Op Fl u`
			`flag is an extension to that specification.`