This at least fixes the "recent changes" page in gitit on my machine.

Note that the patch makes things like
    echo yy | darcs changes -i > out
impossible since as soon as the output is piped, changes is non-interactive.

2 patches for repository http://darcs.net:

Wed May  8 20:50:18 ART 2013  Guillaume Hoffmann <guillaumh@gmail.com>
  * resolve issue2319: make changes non-interactive if fed to a pipe

Wed May  8 21:57:53 ART 2013  Guillaume Hoffmann <guillaumh@gmail.com>
  * fix issue2270 test since piped darcs changes is now never interactive

Attachments

• patch-preview.txt
• resolve-issue2319_-make-changes-non_interactive-if-fed-to-a-pipe.dpatch
• unnamed

Is it easy (with the current flag handling structure) to always respect 
explicit flags? i.e. only the default behaviour would change depending on 
whether the output is a pipe

I think it's possible, but do we if someone scripts darcs like this?
Shall we wait for reactions?

A small fixup.

1 patch for repository http://darcs.net:

Fri Jun 14 20:57:31 ART 2013  "Guillaume Hoffmann" <guillaumh@gmail.com>
  * make changes non-interactive when given flags --count or --xml-output

Attachments

• make-changes-non_interactive-when-given-flags-__count-or-__xml_output-.dpatch
• patch-preview.txt
• unnamed

See <http://lists.osuosl.org/pipermail/darcs-users/2013-November/026966.html>
and the messages before it for the reasons behind this bundle.

3 patches for repository http://darcs.net:

Tue Nov 19 18:29:49 ART 2013  Guillaume Hoffmann <guillaumh@gmail.com>
  * Make changes non-interactive by default again

Tue Nov 19 19:32:27 ART 2013  Guillaume Hoffmann <guillaumh@gmail.com>
  * output darcs changes to a pager if more than 20 lines big

Tue Nov 19 20:24:32 ART 2013  Guillaume Hoffmann <guillaumh@gmail.com>
  * rename changes command to log, keep changes as alias

Attachments

• make-changes-non_interactive-by-default-again.dpatch
• patch-preview.txt
• unnamed

Patches are now in the screened branch!

Self-accepting.

Note that issue896 is still open.