From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] 9fans Digest, Vol 98, Issue 15
Date: Fri, 8 Jun 2012 20:15:45 -0400 [thread overview]
Message-ID: <d5a39bba73d085d321ee092b25031729@coraid.com> (raw)
In-Reply-To: <4FD28E5C.3020608@gmx.de>
> Ok, so I got the whole idea wrong, I guess. I thought that $var is
> basically just syntactic sugar for `{cat /env/var}, so referencing a
> variable would always read from /env ...
> I don't really understand how and why this is not the case though, but
> I'll try to find out by reading a few more manpages ...
it would then make sense to say $./fu. an idea i first heard
from mike haertel.
- erik
prev parent reply other threads:[~2012-06-09 0:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.286.1339197321.2642.9fans@9fans.net>
2012-06-08 23:44 ` Friedrich Psiorz
2012-06-08 23:51 ` Lyndon Nerenberg
2012-06-09 0:15 ` erik quanstrom [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=d5a39bba73d085d321ee092b25031729@coraid.com \
--to=quanstro@labs.coraid.com \
--cc=9fans@9fans.net \
/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.
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).