Jeff King <p...@peff.net> writes: > I don't think this is "unfortunately"; freeing the memory was the entire > purpose in adding env_array. If you want to easily reuse the same > environment in multiple commands, it is still perfectly fine to use > "env" directly, like: > > struct argv_array env = ARGV_ARRAY_INIT; > struct child_process one = CHILD_PROCESS_INIT; > struct child_process two = CHILD_PROCESS_INIT; > > ... setup env with argv_array_push ... > > one.argv = foo; > one.env = env.argv; > run_command(&one); > > two.argv = bar; > two.env = env.argv; > run_command(&two); > > argv_array_clear(&env); > > You do not get the benefit of the auto-cleanup (you have to call > argv_array_clear yourself), but that is less bad than repeating the > setup of "env" twice.
Yeah, the above looks like the best option, better than using a single child_process and having to re-initialize fds and envs. Thanks for helping. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
