-
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
Repeated "parse-sexp-propertize-function did not move syntax-propertize--done" with emacs built from git master #570
Comments
emacs26 seems ok. |
Could you try to delete and reinstall (or recompile) the php-mode package in emacs 27.0.50 to see if this fixes this problem? |
It did disappear once I removed the elc file. Then it showed up again, but, today, it looks like it is gone. |
Note the problem may be related to flycheck and any of the -php, -phpcs, -phpmd, or my -psalm checkers. Because yesterday was evidently my "play with emacs" day, I managed to get eglot (which uses flymake) working and ditched flycheck. |
doh.... I spoke to soon. Just after I typed that comment I went to try to edit the file again and ran into the error while trying to save. backtrace:
|
And, because I have changed my config here are the results of php-mode-debug:
|
And, if it makes any difference, I just ran However, once eglot highlighted problems that it found with the psalm-language-server, the error returned. |
disabling some minor modes makes saving work again. php-mode-debug is the same as above with the following minor modes removed: |
Eh... This seems intermittent. In any case, I just ran into this again and saw that fontification stops on line 344. Don't know if that means anything. I suppose it could be the results of multiple invocations of |
Recently, editing PHP files in emacs has become rather frustrating. It seems that at any point I could end up with an backtrace like the following one I got when I tried to close the parens:
I don't know what other info you need, but here are the results of
php-mode-debug
:The text was updated successfully, but these errors were encountered: