Proposal: Adaption of the forward/reverse search behavior for custom source files instead of *.tex #36
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.
Hello,
I would like to change the forward/reverse search behavior of SimpleSynctexParser by an SynctexParserAdapter, from another eclipse plugin.
The use case is, I generate *.tex files from other files like *.java, *.groovy, *.scala and *.md.
The generated tex files are not much help to jump to. So it would be great to jump directly to the real source instead of the generated *.tex file.
The SynctexParserAdapter allows me to modify the lookup of the PDF target or the source file to jump between e.g. *.java and the PDF file.
The adapter will implement the ISynctexParser methods and change the returned file paths, if the adapter find a corresonding java file.
The SimpleSynctexParser was not changed, i only "intercept" the method calls by the adapter.
The extension point is used to scan for adapters in the EclipseIDE, so that your plugin do not have to implement my custom logic.
This only a proposal, please comment on my idea and let me know what you think about it.
I would be pleased to help to integrate the feature.
Andreas Turban