zsh-workers
 help / color / mirror / code / Atom feed
From: Phil Pennock <comet@fysh.org>
To: Zsh Development Workers <zsh-workers@math.gatech.edu>
Subject: How sensible is ... ?
Date: Wed, 13 Jan 1999 10:26:26 +0000	[thread overview]
Message-ID: <19990113102626.A6200@fysh.org> (raw)

How good an idea would it be to add a shell-callable context builtin, or
a shell variable, to tell whether something is being run directly or as
a function call?  (I could be displaying ignorance of something that's
already there, I suppose)

Eg, have a directory of zsh scripts, which start:
#!/bin/zsh -f
case $context in
 toplevel) alias leave=exit ;;
 function) alias leave=return ;;
esac

the scripts could then be written such that zsh users could autoload
them and others could run them and get the same effective results.

These would of course be tricky, but I feel potentially more useful for
system administrators who want to provide a bunch of small fast
utilities for ALL users.

I don't particularly want to have to litter a directory with 5-line
scripts which always require fork-exec, I'd rather have a special
directory containing files as per above and have the relevant system
initialisation scripts sort out which PATH/FPATH it should go in.

Feedback welcome
-- 
--> Phil Pennock ; GAT d- s+:+ a23 C++(++++) UL++++/I+++/S+++/H+ P++@ L+++
E-@ W(+) N>++ o !K w--- O>+ M V !PS PE Y+ PGP+ t-- 5++ X+ R !tv b++>+++ DI+ D+
G+ e+ h* r y?


             reply	other threads:[~1999-01-13 10:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-13 10:26 Phil Pennock [this message]
1999-01-13 11:09 ` Phil Pennock
1999-01-13 11:17   ` Peter Stephenson
1999-01-13 12:01     ` Phil Pennock
1999-01-13 12:45       ` Peter Stephenson
1999-01-13 16:11         ` Bart Schaefer
1999-01-13 17:02           ` Phil Pennock

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=19990113102626.A6200@fysh.org \
    --to=comet@fysh.org \
    --cc=zsh-workers@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).