Debates on default switches, or the rationale for defaults that
people have different opinions on. The purpose of this page is to
maintain a record of, and to provide a global overview on all
previous debates regarding default switches.

Please place your pros and cons here! This will help future debates
move along more quickly :-)

--set-scripts-executable
------------------------

`http://bugs.darcs.net/issue742 <http://bugs.darcs.net/issue742>`_

push/pull/send --set-default
----------------------------

send --edit-description
-----------------------

record --test
-------------


-  Current setting: --test is the default. Should --no-test be the
   default instead?
-  --test default
-  safer
-  maybe we can make send/push apply the selected patches (at
   once/in turn?) to the intersection of the repos, and do the tests
   at that time?
-  --no-test default
-  faster

check --test
------------

A test pref is usually used by record to check if the changes to
the repository fit criteria such as compiling or passing the test
suite. A fresh repository, or even one that doesn't compile, can
still be consistent. This command is designed to check for
consistency not whether it's okay to record your patch.


-  keep ``--test``as default:
-  switch to ``--no-test``as the default:
-  you can still use a post-hook to run a test.

changes --interactive
---------------------

Requested in
`http://bugs.darcs.net/issue1303 <http://bugs.darcs.net/issue1303>`_
. Makes "changes" consistent with other commands in being
interactive by default. Also it seems to be the more common and
friendly mode of "darcs changes".

--------------

`CategoryDevelopers <CategoryDevelopers>`_