From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@sunsite.dk
Subject: Re: Subshells and parameters
Date: Wed, 17 May 2006 08:42:54 -0700 [thread overview]
Message-ID: <060517084254.ZM8380@torch.brasslantern.com> (raw)
In-Reply-To: <20060517142404.GS871@prunille.vinc17.org>
On May 17, 4:24pm, Vincent Lefevre wrote:
} Subject: Re: Subshells and parameters
}
} On 2006-05-12 22:05:23 -0400, Lloyd Zusman wrote:
} > I'm wondering if there's a solution that doesn't require a separate
} > executable.
}
} You need a module, but this isn't implemented yet.
As someone pointed out earlier, you can fork a new copy of zsh to find
this information; to split hairs, that's a separate process, but not a
separate executable.
Example:
getpid() { typeset -g PID=$(exec $ZSH_NAME -fc 'print $PPID') }
The exec is important, otherwise you spawn two processes and get the
PID of the intermediate descendant.
Compare:
getpid; print $$ $PID
( getpid; print $$ $PID )
next prev parent reply other threads:[~2006-05-17 15:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-09 22:04 File locking within zsh? Lloyd Zusman
2006-05-10 3:31 ` Tim Writer
2006-05-10 5:59 ` Brian K. White
2006-05-10 10:02 ` Lloyd Zusman
2006-05-10 22:04 ` Tim Writer
2006-05-11 3:41 ` Bart Schaefer
2006-05-11 14:25 ` Tim Writer
2006-05-11 15:01 ` Peter Stephenson
2006-05-12 4:22 ` Tim Writer
2006-05-12 9:17 ` Subshells and parameters (was: File locking within zsh?) Vincent Lefevre
2006-05-12 12:09 ` Subshells and parameters Lloyd Zusman
2006-05-12 23:09 ` Vincent Lefevre
2006-05-13 2:05 ` Lloyd Zusman
2006-05-17 14:24 ` Vincent Lefevre
2006-05-17 15:42 ` Bart Schaefer [this message]
2006-05-17 16:07 ` Vincent Lefevre
2006-05-13 2:10 ` Dan Nelson
2006-05-11 16:13 ` File locking within zsh? Brian K. White
2006-05-10 17:13 ` Vincent Lefevre
2006-05-11 15:45 ` Brian K. White
2006-05-12 7:54 ` Vincent Lefevre
2006-05-12 19:40 ` Tim Writer
2006-05-12 23:24 ` Vincent Lefevre
2006-05-10 21:53 ` Tim Writer
2006-05-10 6:29 ` DervishD
2006-05-10 10:02 ` Lloyd Zusman
2006-05-10 21:21 ` DervishD
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=060517084254.ZM8380@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-users@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).