pil keeps parent shell around

Hi Alex, is it expected that calling pil keeps the parent shell process around? tomas@x ~ % pstree | grep pi | |-zsh---pil---picolisp I can see pil in the process list but I would prefer if it was replaced by the picolisp process (aka shell exec). Thank you, Tomas -- UNSUBSCRIBE:

Re: pil keeps parent shell around

Hi Alex, tomas@x ~ % pstree | grep pi | |-zsh---pil---picolisp I can see pil in the process list but I would prefer if it was replaced by the picolisp process (aka shell exec). This can be done with the (surprise!) 'exec' function

Re: pil keeps parent shell around

On Sun, Jun 28, 2015 at 07:04:20PM +0200, Alexander Burger wrote: Hi Tomas, tomas@x ~ % pstree | grep pi | |-zsh---pil---picolisp I can see pil in the process list but I would prefer if it was replaced by the picolisp process (aka shell exec). This can be done with the

Re: pil keeps parent shell around

Hi Tomas, tomas@x ~ % pstree | grep pi | |-zsh---pil---picolisp I can see pil in the process list but I would prefer if it was replaced by the picolisp process (aka shell exec). This can be done with the (surprise!) 'exec' function http://software-lab.de/doc/refE.html#exec

Re: pil keeps parent shell around

On Sun, Jun 28, 2015 at 11:19:00PM +0200, Tomas Hlavaty wrote: This can be done with the (surprise!) 'exec' function http://software-lab.de/doc/refE.html#exec On the other hand, if you need to use (fork) 0 for example because you want to inherit something from the parent pil