🚀 go-pugleaf

At the beginning of this month I announced the alpha test of  
WorkspaceHack, and it's finally ready for general release. You can get it  
on sonata.cc.purdue.edu as pub/next/submissions/WorkspaceHack1.0.tar.Z.
Here's part of the README:

This documents WorkspaceHack, a set of perl scripts that patches the  
binary of NeXT's Workspace application to add support for two new options  
in the defaults database. These defaults are completely independent, and  
you can choose to use either one, both, or none of them. The installation  
program never modifies the standard system Workspace, rather it creates a  
copy as ~/Apps/Workspace.app, and if you already have one there it makes a  
backup. A simple procedure, which I explain below, can restore your system  
to its original state.

Workspace CustomEmptyRecyclerSound

This is the name of a sound file. If this default is set, and the named  
file is a valid sound file, Workspace will play the sound when you empty  
the recycler. I used SuperHack to change my recycler to a toilet, so I  
naturally chose the flush.snd that's available on sonata.cc.purdue.edu in  
pub/next/submissions/sounds. This hack makes deleting files so much fun  
that your disk space problems will be gone forever!

Workspace CustomEnvironmentCommand

This lets you set up the environment variables of the Workspace program  
itself, so that all applications you launch from Workspace will have the  
environment you want them to have. This is useful in Terminal/Stuart type  
programs, where the current compromise is to have every new shell read  
your .login file, which may not be ideal. Having a flexible environment is  
especially important to TeXview users like myself who have expanded the  
TEXINPUTS, etc., variables. TeXview needs to know those variables. My  
previous compromise was never to start TeXview from Workspace, rather  
always from a shell.

The value of this default is a string that gets passed to the shell. That  
is, it's something you could type in your terminal window. The command  
must print on standard output the entire environment you want programs to  
see. The format is that produced by printenv. The value of this default I  
use is:

    csh -c "source ~/.environment; printenv"

The file .environment consists of a bunch of setenv commands.  There can  
be any shell commands there as long as whatever they print is something  
you want to go into your environment.

--
Chris Paris
cap+@cmu.edu (NeXT mail)