Profpatsch
Profpatsch
Yeah, this would be fantastic to have.
Bear in mind that this recursively goes up the tree to include parent gitignores, which means that e.g. lorri doesn’t like it by default.
You can detect it, right, so you could at least throw a giant multi-line warning for now if the bad cases happen (and maybe tell users to activate the `--do-not-unlink`...
@curiousleo says he can’t reproduce: https://github.com/target/lorri/issues/245#issuecomment-559117471 update: he can’t reproduce even before this change. I’ll take a look.
Maybe we want to ping @Gabriel439 on this, since they have the most experience with non-local dependencies in a config language.
From what i gathered you really want a semantics where file `A` can import file `H1` on Host `H`, which in turn wants to import file `H2` on Host `H`...
Two more points to consider: * Blowup of the dependency tree because of dependency on a http client and tls stack * Harder to compile the resulting language “to the...
Ah yes, `self` would refer to the `foo` I just define in this case, so I guess it would have to be `super` or something? On Fri, Dec 4, 2020...
(triage) any new leads?
Are there any ways we can take this forward? Simple first steps?