In various conversations, people have suggested that we make hg status default to -mard in the .hgrc that hgsetup(1) will create for people.
I'm not certain the people suggesting this have, thus far, tried it, so I'll describe the resulting behaviour. with an entry: [defaults] status = -mard In an hgrc, the options specified will *always* be present when running 'hg status' For instance, my workspace contains many thousand unversioned files, and one modified file, $SRC/Makefile % hg st M usr/src/Makefile % hg st -u usr/src/Makefile M usr/src/Makefile % hg st -u | grep '^M' M usr/src/Makefile % hg st -u M usr/src/Makefile ? env/debug-bfu ? nohup.out ? usr/src/.build.tstamp ... thousands and thousands more lines ... Is this really the behaviour that people find desirable? I, personally, would have wanted options I specify to *completely* override the defaults, such that only the options I specify are used. (such that, with -u, above, usr/src/Makefile was not output). -- Rich (who's somewhat working on #444, and was asked to make this change as part of it)
