From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] environment + functions
Date: Tue, 7 Oct 2008 14:33:36 -0400 [thread overview]
Message-ID: <99e3ea4960b4f984b860b700c3ec3b94@quanstro.net> (raw)
In-Reply-To: <a560a5d00810071131v10aeaba6tfd0f2a7caa91c1f1@mail.gmail.com>
> why after creating a function with
>
> fn my_func_name { something }
>
> and removing this function with
>
> fn my_func_name
>
> a file (though of zero size) exists in /env?
>
> (If I create a lot of functions and then want them be removed, I find a lot
> of for-me-uninteresting files in /env...)
good question. there are several interesting things about
how rc deals with the environment.
- erik
next prev parent reply other threads:[~2008-10-07 18:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 18:31 Rudolf Sykora
2008-10-07 18:33 ` erik quanstrom [this message]
2008-10-07 18:52 ` andrey mirtchovski
2008-10-08 10:58 ` Rudolf Sykora
2008-10-08 18:46 ` Pietro Gagliardi
2008-10-08 18:52 ` Rudolf Sykora
2008-10-08 19:12 ` erik quanstrom
2008-10-08 19:16 ` Pietro Gagliardi
2008-10-08 19:25 ` Rudolf Sykora
2008-10-08 11:35 erik quanstrom
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=99e3ea4960b4f984b860b700c3ec3b94@quanstro.net \
--to=quanstro@quanstro.net \
--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).