1. Summarise the issue (what were doing, what went wrong?)

The manual says (under 'darcs record'):

The -set-scripts-executable option causes scripts to be made executable
in the clean copy of the working tree, prior to running the test. See
`darcs get' for an explanation of the script heuristic.

But there is no such explanation under 'darcs get'.

2. What behaviour were you expecting instead?

For each command that supports this option, a hyperlink to some
explanation of the script detection heuristics. Should be a subsection
under 'Common options to darcs commands'.

We should fix this

(Man I do hope we sort the doc infrastructure out one day soon (the 
converging things to markdown, considering moving parts to the wiki, etc)

It seems easy (my humble opinion of course) to fix. I think I found 
where make the changes. But I can't find any information about the 
scripts heuristic.

I was searching for darcs.net/manual, where I find the subsection 
'Common options to darcs commands' :) So, I think that I will not find 
the info there jeje.

In cases like this one, one should assume that the only trustable
information is the source code itself, and possibly the communications
between developers when the relevant code was introduced or modified
(mailing lists, IRC). Fortunately, archives are available and
google-able.

You can do some archeology in the code itself by running `darcs log -i
--matches "hunk set-scripts"`. This will let you find all patches that
have the string set-scripts somewhere inside them.

Great! Just had found something of info in

src/Darcs/Repository/Internal.hs:949

using 'grep'. Good to know there are other way.

The following patch sent by Ale Gadea <alex.aegf@gmail.com> updated issue Issue2263 with
status=resolved;resolvedin=2.10.0 HEAD

* Resolve Issue2263: Option --set-scripts-executable is not properly documented 
Ignore-this: cdfff821ce91e6e5070fdcd62f0f3ad2