Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rewrite
with_history
test helper to be more robustWrite mock history to a temp file and load it directly with
fc -R
instead of running each command individually to build up the history.Fix flaky special char specs by not using
with_history
twice per testThere's something funny occasionally happening when
with_history
is used twice in the same test. It seems to be happening more frequently since asynchronous mode was enabled by default. My guess is it has something to do with theC-c
keys being sent toward the end not consistently terminating the prompt. But I'm really not sure how it would ever get into athen
block like it seems to:Sticking to only one
with_history
per terminal session (per test) seems to fix the flakiness.I also removed an old test case because I could not understand why it was necessary and so couldn't write a good description for it. Could be we'll need to add it back in at some point.