Comments on: Lazy environment variables http://existentialtype.net/2008/03/05/lazy-environment-variables/ For People Who Like Type and Types Thu, 10 May 2012 12:36:27 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: washburn http://existentialtype.net/2008/03/05/lazy-environment-variables/comment-page-1/#comment-21981 washburn Thu, 06 Mar 2008 10:01:52 +0000 http://existentialtype.net/2008/03/05/lazy-environment-variables/#comment-21981 @Matt: That is a reasonable solution for most things, I'll have to see if I can use it to simplify my <code>.zshrc</code> and <code>.zshenv</code> files. Unfortunately, it does not entirely solve the problem with special variables like <code>PATH</code> that you do not generally examine directly. The other issue is that in general this sort of thing is basically dynamic binding, so it might be nice to think about whether there is a better way to do things that would maintain lexical binding. @Matt: That is a reasonable solution for most things, I’ll have to see if I can use it to simplify my .zshrc and .zshenv files. Unfortunately, it does not entirely solve the problem with special variables like PATH that you do not generally examine directly.

The other issue is that in general this sort of thing is basically dynamic binding, so it might be nice to think about whether there is a better way to do things that would maintain lexical binding.

]]> By: Matt Hellige http://existentialtype.net/2008/03/05/lazy-environment-variables/comment-page-1/#comment-21978 Matt Hellige Wed, 05 Mar 2008 14:52:40 +0000 http://existentialtype.net/2008/03/05/lazy-environment-variables/#comment-21978 export FOO='$BAR/foo' export BAR=bar echo ${(e)FOO} That sort of does what you want. I have no idea if it's really a good idea... Shells are really ridiculous little languages. export FOO=’$BAR/foo’
export BAR=bar
echo ${(e)FOO}

That sort of does what you want. I have no idea if it’s really a good idea… Shells are really ridiculous little languages.

]]>