LAURENS Jérôme
LAURENS Jérôme
This is a long standing problem. Actually, synctex writes down the full path of the source file which is problematic for the situation you describe and also for security reasons...
Are you on windows?
If you have the `synctex` command line tool, you can try to typeset some `foo.tex` which full path contains non ascii characters, the you can try to execute ``` synctex.exe...
Normally the first 0 in x0,0.... should mean filter out this line. I'll check this out.
I have no real option, if you think there is something missing, feel free to make more precise suggestions or add a pull request.
Any ways of rendering the code stronger is welcome. Maybe static code analysis can be automated at the GitHub level. About aspect oriented, I can't tell anything except that changes...
Here is the link https://github.com/latex3/l3build/blob/e2060d6730230235e2b81f6db9199b40fa43e317/l3build-aux.lua#L207
@josephwright If `env` is empty and `vars` only contains variable `FOO`, then line 210 ``` return run(dir,set_epoch_cmd(epoch, forcedocepoch) .. env .. cmd) ``` is equivalent to ``` return run(dir,set_epoch_cmd(epoch, forcedocepoch)...
Concerning point 2) I perfectly understand your explanation and it makes sense for LaTeX. But for other packages, the testing policy might be different and the developer might want to...
What do you mean by ´you just pick the right path'? In the above mentionned situation there are at least 2 right paths, and developers will want to handle them...