Add valid word characters as a configuration option#147
Draft
stevepiercy wants to merge 5 commits intosphinx-contrib:mainfrom
Draft
Add valid word characters as a configuration option#147stevepiercy wants to merge 5 commits intosphinx-contrib:mainfrom
stevepiercy wants to merge 5 commits intosphinx-contrib:mainfrom
Conversation
dhellmann
reviewed
Mar 13, 2022
Author
|
I just pushed a fix for lint and added a rough draft for a history.rst entry. I think we've gone as far as possible without getting feedback from the maintainer of PyEnchant. What's next? |
Member
It would be useful to have a public API for passing the value into PyEnchant. I'm not sure the best way for you to start that conversation. Perhaps filing an issue on https://github.com/pyenchant/pyenchant? |
Author
|
Sounds like a plan. I also pushed a fix to add |
2 tasks
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
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.
See #119 (comment)