From: arnold@skeeve.com
To: tuhs@tuhs.org, edouardklein@gmail.com
Subject: Re: [TUHS] Scratch files in csh
Date: Wed, 05 Jun 2019 06:50:28 -0600 [thread overview]
Message-ID: <201906051250.x55CoSxK005467@freefriends.org> (raw)
In-Reply-To: <87blzcmckd.fsf@plume.lan>
Edouard Klein <edouardklein@gmail.com> wrote:
> Hi all,
>
> I saw this on https://old.reddit.com/r/unix :
>
> http://blog.snailtext.com/posts/no-itch-to-scratch.html
>
> It's about (the lack of) scratch files in csh. Maybe somebody here know
> what happened to the feature ?
>
> Cheers,
>
> Edouard.
From the phraseology in the paper ("The system will remove ....") it sounds
to me like it was not a csh feature at all, but rather that the UCB
systems had a cron job to run something like
find / -name '#*' -mtime +7 -exec rm {} \;
It's easy enough to research this in the archives, if you have the energy.
:-)
HTH,
Arnold
next prev parent reply other threads:[~2019-06-05 12:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 12:38 Edouard Klein
2019-06-05 12:50 ` arnold [this message]
2019-06-05 13:05 ` Thomas Paulsen
2019-06-05 13:31 ` Clem Cole
2019-06-05 13:34 ` Clem Cole
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=201906051250.x55CoSxK005467@freefriends.org \
--to=arnold@skeeve.com \
--cc=edouardklein@gmail.com \
--cc=tuhs@tuhs.org \
/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).