| Age | Commit message (Collapse) | Author |
|---|
|
ok jasper@ millert@
|
|
would insert 16000 letter l'. Going over the line limit makes no sense
so limit it's repetition and prevent the hang in the process.
ok guenther
|
|
specifically, rewrite them to permit some markup in the column headers,
and use "Ta" instead of literal tabs; mandoc does not currently match groff
100%, but a mandoc fix may be some time off, and we've gone enough releases
with poorly formatting column lists.
in some cases i have rewritten the lists as -tag, where -column made
little sense.
|
|
|
|
has changed to conform with modern groff releases.
diff for route6d(8) written mostly by schwarze@, with lots of useful
advice from jmc@.
ok jmc@, schwarze@
|
|
noticed by and ok kevlo@
|
|
no binary change.
sure @deraadt
|
|
feedback from Dan Harnett
OK deraadt@
|
|
revert that part of yesterday's diffs;
|
|
- remove some old groff workarounds in SYNOPSIS
- avoid "Op ... Oc" constructions
- avoid empty Sq/Dq
- change some incorrect Xr
|
|
(parentheses and/or square brackets), both modern groff and mandoc first
output those leading delimiters as plain text, then start the macro scope
after these opening delimiters. This is similar to printing trailing
punctuation and trailing closing delimiters on a macro line outside and
after the macro scope. For example, ".Sq ( text )" is "(`text')",
not "`(text)'". Thus, we now need to quote leading opening delimiters
when we want them inside the macro scope.
These are the cases in src/bin.
"makes sense" jmc@
|
|
sh.1: add ]] and `name' to the list; additionally document the commands
`select' (requested by Ross L Richardson) and [[
ok millert sobrado
|
|
millert@ ok some time ago.
|
|
this fixes pr 6195. diff from manuel giraud, thanks.
ok kili@
|
|
|
|
ok guenther@
|
|
|
|
c_sh.c part from sobrado;
ok millert guenther
|
|
when they shouldn't. originally from mksh but modified to handle the case
when the expr is quoted as noticed by halex@.
input from guenther@ and halex@, millert@ ok
|
|
ok jmc deraadt
|
|
found by and unbreaking the build with mandoc(1);
"fine" jmc@ sobrado@
|
|
Please keep in mind that ksh accesses are not O(1) in any sense.
Needed by todd, ok otto, guenther
|
|
ok guenther
|
|
|
|
unmaintainable). these days, people use source. these id's do not provide
any benefit, and do hurt the small install media
(the 33,000 line diff is essentially mechanical)
ok with the idea millert, ok dms
|
|
ok theo, millert@
|
|
vi back-words and emacs kill-region are not completely the same.
ok merdely@, millert@. "Get it in" Darrin Chandler
|
|
Found by Daniel LEVAI
Fix by Darrin Chandler
ok millert@
|
|
have whole paths go away on ^W instead of just the last bit."
"That looks right to me" millert@, "YES kthx bye!" thib@
|
|
|
|
|
|
involving ++ and -- also ran into this. Insufficient checks for end of parse in
the tokenizer made it assume that an lvalue had been found
ok millert otto
|
|
|
|
|
|
lists encounter a name too long for the width of the terminal.
from Matthew Haub, no objections krw@.
|
|
from glob(7) to the shell pages - they have their own glob stuff,
and pointing to glob(7) is just not helpful.
ok millert
|
|
|
|
OK deraadt@ krw@ jmc@ sobrado@
|
|
Make sure ksh builtin test and test(1) do not differ.
From Christiano Farina Haesbaert. ok miod@
|
|
|
|
ok otto@
|
|
the only option is -n, and only one of those is parsed.
diff from Ingo Schwarze
ok otto@ kili@; manpage changes ok jmc@
|
|
match what both POSIX and ksh.1 already describe in regards to set
-e/errexit's behavior in determining when to exit from nonzero return
values.
specifically, the truth values tested as operands to `&&' and `||', as
well as the resulting compound expression itself, along with the truth
value resulting from a negated command (i.e. a pipeline prefixed `!'),
should not make the shell exit when -e is in effect.
issue reported by matthieu.
testing matthieu, naddy.
ok miod (earlier version), otto.
man page ok jmc.
|
|
|
|
the leaked memory is actually reclaimed when the command
finishes but may grow until that happens, e.g. during
command execution.
ok phessler@.
testing sobrado@ jmc@ oga@.
|
|
reported by Thorsten Glaser, thanks.
ok millert@, earlier version miod@
|
|
|
|
|
|
contains a '#' character. Make it also accept the \$ PS1 sequence
(which is supposed to automagically be $ or # depending on the user
running the shell) unless ksh has been started in sh-compatibility
mode.
pointed out by millert@ when I asked why my SUDO_PS1 was not being
honoured; ok millert@
|
|
report and testing by david@; ok millert@ jaredy@
|
