From: "Rudolf Sykora" <rudolf.sykora@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] environment + functions
Date: Wed, 8 Oct 2008 12:58:26 +0200 [thread overview]
Message-ID: <a560a5d00810080358p59422919n7aa79574e2de6071@mail.gmail.com> (raw)
In-Reply-To: <14ec7b180810071152i1dcdc311la333bfc3e737729d@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]
>
> it's done this way, i believe, to ensure that two rc shells running in
> the same namespaces do not step all over each others' environments. if
> you simply run 'rfork e' before you experiment with all those
> functions you won't see the empty files anywhere.
Sorry, but I don't understand... Could you give me some example?
> last note: once you've deleted the function with the 'fn' builtin
> you're free to remove the corresponding file in /env: it won't matter
> anymore. i'm sure rc can be changed to delete the file.
>
So, if I continuously want to add and remove functions within one shell
(running hypothetically forever), do I have to 'manually' delete those empty
left-behind files? --- that is, not only use
fn name_that_I _don't_need
but also
rm /env/'fn#name_that_I _don't_need' ?
(I was playing with this to have a prompt that reflects the last part of my
current directory. Following the example of setting fn term% { $*} I,
whenever I change a directory, define a similar function with an appropriate
name. When I change the directory again I do the same for the new one, but
also want to get rid of the old one... -- actually in the opposite order.)
Ruda
[-- Attachment #2: Type: text/html, Size: 1674 bytes --]
next prev parent reply other threads:[~2008-10-08 10:58 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
2008-10-07 18:52 ` andrey mirtchovski
2008-10-08 10:58 ` Rudolf Sykora [this message]
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=a560a5d00810080358p59422919n7aa79574e2de6071@mail.gmail.com \
--to=rudolf.sykora@gmail.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).