I can see what you are meaning here.

When I setup the paths/URLs I changed the db_static_url path & image path outside of the .cgi-bin. Presumably if I'd left the .css paths as they were, I would have been able to edit the style sheets through the template editor?

To explain what I'm trying to do-

I will have 5 installations (1 with 11 different template sets" with a unified design but the templates themselves will be different. My intention is to have all sites using the same core.css & then using the templateset.css.

My concern is that if I have all the custom.css labelled the same, and stored in different directories, I'll accidentally ftp the file into the wrong directory. If all templateset.css are stored in the one directory with different names, then I should not make this error.

I live in a remote area and depend on a slow connection ( what is broadband?) so editing on my own computer and then uploading the files is the only option open to me.

Perhaps this is too much of a change for the standard setup, and one I will have to implement myself. I'm not sure how many other people would find the change I suggested useful- particularly if the .css files can normally be edited through the template editor.