From: Mike Hopkirk(hops) <ho...@sc...> - 2000-04-24 19:18:00
|
On Sat Apr 22,2000 (03:46:54AM -0700), uz...@li...(Joshua Uziel) wrote: > Since it causes no trouble and seemed approprate, I added the > functionality of the cscope.files config file to handle both > the -c and -k options. It made sense, and I admit that for > selfish reasons, it'll work well for a patch to the Linux > Kernel's Makefile I want to submit after the next release > of cscope (or maybe sooner, and I'll say it requires a version > later than 13.0, so CVS for now). > > Along with this is the thought... one of these two should > happen: > > a) cscope.files support be modified such that if no files are > listed, it treats the file as another means of supplying > options... and it goes and gets a default file list. > b) another confile file (cscope.config?) is added to do the > functionality described in a). cscope.dflt, cscope.rc, .cscoperc. Think its probably preferable to have this in a separate file (for base default values) looked for in home dir then cwd. (traditional rc file handling) Per project settings ( files and override switches) from cscope.files in cwd. The contents and parsing common to both. > I think this becomes more important once you have a -R option > instead of having to use cscope.files for large source trees. > What do you guys think? > > I also noticed that there's an undocumented -o "OGS" option. > What is this? Looks like it was some handling for some sort of help system hook (dead ended fossil ??) -- - hops Everything disclaimed (including disclaimer) ------<ho...@sc...>-------------------------------------- Mike Hopkirk (hops) | Whenever possible steal code. SCO Inc | Tom Duff. (ex) Bell Labs |