load_project looks for a key named path, which is not specified here, and so the base path is null. It is only because this is a relative path that this accidentally works, because the project directory is looked up automatically.
An additional thing highlighted by this bug is that if you incorrectly specify a non-relative recursive path, this destroys 4coder one way or another. That is to say:
TheSandvichMaker commentedMay 19, 2021
Version: 4.1.7
When you use setup_new_project, the fkey_command entry it generates uses semicolons where it should use commas:
and the load_paths_base presumes that an initial anonymous string will specify the path, but this is incorrect.
load_project looks for a key named
path, which is not specified here, and so the base path is null. It is only because this is a relative path that this accidentally works, because the project directory is looked up automatically.The correct version is
An additional thing highlighted by this bug is that if you incorrectly specify a non-relative recursive path, this destroys 4coder one way or another. That is to say:
Will lock up 4coder for me on windows, stuck somewhere inside a syscall in ntdll.dll.
The text was updated successfully, but these errors were encountered: