| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
of the typeset output, tend to make diffs harder to read and provide
bad examples for new-comers to mdoc.
|
| |
|
|
|
| |
PR: docs/13409
Reviewed by: mpp
|
| |
|
|
|
|
|
| |
easier for translation teams.
PR: docs/13418
Submitted by: Alexey Zelkin <phantom@cris.net>
|
| | |
|
| |
|
|
|
| |
getopt in bourne shell is in fact hard. Maybe perl isn't *that* bad
after all...
|
| |
|
|
|
|
|
|
|
| |
Arguments with whitespaces are easy to fix, but in combination with
shell metachars that should not be evaluated it is very hard, probably
impossible to fix without going to a line-oriented solution.
Next time I will believe Henry Spencer when he says "this looks easy
to fix but isn't".
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
parameter that has space in it, both in getopt.c and in the manpage
example.
2) Fix the example in the manpage. The set(1) command is required to
return 0 (POSIX 1003.2, section 3.14.11), so you can't test for
getopt's exit status like the example did:
#! /bin/sh
set -- `getopt abo: $*`
if test $? != 0 # wrong, tests for set's exit status, which is
# always zero, no for getopt(1)'s.
Fixes PR bin/5845, which thought it was getopt's fault, but in fact
the manpage was wrong.
I also updated the example to be more useful and updated the BUGS
section.
PR: bin/5845
|
| |
|
|
| |
posix standard on the topic.
|
| |
|
|
|
|
| |
other mdoc(5) usage errors.
Pointed out by: kuku@physik.rwth-aachen.de (Chris Kukulies)
|
| | |
|
| | |
|
| | |
|
| |
|
