Jordan Rome

@Delta-in-hub Mind describing your use case for this feature?

@fbs How do you feel about me trying to resurrect this effort and borrowing some of the code you wrote in this PR? Also was there a consensus on the...

Moving the conversation back here because, as @viktormalik and @fbs mentioned, how bpftrace handles command line arguments and env variables from [2815](https://github.com/iovisor/bpftrace/pull/2815) are closely tied. I think it ultimately comes...

> maybe we could go even further an enforce that all env definitions should be in the same block I like it. Especially since they will have to all be...

> Will it support setting arbitrary env vars? It's a bit confusing to have an 'env' block that doesn't set env vars for subprograms it spawns It could I suppose....

Summing up discussion from the last office hours (12/07/2023). There seems to be general consensus at least for the config/env variables as we're semi punting on the command line args...

I believe this is now possible using the wildcard match and pid targeting: https://github.com/iovisor/bpftrace/pull/2734

I was considering working on this feature request but only if folks feel like it would offer a large benefit over what exists currently (mostly just targeting everything and filtering...

This seems to work `nix build .#bpftrace-llvm12` so closing this issue. feel free to re-open if needed

Seems like man.tar.gz is now included: https://github.com/iovisor/bpftrace/releases/tag/v0.19.1