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

Spellright creates huge delay (up to 5s) on enter when used with LaTeX-Workshop #225

Closed
tecosaur opened this issue Oct 22, 2018 · 14 comments

Comments

@tecosaur
Copy link

This is related to James-Yu/LaTeX-Workshop#903.

When both LaTeX-Workshop and Spell Right are active on long .tex files a huge delay can be created when pressing enter. This is a significant issue for me as I frequently makes spelling mistakes, and work with long files on a potato PC (far less of an issue on a non-potato, but still very irritating). As a result of this, despite how much I need this, this extension is rendered unusable.

This is not an issue without LaTeX-Workshop, however it plays fine with many other extensions and the developers don't seem to know what's causing this.

Please help, I really want to be able to use this.

@bartosz-antosik
Copy link
Owner

I saw the thread. it is unclear to me wither. I asked in the thread for a document that you could claim does this delay in this or that point.

On the other hand does this (long time wait after ENTER is pressed) happen in any other document type?

@tecosaur
Copy link
Author

tecosaur commented Oct 22, 2018

Re: Document Type Specificity — see James-Yu/LaTeX-Workshop#903 (comment)
Edit: This comment is probably more helpful James-Yu/LaTeX-Workshop#903 (comment)

To get an idea of the perceived effect here's a gif from # 903:
imageedit_3_7923626959
The 'scrolled area' is equivalent to 5 seconds, this clip was produced by my pretty beefy desktop. My potato laptop starts showing issues around a few hundred lines.

@bartosz-antosik
Copy link
Owner

Could you please try to install this version from VSIX and see whether it reduces the delay:

https://drive.google.com/open?id=118oGg9HiGIec4BYtc4Th7IEEe4xW9xJb

@tecosaur
Copy link
Author

Unfortunately I'm currently experiencing issues with vs code 1.29, so I'll hold off until those are resolved.

@bartosz-antosik
Copy link
Owner

@tecosaur But, issues related to Spell Right?

@tecosaur
Copy link
Author

More just general vs code related issues, the update seems to have introduced hangs and other issues for me so I'm not sure how good any result I get would be.

@bartosz-antosik
Copy link
Owner

Oh, I see. Haven't notice anything but had similar sentiments with earlier versions.

@bartosz-antosik
Copy link
Owner

I am sorry to ask, but when would you expect to have a moment to see if the delays happen to you in the pre-release version I have shared few posts above?

@bartosz-antosik
Copy link
Owner

I am closing this as I hope the just published version 3.0.14 should help with this. Shall you have some more evidence please reopen/post in this thread.

@pycckuu
Copy link

pycckuu commented Oct 8, 2019

I am experiencing huge delays as well when entering the text in Latex. When I disable the extension the delays disappear. Could you add an option to check grammar only on save?

@bhvieira
Copy link

bhvieira commented Dec 1, 2020

I second @pycckuu's suggestion, at least until more permanent workarounds are found

@miromarszal
Copy link

I'm on v3.0.60 and I'm seeing this problem too. In a file of 1000+ lines, pressing enter has a very noticeable lag, disturbing me a lot when I write.

@KonstantinKhabarlak
Copy link

This is still a problem to me. Pressing enter takes 10-15 seconds on a long document

@NiklasRentzCAU
Copy link

I also just recently noticed this issue and pinpointed it to this issue today. Even when deactivating all other extensions and working in a simple 2-line markdown file this causes serious delays in saving, and - when activated - other interactions such as previewing the markdown. I would like to see this issue revisited.

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

No branches or pull requests

7 participants