zsh-users
 help / color / mirror / code / Atom feed
From: DervishD <disposable1@telefonica.net>
To: Zsh Users <zsh-users@sunsite.dk>
Subject: Making a script 'sourceable'
Date: Fri, 3 Sep 2004 18:35:09 +0200	[thread overview]
Message-ID: <20040903163509.GA12618@DervishD> (raw)

    Hi all :)

    Last month I asked here how to detect, portably, whether a script
had been sourced, and since then I've tried, with no success.

    That given, I'm trying to do two things. First one is detecting
the 'sourcing' non portably, in zsh. Checking for $SHLVL doesn't
work, because the user could have launched a new instance of zsh and
so SHLVL will appear increased even when sourceing. So what I'm
thinking about now is to check the value of the option 'interactive'.
If it is on, chances are that we have sourced the script. Otherwise,
we may not. This is not perfect, though, because you can run a script
(interactive=off) and then source the other script within...

    The second thing is derived from the above question: since
checking for 'sourcery' ;) is very difficult even non portably, I've
thought about making my zsh scripts sourceables. I thought that simply
doing 'emulate -L zsh' will do, since any change to options and
values will remain local to the script, but it won't work when
sourceing because the script is run in the current environment :(

    So I must, by hand, restore any changed variables, options and,
what more? Must I restore any other thing? Is there any simple way of
making scripts source-safe or source-aware?

    Thanks a lot in advance :)

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/


             reply	other threads:[~2004-09-03 16:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-03 16:35 DervishD [this message]
2004-09-03 17:01 ` Lloyd Zusman
2004-09-03 22:16   ` DervishD
2004-09-03 17:20 ` Bart Schaefer
2004-09-04 11:07 DervishD
2004-09-04 15:44 ` Bart Schaefer
2004-09-05 13:33   ` 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=20040903163509.GA12618@DervishD \
    --to=disposable1@telefonica.net \
    --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).