patch(preprocessor): make Command::Delete more explicit#286
Merged
Conversation
This commit facilitate the usage of the delete command for environment where we can't easily delete a non ascii characters. It also help the developer to what to be deleted. As additional change, it leave the backspace operation pass through the preprocessor when when there is not matching characters or the buffer is empty.
Member
Author
|
The pr is not yet ready, i have to update the afrim service. |
pythonbrad
changed the title
Command::Delete explicitCommand::Delete more explicit
This commit fix the issue with the additional backspace trigger during the usage of backspace to undo a typing.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Related issues
afrim::preprocessordelete command more explicit #283Changes