On Fri, Feb 17, 2012 at 08:10:01AM -0600, Jim Warner wrote: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=340751 Wow, 7 years ago. Reminds me I've been working on Debian for nearly 15 years. To me this would be an ideal list of things: * top is called top, I type top and get it. * I may have another top with another config file with the program called something else. This is Jim's clever little toprc hack and I can see why its useful. So perhaps I have ttop which is top showing threads, if I want that. * Newer tops, ideally, should read older toprc with some sane defaults for stuff that the older toprc doesn't cover. * If newer tops cannot understand some component in an old toprc they silently? ignore it. * You can somehow specify what toprc to use. Either command line or an option. * My preference is its a command-line option because you can do things with aliases then. This is what a lot of other programs do. * We can add Sami's script if required. * If you write out a toprc on a new top then old top probably won't like that, but then you shouldn't of done that in the first place. - Craig -- Craig Small VK2XLZ http://enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint: 5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5