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
Markdown highlighting is kinda slow #104
Comments
Thank you for the report, @suhr. The highlighting is done every second by a customized version of PEG Markdown Highlight. Do you think that is a problem? |
Yes, editing doesn't feel smooth.
You can parse markdown in a small window before parsing the whole file, for example. |
Can you please explain in more detail what you are referring to. 😸 |
I'm not actually referring anything. Just a simple idea:
There're probably better ways to handle changing markdown (with something like incomplete syntax tree?), but I'm not aware of any. |
That if the whole markdown file is one big code block (like I know some people are using it)? |
Um... Nope. I may know a bit about parsing, but I don't know Qt. |
Currently the highlighting for the |
Of course we can always make a setting that allows to set the ms time interval between highlighting commands, most systems would allow smaller intervals. |
from the v16.06.3 changelog
|
There now is a new release, could you please test it and report if the new features work for you? |
It works. With a small highlighting interval it's much nicer to use, though it is still not instant like ghostwriter. |
You are always welcome to write a faster one. 👍 |
16.11.15
|
It should react instantly, but instead it takes about about 1-1.5 seconds to highlight something like
*test*
.The text was updated successfully, but these errors were encountered: