<muurkha>yeah, that's generally the reason for that kind of thing <muurkha>and it can be nice to include the full path <oriansj>muurkha: well if you notice full paths are not needed to provide those useful error messages by the compiler. However cgdb debug info pointing to the source files could use the full path but honestly I hope one way we can get people to just create a .source segment and use that instead. <oriansj>would seriously bloat the binaries but then all binaries would always carry the correct and corresponding source code. <muurkha>if the error messages include the full path, Emacs can take you to the correct file when you click them, which can be useful, without having to ask you which directory it's in (and possibly getting the wrong one). I like the .source segment idea but I don't think it helps for that particular case <muurkha>because the source you want to edit then is the original source you will then try to recompile, not the source embedded in the .o file you're about to overwrite <muurkha>I don't know if that's why tcc embeds the paths, I haven't looked ***alMalsamo is now known as lumberjack
***genr8eofl_ is now known as genr8eofl
***alMalsamo is now known as lumberjack123
<PureTryOut[m]>mbakke: do you by any chance know if the author of that Dart packaging series is reachable on Matrix and/or IRC? ***dongcarl2 is now known as dongcarl