Travis A. Everett

@SamLukeYes the last workaround in the first post may help here. Since 0.8.3 you can use `fix. = true` to bypass the error here and force it to resolve from...

One (potentially worst-case) example is an `ssh` invocation that would run commands on another system. - resholve could in theory recognize an ssh invocation that would run remote commands (and...

Another example is `nixos-enter` (brought up in https://github.com/abathur/resholve/issues/81#issuecomment-1366964535) which will run the commands in a chroot (potentially with or without a shell) on the same system. Despite being nixos-native, I...

This is one of the cases where the OSH/Oil parser doesn't support it, and unless maybe we convince upstream to do it (or patch and maintain it...) we're a little...

~Ah. I may be mis-remembering. It's actually the use of `[name]` that causes this and not the braces, yeah?~ Nope. Braces. Phew :)

I'll link yours upstream. It's at least a real example. :) I wrestled with this general issue a bit when I wrote lilgit; I currently try to have my cake...

It should, though I can't promise some holes won't turn up as we put it through the paces. If the scripts don't need incompatible solutions, you can just specify all...

@clkamp Ah. I do see the same locally. I guess you're at the intersection of a few things that aren't quite sorted out, yet: - The main difference between this...

@clkamp Glad to hear it. It's probably best to leave it open for now.

Came to the late realization tonight that the the 0.6.0 release broke this placeholder workaround. I assume from your description that this won't affect you, but wanted to ~document it...