Age | Commit message (Collapse) | Author |
|
don't try to free garbage on cleanup. Fixes problem noticed by david@
|
|
|
|
OK otto@
|
|
that. ok millert@
|
|
longer call shf_fprintf() we don't need to jump through hoops using
shf_sopen/shf_sclose and can simply use str_save.
OK otto@ and tested by several ksh users
|
|
sequences) are detected reset the "pointer to first character in
last line of prompt" and "length of last line of prompt" variables,
just like how it done for \n (the literal character). this fixes
cursor movement for prompts with those sequences embedded within
ok jmc pval
|
|
|
|
ok millert@
|
|
|
|
Verified with aaron@ who did the conversion from man -> mdoc.
|
|
running with strict malloc.conf options. Problem spotted by hshoexer@;
fix by me with some help from millert@.
ok millert@ hshoexer@ krw@ deraadt@
|
|
|
|
to ticks. Since ksh needs things in seconds it then converted them back.
Avoid the silliness and use the getrusage(2) and gettimeofday(2) directly.
With man page help from jmc@
|
|
Bug noticed by otto@.
|
|
values and names via an awk script. OK otto@
|
|
|
|
|
|
sparc64, binary change in lex.o on macppc due to introduction of
dopprompt() prototype. ok millert@
|
|
|
|
|
|
|
|
(we define it away in sys/cdefs.h if it is not supported).
|
|
|
|
Use tc[gs]etattr() instead of [gs]et_tty() abstraction
|
|
|
|
Remove KSH_SA_FLAGS
|
|
|
|
|
|
the #ifdef KSH code is required to make a POSIX sh. From Matthias Kilian
|
|
|
|
First step in making the ksh code easier to read. From Matthias Kilian
|
|
- grammar, punctuation, xref, mdoc tweaks
- sort keywords
- indent example displays
- minimize against diffing between sh.1tbl
- document set -o sh
- tweak the displays of some editing and builtin commands
- rework some operator descriptions
ok jmc
|
|
- add missing variable $ signs
- add the IFS example mentioned in the manpage as a test
based on diff from Thorsten Glaser
ok millert
|
|
the actual expression that caused the error. OK otto@
|
|
|
|
set -o csh-history (off by default)
this is not feature complete, and likely never will be. no ^
and ! has some oddities ... ksh's internal history stuff has got
some very odd behaviours that are rather nasty
ok various developers
|
|
- be more consistent w.r.t. variables in macros with `.Ic'
instead of `.Va'
- document changes in IFS parsing
- minimize diffs between ksh.1tbl and sh.1tbl w.r.t. `.Nm'
macros and in other places
- sort recognized keywords and remove dependency on tbl(1)
- indent example displays
- kill `bind'
- collapse `test' display, it has two entries for `str',
and use different args for file time tests
- grammar, punctuation, and mdoc fixes
- tidy display of `alias' and `kill'
ok and bits from jmc
|
|
|
|
and OK otto@. Closes PR 4023.
|
|
|
|
'looks fine' millert@, krw@. ok jmc@
|
|
when the current character is IFS space and the last
character was a word character or it was non-white IFS
space and the current character is non-white IFS space.
This deviates from the previous behavior because the
latter splits words when the last character is any IFS
space and the current is non-white IFS, resulting in
more fields most of the time.
This new behavior follows what the man page describes;
i.e., that a field is delimited by one or more IFS
whitespace characters followed by zero or one non-white
IFS characters.
Requires addition of a new substitution expansion state
to handle the special case of empty fields at the
beginning.
testing by naddy
ok jmc, millert, otto, deraadt
|
|
means even less fallout from the prompt expansion changes; ok jmc
|
|
|
|
sequences;
from naddy@, via deraadt@
|
|
regular things, except that character counting is turned off temporarily.
character counting is needed so that the shell can handle editing beyond
end-of-line and such
as well, ksh hack: prompts prefixed with [delimitchar]\r means that any blocks
between later matching [delimitchar] toggle counting on and off
semantics corrected based on input from naddy
|
|
naddy ok
|
|
found by (and ok) deraadt@
|
|
|
|
slightly so that no one (me, most likely) falls for it again.
also, make sh(1)'s IFS description a little more consistent.
|