Properly display Class#name entries #12
Open
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
Workaround for emmanueltouzery#11
Workaround for emmanueltouzery#11
Workaround for emmanueltouzery#11
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.
Workaround for #11
This looks whether the doc (entry) filename contains 4 components after being split on
#. If so, it considers the first 2 components to be the "Class" and "Method" parts respectively and joins them with "#" for display in the picker.This way the current filename encoding still works and
Class#methodentries are still displayed correctly.I'm not sure whether that's feasible - the handling in
common.lua,#open_doc_in_cur_window()hints at a potential problem, but it should be fine.