From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: Zsh users <zsh-users@sunsite.dk>
Cc: kynn@panix.com
Subject: Re: IPC (or how to "bounce" a running zsh?)
Date: Thu, 23 Dec 2004 10:01:01 +0100 [thread overview]
Message-ID: <25051.1103792461@trentino.logica.co.uk> (raw)
> Is there any mechanism for interprocess communication in which at
> least one of the processes is a running zsh?
You can use a signal and trap it from the running zsh:
trap "source ~/.zshrc" USR1
Then just send the running zsh the USR1 signal. (kill -USR1).
In effect, signals are a simple form of communication. They are just
somewhat limited because you can't attach data when sending a signal.
Oliver
next reply other threads:[~2004-12-23 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-23 9:01 Oliver Kiddle [this message]
2004-12-23 17:03 ` kynn
-- strict thread matches above, loose matches on Subject: below --
2004-12-23 3:59 kynn
2004-12-23 4:13 ` Clint Adams
2004-12-23 4:53 ` kynn
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=25051.1103792461@trentino.logica.co.uk \
--to=okiddle@yahoo.co.uk \
--cc=kynn@panix.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).