-
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parsing error on &! #85
Comments
This is expected (for now, at least). It's documented in the manpage (here's an excerpt from the plaintext copy): Lines 202 to 213 in 80e9363
In the near-ish term, we can probably:
In the long run I would like for resholve to be a little more parser-agnostic, but my gut says that'll be pretty difficult. I made some strides over the last year to build a more domain-specific abstraction layer between resholve and the OSH parser, but it is still tightly coupled to some of Oil's abstractions and APIs. |
Thanks, makes sense. Indeed, I’d only been looking at the main and nixpkgs readmes. For now I’ll just use a wrapper around resholve to temporarily replace |
Good point--if pluggable parsers don't seem to be tractable, I guess pluggable in/out filters might be... |
zsh has a
&!
syntax for starting a disowned job, e.g.:Using this in a script causes resholve to fail with a parsing error:
The text was updated successfully, but these errors were encountered: