summaryrefslogtreecommitdiff
path: root/lisp/emacs-lisp/byte-run.el
diff options
context:
space:
mode:
authorJoão Távora <joaotavora@gmail.com>2023-03-04 19:14:48 +0000
committerJoão Távora <joaotavora@gmail.com>2023-03-04 19:15:48 +0000
commita7cd125d490295eb24edf43119f3d3511c3dfddd (patch)
treed769848082ad1b7943ec0139532dee84c2c323ad /lisp/emacs-lisp/byte-run.el
parent6c66dbd02c7773a4347583b35b8caa219df30807 (diff)
downloademacs-a7cd125d490295eb24edf43119f3d3511c3dfddd.tar.gz
emacs-a7cd125d490295eb24edf43119f3d3511c3dfddd.tar.bz2
emacs-a7cd125d490295eb24edf43119f3d3511c3dfddd.zip
More robustly unspoof HOME in Eglot tests (bug#61637)
A fair number of LSP servers allow user-local installations instead of system wide installations. Emacs's technique of spoofing the HOME env var to some non-existent or non-home directory during 'make check' breaks these tests. That's because the executables are still found by executable-find, but their invocation will rarely be successful as HOME isn't what they expect it to be. Eglot tests already had a technique for dealing with this, "unspoffing" HOME just for the invocations of LSP server but it stopped working a while back. So make it more robust. Eventually, we'll want to decide wether these local servers should be considered in 'make check' runs at all, or whether there is a way to use them with a spoofed HOME. * test/lisp/progmodes/eglot-tests.el (eglot--call-with-fixture): More robustly unspoof HOME.
Diffstat (limited to 'lisp/emacs-lisp/byte-run.el')
0 files changed, 0 insertions, 0 deletions