-
Notifications
You must be signed in to change notification settings - Fork 444
Issue212 selection highlights #218
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The existing code used Scintilla's built-in findFirst method which changes the active selection as it goes. The attempt to replace the original selection was causing issues when selecting backwards with the keyboard. While it would probably be possible to get the right logic in place by getting the right combination of Scintilla's anchor and caret position, I've simply bypassed the problem by using Python's regex .finditer function to identify matching spans and converting those to Scintilla ranges.
…tor to the right of a selection. Also rework some of the existing highlighter tests to exercise the editor functionality directly, relying less on our underlying implementation
…ccurs which clears the selection)
…plementation does; we can revisit the spec later and decide whether we want this functionality or not. (It doesn't make a ton of sense since, while it's selected, the highlight is hidden by the selected; and once it's unselected, the highlight will be cleared).
Build still failing due to PEP8. :-( |
Hmmm. I ran all the make checks over it. Ok; I'll have a look.
|
Perhaps I'm misunderstanding the output: it looks to me as though the overall merge is passing, but that individual commits are failing -- which they will, since they precede other commits which are exactly fixing up PEP8 errors. Should I have rebased before pushing the PR? |
Apologies... looks like it was Travis that had the collywobbles. I hit it with the proverbial spanner and it's gone green. ;-) |
Looking at coverage, there's a couple of branches in the code that are not exercised. I'll add/massage the tests to get us back to 100%. |
This PR is for the issues discussed in #212 but it builds on the (currently unmerged) work in #209