Make the system macro call set the current working directory
#2784
Conversation
|
The real problem is hardcoding either variant, it should be configurable. |
|
Is there a way to get the project root dir? It's another dir that might be useful. It's hard to find a configuration option in a syntax with backticks. ugly as hell, right? Maybe we could preserve the current directiory somehow (?) |
|
Previously to target a relative file we used Now, we do nothing to target a relative file, but how do we target files in the working directory? Is it possible? |
|
What's the use case for getting files in the working directory where you are compiling a file? |
|
On second thought, it's true that with I'll close this. |
Fixes #2750
I think it makes more sense. If I have:
{{ `cat foo.txt`.stringify }}I'd expect "foo.txt" to be relative to the file where the macro is defined. This makes builds reproducible, which doesn't happen right now because this basically depends on the current working directory where the program is compiled.
I know that
__DIR__can be used, but when dealing with files it will always have to be used, which makes things more verboise and harder to understand.