From: Dave K. <dku...@cu...> - 2003-08-17 21:51:51
|
On Sun, Aug 17, 2003 at 04:13:44PM +0300, Beni Cherniavsky wrote: > It's obvious that a user's file should override the system-wide file. > But why should it override the local per-directory config? This means > that one can't use user's file for defaults he likes for most projects > (the way the system-wide file would be used when users agree on the > same dafaults) - eny setting made there overrides all settings (except > command-line settings but that's awkward). > > The only rationale I can see it a user downloading complete > directories with reST sources and config files, and wishing to > override some settings globally, e.g. for his accessibility. However > this scenario is much less probable than processing one's own files, > in various projects, which frequently involves per-project settings. > > The current behavior makes no sense to me and I believe this should be > changed. I searched this thread and could not find mention of a seemingly obvious suggestion which I'm sure you must have considered: Most writers support a --config option. Why doesn't that give you what you want? It lets you override any config file, doesn't it? Anytime you want your personal config file to be used, you type: ... --config=~/.docutils And, whenever you want the project-specific one, you type: ... --confi=./docutils.conf Is it the configuration processing *after* the first config file that concerns you? Hoping for enlightenment that will teach me more clever uses of config files ... Dave -- Dave Kuhlman dku...@re... http://www.rexx.com/~dkuhlman |