zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@brasslantern.com>
To: Peter Stephenson <pws@ibmth.df.unipi.it>,
	zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: PATCH: zsh-3.1.5-pws-5 + recent: typeset -T MYPATH mypath (finally!)
Date: Fri, 29 Jan 1999 08:56:29 -0800	[thread overview]
Message-ID: <990129085629.ZM6630@candle.brasslantern.com> (raw)
In-Reply-To: <9901281725.AA31711@ibmth.df.unipi.it>

On Jan 28,  6:25pm, Peter Stephenson wrote:
} Subject: PATCH: zsh-3.1.5-pws-5 + recent: typeset -T MYPATH mypath (finall
}
} Now I've tidied up bin_typeset() a bit, it's finally possible to make
} user-tiable path-like variables without the onset of suicidal
} feelings.

Cool.

} Also, typeset +T doesn't work.
} 
} Feel free to destruction test this.

There seem to be some differences between "special" tied variables and user
defined ones.  Not a big deal, but it should perhaps be documented (lest
anyone get the idea that the special variables could cease to be special).
The stuff at <17> through <19> below might even be considered a bug, though
it behaves the same way as it did before this patch.

zagzig<1> typeset -T BAR bar
zagzig<2> bar=(x y z)
zagzig<3> typeset -U bar
zagzig<4> echo $BAR
x:y:z
zagzig<5> BAR=a:b:c:d:a
zagzig<6> echo $bar
a b c d a
zagzig<7> bar=($bar)
zagzig<8> echo $BAR
a:b:c:d
zagzig<9> bar="oops"
zagzig<10> echo $BAR

zagzig<11> bar=(a b c d)
zagzig<12> echo $BAR

zagzig<13> path="oops"
zagzig<14> echo $PATH
oops
zagzig<15> unset path
zagzig<16> echo $PATH

zagzig<17> path=(/usr/local/bin /bin /usr/bin /usr/sbin)
zagzig<18> echo $PATH

zagzig<19> printenv PATH
/usr/local/bin:/bin:/usr/bin:/usr/sbin

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


      parent reply	other threads:[~1999-01-29 16:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-28 17:25 Peter Stephenson
1999-01-28 17:53 ` Bruce Stephens
1999-01-29 16:56 ` Bart Schaefer [this message]

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=990129085629.ZM6630@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=pws@ibmth.df.unipi.it \
    --cc=zsh-workers@sunsite.auc.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).