Observe the following listing:

| twb@baal[profile]$ darcs optimize
| 
| darcs failed:  Command optimize disabled by configuration!
| twb@baal[profile]$ cd ..
| twb@baal[canon]$ darcs optimize --repodir profile
| Done optimizing!
| twb@baal[canon]$

With --repodir, commands cannot be disabled or otherwise customized on
a per-repo basis.
-- 
Trent Buck

Trent,

Thanks for the bug report. This sounds like a bug to me, too. I'm assigning it
to myself temporarily to create a formal test case for it.

Trent,

I'm re-assigning this back to you in hopes that you'll submit your own test case
for it. The help would be appreciated! Otherwise, we'll get to it. 

See also:

tests/README.test_maintainers.txt

which provides an overview of the test suite setup. 

  Mark

Sat Feb  2 21:38:16 EST 2008  Trent W. Buck <twb@cyber.com.au>
  * Add functional sh test for issue496.

Sat Feb  2 21:38:48 EST 2008  Trent W. Buck <twb@cyber.com.au>
  * Don't use the builtin !; it has the wrong semantics.

Attachments

• add-functional-sh-test-for-issue496_.dpatch
• unnamed

Trent's test has been peer reviewed now, and moved to ./bugs, since it is failing. 

Thanks for the help, Trent!

The following patch updated the status of issue496 to be resolved in the unstable branch:

* resolved issue496 delayed the check for --disabled until after reading defaults. 
As it turns out, this bug was specific to the --disabled flag, which was
treated specially (and buggily, as it turns out).  It was easily fixed by
moving the check for Disabled *after* we've confirmed the validity of the
repository and added any default flags.

You can view the patch details online here: 
http://darcs.net/cgi-bin/darcs.cgi/unstable/?c=annotate&p=20080215154653-72aca-f5db321bbf0a8e863d52b78fd11941c939e3507c.gz