add accessibility text manipulation commands for Texmaker #12
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
Author
|
sorry I meant to make the non-accessibility Texmaker commands in a separable request. I guess I forgot to put them on their own branch. If that's a problem, I can redo it just let me know |
Owner
|
No worries! Looks good, I have been meaning to test out this stuff for a while but haven't got round to it. May take me a week or two to test this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
I am adding James Stout's accessibility commands. I explain how to install the prerequisites for these commands in the comments at the top of texmaker_accessibility.py
Texmaker seems to be the only latex editor that these work in. They also work in chrome and Firefox. Eventually, you may want to consider making the CCR, but I have not made them CCR.