Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add wsf lexer performance improvements used by vis #16

Open
wants to merge 1 commit into
base: default
Choose a base branch
from

Conversation

moesasji
Copy link

This fix for performance improvements in the wsf lexer used by vis is committed in baa51e934ce057af5b5be829d6a73a3e8b4c03d0
and is the same as used in the xml lexer.

Would be good to add this to the upstream version

This fix is committed in baa51e934ce057af5b5be829d6a73a3e8b4c03d0
and is the same as used in the xml lexer.
@orbitalquark
Copy link
Owner

orbitalquark commented Dec 24, 2020 via email

@moesasji
Copy link
Author

Thanks for taking a look and I indeed didn't spot this as vis is not yet fully compatible with the styles used in the new format. The strange thing is that the patch did work for the legacy format.

vis-legacy-wsf

Back to the drawing table then....

btw) some of these patches don't really show test-cases...so it being "performance" improvements comes from the original patches.

@orbitalquark
Copy link
Owner

orbitalquark commented Dec 24, 2020 via email

@moesasji
Copy link
Author

Your explanation makes perfect sense. My understanding is that vis passes chunks of a file starting from a previous white line to maintain performance on large files, but does small files as the whole buffer based on this

For now best to just ignore this issue as your response gives a test-case to explore. Thanks!

@mcepl
Copy link

mcepl commented Aug 13, 2023

@moesasji vis has merged then upstream scintillua lexers in martanne/vis@8a420ec and we are now working on merging in all changes up to scintillua_6.2 tag in https://git.sr.ht/~mcepl/vis/log/devel_scintillua.

Do you think you would be able and willing to rebase all three of your PRs (#15, #16, and #17) on the top of scintillua_6.2, so that we all could benefit from it?

Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants