You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, I want to express my sincere gratitude for this fantastic plugin. After comparing it with other options, I still find this one renders the fastest, with no perceivable delay to the human eye. I’m genuinely appreciative of this wonderful community.
As the title suggests, there seems to be a small issue here, as shown in the image below.
I understand that this plugin was likely developed with simplicity and speed in mind. Therefore, I suspect this might not be a bug but rather an intentional choice (apologies if I’m mistaken—please feel free to correct me!). Regardless, "rendering speed" is my top priority, so even if this isn't an issue to be fixed, I'm more than happy to continue using it!
Best wishes!
The text was updated successfully, but these errors were encountered:
Yes, this is the result of special processing. Currently, the space is tightened to the maximum above and below to avoid gaps. Behavior like C/C++ supports single lines without {} may look strange. Currently, it is based on a sloppy space judgment. Due to the difference in ast, it may be better to use treesitter. But people usually disable this highlighting system in large files. So the context search judgment is used here....some specific file types may need to be determined by syntax rules. In this way, we can continue to maintain without the help of any tools
First of all, I want to express my sincere gratitude for this fantastic plugin. After comparing it with other options, I still find this one renders the fastest, with no perceivable delay to the human eye. I’m genuinely appreciative of this wonderful community.
As the title suggests, there seems to be a small issue here, as shown in the image below.
I understand that this plugin was likely developed with simplicity and speed in mind. Therefore, I suspect this might not be a bug but rather an intentional choice (apologies if I’m mistaken—please feel free to correct me!). Regardless, "rendering speed" is my top priority, so even if this isn't an issue to be fixed, I'm more than happy to continue using it!
Best wishes!
The text was updated successfully, but these errors were encountered: