Fix issues discovered in 2.3.0 #88
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
this token type wasn’t working correctly and failing to set the top bit of the next character - now fixed
fixes copy
an issue had been observed when pushing a duplicate entry - the history number wasn’t appropriately reset, so pressing up/down wouldn’t produce expected results this fixes by ensuring that the `history_no` is appropriately set on entry into the editline function
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Bumps up stack space to 2kb, fixing an issue observed with the
copycommand causing crashes from the MOS CLIFixes an issue observed with
echowhere|!token wasn't being correctly interpretedFixes #87 where history could slightly misbehave when not pushing a new item