Travis A. Everett

Good point--if pluggable parsers don't seem to be tractable, I guess pluggable in/out filters might be...

Preserving this since there are at least a few things in here that need to get individually fixed ~ASAP.

That (or something similar) is the long-term intent. There are a few boxes I'd like to check there... - provide specific recommendations at error time since they're a good reminder...

I'm making 2 posts addressing this. The first focuses on things you noted that I've fixed today. The 2nd will just record some thoughts on the open questions... --- >...

> * "There is not yet a good way to resolve 'ping' in Nix builds." (Which don't come up with any suggestion, I've added it as an external) Yes. Sorry...

I have some WIP fixes that are making incremental progress on this, but as I'm working through it I'm thinking I should double-check my understanding. Generally speaking, I've only been...

Hehe. Fair. I'll chew on this. Thanks for the confirming. It doesn't square with how I've been using the parsers, but I agree there's some merit. I've avoided dealing with...

Curious what you think about the approach (and perhaps more importantly the right term--I suspect dead-end encodes too much of my perspective) here: https://github.com/abathur/resholve/commit/914061c2c70d32ff057d598152b12dfffd79979b#diff-3791dcc7805ec6044570664bd7360fb4e9441c5987f7df8641b50e8bdac2df48L2421-R2436 Basically, adding support treating a command...

> * I would change this... Thanks for noticing. I intended both the item and the final bracket on their own lines, but that column in my editor was a...

Just a ping to let you know I haven't forgotten this and thank you again for kicking it off. I agree with carving out space for this kind of parser...