search

timm / crusty

Automatically exported from code.google.com/p/crusty
0 stars 0 forks source link

Give crusty its' own command #39

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Crusty is a configuration bundle to help users get a sweet setup of tools.
However, not everyone wants to have all of those configuration files
overridden in that manner, or they might only want to use the crusty
configs whenever they're using a crusty screen.

As such, I want to change crusty so that it places all the configs in the
user's .crusty directory. It will also have a new command, "crusty", that
get's placed in the user's bin directory. When the user runs crusty, it
starts up a screen session and everything within this crusty session would
use the crusty configs.

Original issue reported on code.google.com by jime...@gmail.com on 23 Jan 2007 at 9:36

GoogleCodeExporter commented 9 years ago 
Interesting idea- in this mode, crusty would not be invasive to current set up 
and
everything would disappear when you quit crusty.

But I think UNIX would defeat us here. CRUSTY= config for numerous packages. If 
you
wanted an optional use-crusty-then-quit to get back to your current environment 
then
you'd need to generate a cvim (crusty vim) cemacs (crusty emacs), cnews (crusty
snownews), etc etc

The core problem is that, unlike MULTICS, UNIX assumes that person to role is
one-to-one. Ideally, person to role is many-to-many and different config files,
environments, files, are magically awoken when you change roles.

So I'm going to close this issue, mark in "WONTFIX",  but I'd reopen it again if
someone can explain to me how to "role management" in UNIX.

Original comment by menzies....@gmail.com on 4 Feb 2007 at 4:34