Herbert said: > As we build up a new set of defaults we could then add > one more command > > set default <setup> > > where setup would be the name of a "standard" set of default > settings all packaged together (e.g. oldunix, oldwindows, > newcommon, etc.) This way we would not break any existing > scripts, but could move towards common choices that satisfy > current demands.
I think that this sounds like a *very* good idea. One thing ... it isn't clear to me why we would want to make the platform distinction (you said 'oldunix, oldwindows'). If there is a need to make some type of platform distinction, then we may want to consider a hyphenated or dotted name so that it could be optional: old old.unix old.windows Miguel ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Jmol-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jmol-users
