| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Noticed by: Dave Hart
MFC plans: after checking with re@
|
|
|
|
|
|
|
|
|
|
|
| |
1) An unquoted space is always a separator, even when not "in_arg".
2) When a new destination buffer must be allocated during variable
substitution, only copy data from the active buffer to the new
one when we *are* "in_arg".
These were noticed when testing variable-substitution of variables
which have null values, and are not inside quoted strings...
MFC plans: after a few days, and re@ approval...
|
|
|
|
|
| |
Approved by: re (blanket)
OK'ed by: gad
|
|
|
|
|
|
|
|
| |
was a separator character immediately before it. This wasn't likely to
happen in #-lines, but we might as well get it right. Also fix it so
that "" and "" will create a zero-length argument.
Approved by: re (blanket `env')
|
|
|
|
|
| |
Noticed by: Matthew D Fuller
Approved by: re (blanket `env')
|
|
|
|
|
|
|
|
| |
start with a '/', they are more supported (by POSIX and SUSv3) than
filenames which have an '=' in them.
Noticed by: tjr
Approved by: re (blanket `env')
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
apart a string, and supports some text substitutions. This can be
used to provide all the flexibility (and more!) that was lost by recent
changes to how the kernel parses #!-lines in shell scripts.
The '-P' option provides a way to specify an alternate set of directories
to use when searching for the 'utility' program to run. This way you can
be sure what directories are used for that search, without changing the
value of PATH that the user has set. Note that on FreeBSD 6.0, this
option is worthless unless the '-S' option is also used.
Approved by: re (blanket `env')
|
|
|
|
|
|
|
| |
without checking it for an equals-sign. If it starts with a slash, then
it cannot be a request to set the value of a valid environment variable.
Approved by: re (blanket `env')
|
|
|
|
|
|
|
| |
it does not happen until all single-letter options are processed. This will
be important for the -S option, which will be coming soon.
Approved by: re (blanket `env')
|
|
|
|
|
|
|
| |
it is doing, and what order it does them. This will be much more useful as
more options are added.
Approved by: re (blanket `env')
|
| |
|
| |
|
| |
|
|
|
|
| |
to the .Nm macro.
|
|
|
|
| |
in keeping them together. Mention that printenv is obsolescent.
|
|
|
|
|
|
|
|
|
| |
Add some constness to avoid some warnings.
Remove use register keyword.
Deal with missing/unneeded extern/prototypes.
Some minor type changes/casts to avoid warnings.
Reviewed by: md5
|
|
|
|
| |
Compatibility section of the manual page.
|
|
|
|
|
|
|
|
|
|
| |
executes in the usage() message and manual page. Use "utility" instead of
"command" in both places to emphasise that shell builtins etc. will not work,
and to be consistent with the terminology used by POSIX.
PR: 39210
Submitted by: Danny J. Zerkel <dzerkel@columbus.rr.com>
MFC after: 1 week
|
| |
|
|
|
|
|
|
| |
is to put a copyright in the object file.
Submitted by: bde
|
|
|
|
|
|
|
| |
Fix env(1)'s exit status to conform with SUSv3.
Submitted by: Tim Robbins <tim@robbins.dropbear.id.au>
MFC after: 2 weeks
|
|
|
|
| |
help the GCC3 transition and CURRENT in general.
|
|
|
|
|
|
| |
where necessary.
Submitted by: Mike Barcroft <mike@q9media.com>
|
|
|
|
|
|
|
|
|
| |
recommended option in the manpage, but the - option remains for
backward compatibility and is documented as such.
PR: 13363
Reported by: James Howard <howardjp@wam.umd.edu>
Reviewed by: bde
|
| |
|
| |
|
|
|
|
| |
posix standard on the topic.
|
|
|