github-mirror/fish-shell
2
0
Fork 0
mirror of https://github.com/fish-shell/fish-shell.git synced 2024-11-29 21:43:55 +08:00
Code Issues Actions 4 Packages Projects Releases Wiki Activity
925382dc3e
fish-shell/tests/checks/tmux-prompt.fish

39 lines
899 B
Fish
Raw Normal View History

tests: filter control sequences only when interactive This demonstrates that we only write control sequences when interactive.
2024-04-12 18:19:32 +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
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 '
Send repaint requests through the input queue again Another consequence of a583fe723 ("commandline -f foo" to skip queue and execute immediately, 2024-04-08) is that "commandline -f repaint" will paint the prompt with the current value of $status which might be set from a shell command in a the currently executing binding, instead of waiting for the top-level status. This is wrong, at least historically. It surfaces in bindings like alt-w which always paint a status value of [1] when on single-lines commandlines. Another regression is that a redundant repaint in a signal handler outputs an extra prompt. Fix both by making repaint commands go over the input queue again. This way, they are always run with a good commandline state. There is no need to repaint immediately because I don't think anyone has a data dependency on it (we currently don't expose the prompt string), it's only for rendering.
2024-04-19 17:25:05 +08:00
function fish_prompt
printf "prompt $status_generation> <status=$status> <$prompt_var> "
set prompt_var ''
end
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 on_prompt_var --on-variable prompt_var
commandline -f repaint
end
Send repaint requests through the input queue again Another consequence of a583fe723 ("commandline -f foo" to skip queue and execute immediately, 2024-04-08) is that "commandline -f repaint" will paint the prompt with the current value of $status which might be set from a shell command in a the currently executing binding, instead of waiting for the top-level status. This is wrong, at least historically. It surfaces in bindings like alt-w which always paint a status value of [1] when on single-lines commandlines. Another regression is that a redundant repaint in a signal handler outputs an extra prompt. Fix both by making repaint commands go over the input queue again. This way, they are always run with a good commandline state. There is no need to repaint immediately because I don't think anyone has a data dependency on it (we currently don't expose the prompt string), it's only for rendering.
2024-04-19 17:25:05 +08:00
function token-info
__fish_echo echo "current token is <$(commandline -t)>"
end
bind ctrl-g token-info
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
'
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
Send repaint requests through the input queue again Another consequence of a583fe723 ("commandline -f foo" to skip queue and execute immediately, 2024-04-08) is that "commandline -f repaint" will paint the prompt with the current value of $status which might be set from a shell command in a the currently executing binding, instead of waiting for the top-level status. This is wrong, at least historically. It surfaces in bindings like alt-w which always paint a status value of [1] when on single-lines commandlines. Another regression is that a redundant repaint in a signal handler outputs an extra prompt. Fix both by making repaint commands go over the input queue again. This way, they are always run with a good commandline state. There is no need to repaint immediately because I don't think anyone has a data dependency on it (we currently don't expose the prompt string), it's only for rendering.
2024-04-19 17:25:05 +08:00
# CHECK: prompt 0> <status=0> <>
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 -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
Send repaint requests through the input queue again Another consequence of a583fe723 ("commandline -f foo" to skip queue and execute immediately, 2024-04-08) is that "commandline -f repaint" will paint the prompt with the current value of $status which might be set from a shell command in a the currently executing binding, instead of waiting for the top-level status. This is wrong, at least historically. It surfaces in bindings like alt-w which always paint a status value of [1] when on single-lines commandlines. Another regression is that a redundant repaint in a signal handler outputs an extra prompt. Fix both by making repaint commands go over the input queue again. This way, they are always run with a good commandline state. There is no need to repaint immediately because I don't think anyone has a data dependency on it (we currently don't expose the prompt string), it's only for rendering.
2024-04-19 17:25:05 +08:00
isolated-tmux send-keys Enter
# CHECK: prompt 0> <status=0> <changed>
isolated-tmux send-keys echo Space 123
tmux-sleep
isolated-tmux send-keys C-g
# CHECK: prompt 0> <status=0> <> echo 123
# CHECK: current token is <123>
# CHECK: prompt 0> <status=0> <> echo 123
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
Reference in New Issue Copy Permalink