You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm in the process of implementing general support for resolving of commands that appear in the arguments to other commands, which should be available in the coming weeks.
awk can do this via both the system() function and with its piping feature. Actually "resholving" commands in here probably entails having a parser of some sort. I'm undecided but leaning towards this being out-of-scope for resholve and saying this (and maybe sed, expect, and any others with this problem) is a sign that any of these will need their own tools. (Mostly because, if we could define an interchange format, additional tools wouldn't be tied to the resholve's own dependence on Oil/OSH/python2 and would be more likely to be able to tackle these tasks with the help of whatever parsers exist in whatever language they may be written in...).
I managed to find a way to raise an error when this form is encountered:
I don't know how to handle awk sub commands yet--sorry :(Next step: - See the feedback issue for a workaroundhttps://github.com/abathur/resholve/issues/31
I don't really understand how often this feature is used, so I don't know if this is going to be a big stumbling block or an occasional hurdle.
The text was updated successfully, but these errors were encountered:
I'm in the process of implementing general support for resolving of commands that appear in the arguments to other commands, which should be available in the coming weeks.
awk
can do this via both thesystem()
function and with its piping feature. Actually "resholving" commands in here probably entails having a parser of some sort. I'm undecided but leaning towards this being out-of-scope for resholve and saying this (and maybe sed, expect, and any others with this problem) is a sign that any of these will need their own tools. (Mostly because, if we could define an interchange format, additional tools wouldn't be tied to the resholve's own dependence on Oil/OSH/python2 and would be more likely to be able to tackle these tasks with the help of whatever parsers exist in whatever language they may be written in...).I managed to find a way to raise an error when this form is encountered:
I don't really understand how often this feature is used, so I don't know if this is going to be a big stumbling block or an occasional hurdle.
The text was updated successfully, but these errors were encountered: