diff options
| author | João Távora <joaotavora@gmail.com> | 2022-09-18 10:15:43 +0100 |
|---|---|---|
| committer | João Távora <joaotavora@gmail.com> | 2022-09-18 10:15:43 +0100 |
| commit | 14586fedcf9ac4aafe119b89a72d0b438f6a4d04 (patch) | |
| tree | 62c50b7af12b065ae63a41339a1404de852801c3 /test/lisp/emacs-lisp/bytecomp-resources/warn-variable-setq-odd.el | |
| parent | 523547321e4caca6fc966bd71ecd7b60a6e98f73 (diff) | |
| download | emacs-14586fedcf9ac4aafe119b89a72d0b438f6a4d04.tar.gz emacs-14586fedcf9ac4aafe119b89a72d0b438f6a4d04.tar.bz2 emacs-14586fedcf9ac4aafe119b89a72d0b438f6a4d04.zip | |
Don't exceed max-specdl-size in big go projects
When invoking client/registerCapability for
workspace/didChangeWatchedFiles, Gopls lists each file to watch
separately. This makes eglot--glob-emit-{} emit a closure with an
'or' form containing a potentially large number of 're-search-forward'
forms.
For large Go project such as "Kubernetes", this list becomes so large
that -- for some reason I don't understand -- it triggers the
'max-specdl-size' limit.
An alternative using `regexp` opt doesn't seem to trigger the error.
* eglot.el (eglot--glob-emit-{}): Use regexp-opt.
GitHub-reference: fix https://github.com/joaotavora/eglot/issues/633
GitHub-reference: fix https://github.com/joaotavora/eglot/issues/1067
Diffstat (limited to 'test/lisp/emacs-lisp/bytecomp-resources/warn-variable-setq-odd.el')
0 files changed, 0 insertions, 0 deletions