Fixed issue #15 - no match displays user input. #19
Conversation
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.
This was a project for my CSE410 class at University At Buffalo. We were tasked with finding an open-source project, selecting an open bug-fix and trying to narrow down / fix the bug.
I was able to fix issue #15 by comparing the current string buffer to the menu selection returned by action_confirm. If the user presses enter, the N characters in the string buffer are compared to the first N characters of the menu selection using strncmp(). If they don't match, then we can conclude the menu selection is an invalid match.
Someone will want to double check it for type and syntax consistency. Hopefully this helps, I plan on poking around more on my own fork!