fish-shell/tests/jobs.in

jobs -q; echo $status
sleep 5 &
sleep 5 &
jobs -c
jobs -q; echo $status
bg -23 1 2>/dev/null
or echo bg: invalid option -23 >&2
fg 3
bg 3
sleep 1 &
disown
jobs -c
disown foo
disown (jobs -p)
or exit 0
Add tests for `jobs -q` 2018-03-05 05:33:36 +08:00			`jobs -q; echo $status`
Improve `bg` argument handling - Error out if anything that is not a PID is given - Otherwise background all matching existing jobs, even if not all PIDs exist (but print a message for the non-existing ones) Fixes #3909. 2017-04-02 23:02:55 +08:00			`sleep 5 &`
			`sleep 5 &`
don't print header for each job 2016-06-09 07:09:29 +08:00			`jobs -c`
Add tests for `jobs -q` 2018-03-05 05:33:36 +08:00			`jobs -q; echo $status`
Remove caret redirection This removes the caret as a shorthand for redirecting stderr. Note that stderr may be redirected to a file via 2>/some/path... and may be redirected with a pipe via 2>\|. Fixes #4394 2018-04-02 04:43:05 +08:00			`bg -23 1 2>/dev/null`
split builtin bg into its own module 2017-06-15 09:25:51 +08:00			`or echo bg: invalid option -23 >&2`
remove the tests/.status files The tests/.status files aren't useful so eliminate them. Just verify whether a given test module exited with a success status. There isn't any point in having a "status" file that indicates the test module should exit with a success (zero) status. Closes #3208 Closes #3209 2016-07-06 14:12:28 +08:00			`fg 3`
Improve `bg` argument handling - Error out if anything that is not a PID is given - Otherwise background all matching existing jobs, even if not all PIDs exist (but print a message for the non-existing ones) Fixes #3909. 2017-04-02 23:02:55 +08:00			`bg 3`
implement disown builtin Closes #2810. The syntax mirrors that of zsh. 2017-03-23 08:50:57 +08:00			`sleep 1 &`
			`disown`
			`jobs -c`
			`disown foo`
			`disown (jobs -p)`
remove the tests/.status files The tests/.status files aren't useful so eliminate them. Just verify whether a given test module exited with a success status. There isn't any point in having a "status" file that indicates the test module should exit with a success (zero) status. Closes #3208 Closes #3209 2016-07-06 14:12:28 +08:00			`or exit 0`