Add test for edit of WikiWord in an Emacs Lisp docstring #792
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
matsl
force-pushed
the
add-test-for-wikiwords-in-emacs-lisp-docstrings
branch
from
51ffb21 to
dcbbcf2
Compare
Also update test to verify WikiWord face as well as WikiWord.
matsl
force-pushed
the
add-test-for-wikiwords-in-emacs-lisp-docstrings
branch
from
dcbbcf2 to
9ce90a9
Compare
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.
What
Verifies face changes when editing a WikiWord in a docstring. Also
update old test to verify WikiWord face as well as WikiWord.
Why
Docstring highlighting has issues.
Notes
This test case works but doing the same operations interactively
fails. This could be due to the test code calls the pre and post hooks
to simulate what the interactive code does. See
hywiki-tests--command-execute for the details.
Submitting this test as it covers the case we want to test and uses
the same mechanisms as the other face tests does.
I guess the issue now is to figure out why the pre and post command
hooks are not called when testing this manually. Or if they are why it
differs.