Age | Commit message (Collapse) | Author |
|
very specific behaviour
document this accordingly in the guidelines section of the manpage
ok bluhm@
|
|
* compile the edit utility once
* emit a warning during timeout
|
|
look at these tests: add a comment providing a high-level picture of
what is going on here, such that everyday maintenance can be performed
without going down the rabbit hole of subr.sh and edit.c.
|
|
sequences, but coverage of four-byte sequences was incomplete, which
contributed to the recently fixed ksh(1) emacs.c bug not being found
for some time.
Consequently, add some tests covering
+ valid sequences starting with \0360, \0361, and \0363;
+ incomplete sequences starting with \0360 and \0361;
+ invalid (too low) sequences starting with \0360.
OK anton@
|
|
The incorrectness of this test was exposed by the bugfix
in /usr/src/bin/ksh/emacs.c rev. 1.88 and reported to me by bluhm@.
This is a minimal fix replacing the incorrect test line
with two correct tests involving the same byte.
OK anton@
|
|
okay tb@
|
|
millert's clear-screen change in vi.c -r1.57 it now depends on $TERM
|
|
From Martijn Dekker
|
|
With the pipefail option set, the exit status of a pipeline is 0 if all
commands succeed, or the return status of the rightmost command that
fails. This can help stronger error checking, but is not a silver
bullet. For example, commands will exhibit a non-zero exit status if
they're killed by a SIGPIPE when writing to a pipe. Yet pipefail was
considered useful enough to be included in the next POSIX standard.
This implementation remembers the value of the pipefail option when
a pipeline is started, as described as option 1) in
https://www.austingroupbugs.net/view.php?id=789#c4102
Requested by ajacoutot@, ok millert@
|
|
while using option e.
|
|
Suggested by anton@
|
|
|
|
While the code intended to support both -s NAME and -s SIGNAME, the
tests performed were wrong. Replace convoluted code with less cryptic
conditionals. ok anton@
|
|
Prodded by anton@
|
|
|
|
in the installer.
from tb@
|
|
|
|
OK jca
|
|
No binary change on amd64 and there should be no differences on any
other 64 bit architecture either (because long = int64_t).
ok cheloha, tb
|
|
|
|
|
|
POSIX requires only decimal, octal and hex, tests for the $((x#number))
notation could be useful too.
|
|
failure.
|
|
than SIGHUP.
|
|
|
|
|
|
|
|
tests. Makes it easier to run all tests using another binary:
$ pwd
/usr/src/regress/bin/ksh
$ make KSH=/usr/src/bin/ksh/obj/ksh
|
|
|
|
on the following reasoning: once the program to test has written some data it
has entered the main-loop and is by now ready to receive user input. At this
point it should be safe to start writing input and once the program once again
enters a blocking reading state, its done processing the input. This approach
was sensitive to timing and determining when a shell is done processing its
input (if ever) is tricky.
This iteration of the edit program takes a new approach and uses presence of a
prompt for synchronisation of I/O. It doesn't solve all problems but is a step
in the right direction.
Joint work with bluhm@
|
|
my workaround that switched to build user.
|
|
when executed as root.
Spotted by bluhm@
|
|
Prodded by bluhm@
|
|
While here, pass the v option to hexdump in order to output all data.
|
|
|
|
and is not an easy fix for now.
|
|
borrowed from ksh93.
Survived a ports build performed by naddy@ and encouraged by many.
|
|
broken tests.
|
|
|
|
|
|
reused.
|
|
|
|
that valid input does not cause writing invalid intermediate states
to the terminal, and that invalid input is not delayed waiting for
more input, but written through right away.
Currently failing, but expected to be fixed shortly.
|
|
Absent from my previous commit.
|
|
Instead of calling x_vi() directly, run ksh in a pseudo tty.
This makes the process of adding tests for emacs mode simpler since the code can
be shared.
With feedback and help from millert@ and schwarze@
|
|
Reported by Walter Alejandro Iglesias on tech@.
ok schwarze@ tb@
|
|
While here, remove a condition that becomes redundant.
ok schwarze@ tb@
|
|
|
|
|
|
Add seterror tests 8-10 for better "set -e" coverage.
Add seterror-11 test to exercise the bug with "set -e" and
short-ciruited "&&" chains.
From Kartik Agaram
|