github-mirror/fish-shell
2
0
Fork 0
mirror of https://github.com/fish-shell/fish-shell.git synced 2024-11-29 13:23:53 +08:00
Code Issues Actions 4 Packages Projects Releases Wiki Activity
1c4bb214d2
fish-shell/tests/checks/tmux-prompt.fish

25 lines
638 B
Fish
Raw Normal View History

Extract setup and teardown for tmux tests This was long overdue since the setup logic is much more complex than the actual tests. tmux-prompt.fish had extra logic to protect against XDG_CONFIG_HOME with leading double double-dot. I believe this is no longer necessary with the new test driver. We still use our own temp dir because we want to be able to run this independently of the test driver, This can be useful for debugging tests. For example we can insert a "$tmux attach" command in a test, and then run build/fish -C 'source tests/test_functions/isolated-tmux.fish' tests/checks/tmux-bind.fish This allows to inspect the state of the test and debug interactively. Attaching to the terminal doesn't work when running inside littlecheck because littlecheck consumes our output and doesn't give us a terminal. (Maybe there's an easy way to fix that?)
2021-08-29 15:44:22 +08:00
#RUN: %fish %s
Revert "Avoid excessive polling of universal variable file" This reverts commit b56b23007664525e13f7f7ec50a9a6adff0bdfd9. which somehow made us miss repaints on uvar notifications. The commit was a workaround for a polling bug which was later properly fixed by 7c5b8b855 ("Use the uvar notifier pipe timestamp to avoid excessive polling"), so it's no longer necessary. Add a system test. If I had a better understanding of the bug I could probably write a better test. Fixes #8088
2021-07-03 19:57:21 +08:00
#REQUIRES: command -v tmux
Skip tmux tests on Github Actions macOS This lacks the tmux-256color terminfo entry, leading to spurious warnings like warning: Could not set up terminal. <= no check matches warning: TERM environment variable set to \'tmux-256color\'. <= no check matches warning: Check that this terminal type is supported on this system. <= no check matches warning: Using fallback terminal type \'ansi\'. <= no check matches
2022-06-10 00:56:20 +08:00
# Github Actions currently (2022-06-09)
# doesn't include the tmux-256color terminfo on macOS.
# So we skip tmux tests there.
#REQUIRES: test -z "$CI" -o "$(uname)" != Darwin
Revert "Avoid excessive polling of universal variable file" This reverts commit b56b23007664525e13f7f7ec50a9a6adff0bdfd9. which somehow made us miss repaints on uvar notifications. The commit was a workaround for a polling bug which was later properly fixed by 7c5b8b855 ("Use the uvar notifier pipe timestamp to avoid excessive polling"), so it's no longer necessary. Add a system test. If I had a better understanding of the bug I could probably write a better test. Fixes #8088
2021-07-03 19:57:21 +08:00
Extract setup and teardown for tmux tests This was long overdue since the setup logic is much more complex than the actual tests. tmux-prompt.fish had extra logic to protect against XDG_CONFIG_HOME with leading double double-dot. I believe this is no longer necessary with the new test driver. We still use our own temp dir because we want to be able to run this independently of the test driver, This can be useful for debugging tests. For example we can insert a "$tmux attach" command in a test, and then run build/fish -C 'source tests/test_functions/isolated-tmux.fish' tests/checks/tmux-bind.fish This allows to inspect the state of the test and debug interactively. Attaching to the terminal doesn't work when running inside littlecheck because littlecheck consumes our output and doesn't give us a terminal. (Maybe there's an easy way to fix that?)
2021-08-29 15:44:22 +08:00
set -g isolated_tmux_fish_extra_args -C '
Revert "Avoid excessive polling of universal variable file" This reverts commit b56b23007664525e13f7f7ec50a9a6adff0bdfd9. which somehow made us miss repaints on uvar notifications. The commit was a workaround for a polling bug which was later properly fixed by 7c5b8b855 ("Use the uvar notifier pipe timestamp to avoid excessive polling"), so it's no longer necessary. Add a system test. If I had a better understanding of the bug I could probably write a better test. Fixes #8088
2021-07-03 19:57:21 +08:00
function fish_prompt; printf "prompt $status_generation> <$prompt_var> "; end
function on_prompt_var --on-variable prompt_var
commandline -f repaint
end
'
isolated-tmux to more reliably initialize and other fixes Prior to this change, tmux based tests would call 'isolated-tmux' which would initialize tmux on first call, an admitted "evil hack." Switch to requiring an explicit call to 'isolated-tmux-start' which then defines 'isolated-tmux' and other functions. Add some loop-until-prompt logic into 'isolated-tmux-start'. This improves reliability of the tmux tests on systems under load; at least it makes the tests pass in the background on my Mac. Remove the '$sleep' variable, to be replaced with 'tmux-sleep'.
2021-09-24 23:07:17 +08:00
isolated-tmux-start
tmux-prompt test to wait a bit to allow the first prompt to draw The tmux-prompt test would sometimes fail because the first call was: isolated-tmux capture-pane -p this would run a capture-pane which would race with starting fish itself; occasionally the pane would be empty since fish has not yet drawn a prompt. Add a loop to give fish time to draw the prompt.
2021-09-05 07:54:08 +08:00
Extract setup and teardown for tmux tests This was long overdue since the setup logic is much more complex than the actual tests. tmux-prompt.fish had extra logic to protect against XDG_CONFIG_HOME with leading double double-dot. I believe this is no longer necessary with the new test driver. We still use our own temp dir because we want to be able to run this independently of the test driver, This can be useful for debugging tests. For example we can insert a "$tmux attach" command in a test, and then run build/fish -C 'source tests/test_functions/isolated-tmux.fish' tests/checks/tmux-bind.fish This allows to inspect the state of the test and debug interactively. Attaching to the terminal doesn't work when running inside littlecheck because littlecheck consumes our output and doesn't give us a terminal. (Maybe there's an easy way to fix that?)
2021-08-29 15:44:22 +08:00
isolated-tmux capture-pane -p
Revert "Avoid excessive polling of universal variable file" This reverts commit b56b23007664525e13f7f7ec50a9a6adff0bdfd9. which somehow made us miss repaints on uvar notifications. The commit was a workaround for a polling bug which was later properly fixed by 7c5b8b855 ("Use the uvar notifier pipe timestamp to avoid excessive polling"), so it's no longer necessary. Add a system test. If I had a better understanding of the bug I could probably write a better test. Fixes #8088
2021-07-03 19:57:21 +08:00
# CHECK: prompt 0> <>
Extract setup and teardown for tmux tests This was long overdue since the setup logic is much more complex than the actual tests. tmux-prompt.fish had extra logic to protect against XDG_CONFIG_HOME with leading double double-dot. I believe this is no longer necessary with the new test driver. We still use our own temp dir because we want to be able to run this independently of the test driver, This can be useful for debugging tests. For example we can insert a "$tmux attach" command in a test, and then run build/fish -C 'source tests/test_functions/isolated-tmux.fish' tests/checks/tmux-bind.fish This allows to inspect the state of the test and debug interactively. Attaching to the terminal doesn't work when running inside littlecheck because littlecheck consumes our output and doesn't give us a terminal. (Maybe there's an easy way to fix that?)
2021-08-29 15:44:22 +08:00
set -q CI && set sleep sleep 10
Revert "Avoid excessive polling of universal variable file" This reverts commit b56b23007664525e13f7f7ec50a9a6adff0bdfd9. which somehow made us miss repaints on uvar notifications. The commit was a workaround for a polling bug which was later properly fixed by 7c5b8b855 ("Use the uvar notifier pipe timestamp to avoid excessive polling"), so it's no longer necessary. Add a system test. If I had a better understanding of the bug I could probably write a better test. Fixes #8088
2021-07-03 19:57:21 +08:00
set -U prompt_var changed
isolated-tmux to more reliably initialize and other fixes Prior to this change, tmux based tests would call 'isolated-tmux' which would initialize tmux on first call, an admitted "evil hack." Switch to requiring an explicit call to 'isolated-tmux-start' which then defines 'isolated-tmux' and other functions. Add some loop-until-prompt logic into 'isolated-tmux-start'. This improves reliability of the tmux tests on systems under load; at least it makes the tests pass in the background on my Mac. Remove the '$sleep' variable, to be replaced with 'tmux-sleep'.
2021-09-24 23:07:17 +08:00
tmux-sleep
Extract setup and teardown for tmux tests This was long overdue since the setup logic is much more complex than the actual tests. tmux-prompt.fish had extra logic to protect against XDG_CONFIG_HOME with leading double double-dot. I believe this is no longer necessary with the new test driver. We still use our own temp dir because we want to be able to run this independently of the test driver, This can be useful for debugging tests. For example we can insert a "$tmux attach" command in a test, and then run build/fish -C 'source tests/test_functions/isolated-tmux.fish' tests/checks/tmux-bind.fish This allows to inspect the state of the test and debug interactively. Attaching to the terminal doesn't work when running inside littlecheck because littlecheck consumes our output and doesn't give us a terminal. (Maybe there's an easy way to fix that?)
2021-08-29 15:44:22 +08:00
isolated-tmux capture-pane -p
Revert "Avoid excessive polling of universal variable file" This reverts commit b56b23007664525e13f7f7ec50a9a6adff0bdfd9. which somehow made us miss repaints on uvar notifications. The commit was a workaround for a polling bug which was later properly fixed by 7c5b8b855 ("Use the uvar notifier pipe timestamp to avoid excessive polling"), so it's no longer necessary. Add a system test. If I had a better understanding of the bug I could probably write a better test. Fixes #8088
2021-07-03 19:57:21 +08:00
# CHECK: prompt 0> <changed>
Reference in New Issue Copy Permalink