You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the ability to write easy tests is important.
lisp/code/languages/sh.el requires indentation, because it uses some features from lisp/code/indentation.el. However, when the tests were run in a sterile environment, (i.e. presumably with a bad load-path) there were problems.
So kotct/load-corresponding calls kotct/quietly-load-file and loads the file directly. It's just a matter of features being unable to be loaded. Can we set load-path somehow so that it covers all possible things that our tests can require?
The text was updated successfully, but these errors were encountered:
This and a couple other things make me think that it would be good to break out some of the logic in init.el out into init-lib.el (like the old kotct.emacs). That way we can do some stuff without loading the whole config.
I think the ability to write easy tests is important.
lisp/code/languages/sh.el
requiresindentation
, because it uses some features fromlisp/code/indentation.el
. However, when the tests were run in a sterile environment, (i.e. presumably with a bad load-path) there were problems.So
kotct/load-corresponding
callskotct/quietly-load-file
and loads the file directly. It's just a matter of features being unable to be loaded. Can we setload-path
somehow so that it covers all possible things that our tests canrequire
?The text was updated successfully, but these errors were encountered: