| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the "all" target will depend on the "regress" target, so running
"make all" will recurse into the subdirectories for "regress", and
then recurse a second time into the same subdirectories for "all",
running all the tests twice.
Fix this by moving the Makefile to run the main-level tests into
a subdirectory "main" and only including <bsd.subdir.mk> from the
top level Makefile.
Issue reported by otto@; patch OK'ed by otto@ and bluhm@.
|
|
|
|
|
| |
it has no controlliing tty is not causing the test to fail.
based on otto@'s work; OK otto@
|
|
|
|
|
|
| |
(like the parent does).
When make is called in the parent dir, both make regress and make all
are called for the vi subdir. Need to figure out how to avoid that.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This simple patch makes the 'command' builtin POSIX-compliant and
consistent with other current shells. It fixes two things:
a) 'command -v' does not find shell reserved words (a.k.a. keywords).
For instance, 'command -v select' outputs nothing but should output
'select'.
b) 'command -pv' always outputs the path of an external command, even
if 'command -p' would execute a builtin. For instance, 'command -p kill'
executes the 'kill' builtin, as expected, but 'command -pv kill' outputs
'/bin/kill'. The '-v' option is supposed to reflect what would actually
be executed, so 'command -pv kill' should output 'kill'. The -p option
sets the PATH to a default system value before doing the search, but
that has no bearing on the fact that builtins take precedence over
external commands.
The patch fixes both issues for 'command' without affecting the
behaviour of the ksh-specific builtin 'whence', which is handled by the
same C function.
Regression test added to obsd-regress.t.
Issues found and fixed by Martijn Dekker, ok millert@
|
|
|
|
|
|
| |
All work done by Martijn Dekker
OK millert@
|