-
Notifications
You must be signed in to change notification settings - Fork 119
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
php-mode's call to php-syntax-propertize-function makes visiting large files rather slow #491
Comments
Good point! It seems this call was also removed from |
I updated recently and I'm having to axe php-mode on relatively small files around 2600 lines of code. Emacs 27.0.50
|
I took your suggestion and haven't noticed any partial font locking. In any case, it does make a tremendous speed difference. Thanks! |
Ok great! I will give it some more testing to check if I still notice the partial font locking issue. |
@phil-s @bridgesense This slowdown should be fixed by @zonuexe with PR #531. Could you perhaps verify this with the latest MELPA version of php-mode? Thanks! |
Emacs: 27.0.50 I loaded some of my larger projects. It works beautifully with no apparent issues. |
@bridgesense Thanks! I will release |
This is a fairly old issue, but the workaround has been replaced by different code in #786. |
The size of file involved here makes this an edge case, but I have a 450K file of machine-generated PHP, and just opening the file on even a reasonably quick PC takes 3 seconds, which is mostly accounted for by that forced call to
php-syntax-propertize-function
at the end ofphp-mode
:Does anyone have ideas for how to circumvent or reduce that?
I can see that #294 introduced this call because Emacs 25 had ceased to do it automatically, which really makes me wonder whether there's an existing Better Way which Emacs 25 expects modes to be utilising?
NEWS.25 says:
Which sounds like ideally this up-front effort wouldn't be needed at all; but presumably it turned out that it was in practice?
The text was updated successfully, but these errors were encountered: