From: Ken Lareau <elessar@deepika.squonk.net>
To: Dan Nelson <dnelson@emsphone.com>
Cc: zsh-users@math.gatech.edu
Subject: Re: Simple way to get parent process name?
Date: Wed, 16 Sep 1998 09:09:34 -0400 [thread overview]
Message-ID: <199809161309.JAA06097@mailhost2.squonk.net> (raw)
In-Reply-To: Your message of "Tue, 15 Sep 1998 15:13:23 CDT." <19980915151323.A5205@emsphone.com>
In message <19980915151323.A5205@emsphone.com>, Dan Nelson writes:
>In the last episode (Sep 15), Ken Lareau said:
>> At my current job I compile a lot of various packages, and tend to
>> log my configuration, compilation and installation procedures for
>> future reference, using the 'script' command. To keep myself from
>> getting confused as to whether I was in a 'script' process or not, I
>> would have the shell prompt change to something else while running
>> 'script'.
>
>How about
>
>script () {
> export INSCRIPT
> (( INSCRIPT ++ ))
> command script "$@"
> (( INSCRIPT -- ))
>}
>
>then when you set your prompt, test to see if $INSCRIPT is > 0.
Thanks for the response; however, a more insidious problem has reared
it's head: both the above and my former method (modified to zsh, of
course) does not work, since the forking of a subshell doesn't reread
the startup scripts when 'script' is executed.
I have been unsuccessful in figuring out why this seems to happen, as
the documentation I've read doesn't give a clue... anyone have any
ideas on how to get around this little problem?
Ken Lareau
elessar@numenor.org
next prev parent reply other threads:[~1998-09-16 13:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-15 18:47 Ken Lareau
1998-09-15 20:13 ` Dan Nelson
1998-09-16 13:09 ` Ken Lareau [this message]
1998-09-16 16:08 ` /usr/bin/script annoyance Dan Nelson
1998-09-16 16:31 ` Ken Lareau
1998-09-16 16:41 ` Dan Nelson
1998-09-16 16:53 ` Ken Lareau
1998-09-16 17:13 ` Ken Lareau
1998-09-16 17:40 ` Bart Schaefer
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=199809161309.JAA06097@mailhost2.squonk.net \
--to=elessar@deepika.squonk.net \
--cc=dnelson@emsphone.com \
--cc=zsh-users@math.gatech.edu \
/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).