Dear Maintainers of Markdown Preview for (Neo)vim,
I trust this message finds you in good spirits. I am writing to you today to address an aspect of the Markdown Preview plugin that I believe could be refined to enhance the user experience significantly.
Having utilised your plugin extensively, I have observed that the synchronised scrolling feature, while highly beneficial, occasionally exhibits a degree of latency. This lag can detract from the seamlessness of the real-time preview, particularly when editing larger Markdown documents.
Understanding that the updatetime setting in Vim can influence this behaviour, I have experimented with various configurations but have yet to achieve the fluidity of response that one might desire. As such, I propose that we explore potential optimisations within the plugin's codebase that could mitigate this latency.
Possible avenues for investigation might include:
Optimising the event handling mechanism that triggers the scroll update.
Introducing a more efficient diffing algorithm to determine scroll adjustments.
Leveraging web technologies that could offer smoother rendering of scroll events.
I am keen to hear your thoughts on this matter and would be delighted to assist in any capacity should you deem it appropriate. I believe that by addressing this nuance, we can elevate the utility of the Markdown Preview plugin to new heights, ensuring a truly instantaneous and synchronous preview experience.
Thank you for your time and for your continued dedication to the development of this invaluable tool.
Dear Maintainers of Markdown Preview for (Neo)vim,
I trust this message finds you in good spirits. I am writing to you today to address an aspect of the Markdown Preview plugin that I believe could be refined to enhance the user experience significantly.
Having utilised your plugin extensively, I have observed that the synchronised scrolling feature, while highly beneficial, occasionally exhibits a degree of latency. This lag can detract from the seamlessness of the real-time preview, particularly when editing larger Markdown documents.
Understanding that the
updatetimesetting in Vim can influence this behaviour, I have experimented with various configurations but have yet to achieve the fluidity of response that one might desire. As such, I propose that we explore potential optimisations within the plugin's codebase that could mitigate this latency.Possible avenues for investigation might include:
I am keen to hear your thoughts on this matter and would be delighted to assist in any capacity should you deem it appropriate. I believe that by addressing this nuance, we can elevate the utility of the Markdown Preview plugin to new heights, ensuring a truly instantaneous and synchronous preview experience.
Thank you for your time and for your continued dedication to the development of this invaluable tool.
Best regards, yihong1120