9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@coraid.com>
To: rudolf.sykora@gmail.com, 9fans@9fans.net
Subject: Re: [9fans] environment + functions
Date: Wed,  8 Oct 2008 15:12:02 -0400	[thread overview]
Message-ID: <6b1a2daf4ce120cb09f27b304854232e@coraid.com> (raw)
In-Reply-To: <a560a5d00810081152i2fdd24e6gf4f2fab9988e53b4@mail.gmail.com>

>
> Well... that's an answer, but not very constructive indeed. When do those
> files dissapear?

they don't.  but it shouldn't be a problem.
there's no explicit limit.  why don't you
sidestep the problem by using a space between
the fixed part and the path?

- erik



  reply	other threads:[~2008-10-08 19:12 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
2008-10-08 18:46     ` Pietro Gagliardi
2008-10-08 18:52       ` Rudolf Sykora
2008-10-08 19:12         ` erik quanstrom [this message]
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=6b1a2daf4ce120cb09f27b304854232e@coraid.com \
    --to=quanstro@coraid.com \
    --cc=9fans@9fans.net \
    --cc=rudolf.sykora@gmail.com \
    /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).