tests/bind.expect: re-enable but at human typing speed only

The interactive bind tests work if the keys are treated like there is a
human pressing them.

This reverts commit 0006d23df8.
This commit is contained in:
David Adam 2015-10-18 21:11:21 +08:00
parent 0006d23df8
commit 55abe105ea
2 changed files with 3 additions and 5 deletions

View file

@ -18,7 +18,7 @@ expect_prompt -re {\r\nsuccess\r\n} {
puts stderr "Couldn't find expected output 'success'"
}
# try again without the human typing
send_line "echo fail\033ddiecho success"
send_line -h "echo fail\033ddiecho success"
expect_prompt -re {\r\nsuccess\r\n} {
puts "success"
} -nounmatched -re {\r\nfail} {
@ -28,7 +28,7 @@ expect_prompt -re {\r\nsuccess\r\n} {
}
# Test lowercase-r replace
send_line "\033ddiecho TEXT\033hhrAi"
send_line -h "\033ddiecho TEXT\033hhrAi"
expect_prompt -re {\r\nTAXT\r\n} {
puts "replace success"
} -nounmatched -re {\r\nfail} {
@ -38,7 +38,7 @@ expect_prompt -re {\r\nTAXT\r\n} {
}
# still in insert mode, switch back to regular key bindings
send_line "set -g fish_key_bindings fish_default_key_bindings"
send_line -h "set -g fish_key_bindings fish_default_key_bindings"
expect_prompt
send_line "echo success"
expect_prompt -re {\r\nsuccess\r\n} {

View file

@ -66,8 +66,6 @@ end
set -l failed
for i in *.expect
# HACK: Explicitly disable the bind test until we can figure out what to do with it
contains -- $i bind.expect; and continue
if not test_file $i
set failed $failed $i
end