From 78fb99c32434e47bc664fb72315cafabc3458c94 Mon Sep 17 00:00:00 2001 From: "gaetan.lehmann@b47e4a12fac33bef53eafb0b41be69cae45edc1e" Date: Fri, 27 Nov 2015 19:16:53 +0000 Subject: [PATCH] --- ...stdout_isatty_when_reporting_progress.mdwn | 32 +++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100644 doc/bugs/git_annex_should_check_that_stdout_isatty_when_reporting_progress.mdwn diff --git a/doc/bugs/git_annex_should_check_that_stdout_isatty_when_reporting_progress.mdwn b/doc/bugs/git_annex_should_check_that_stdout_isatty_when_reporting_progress.mdwn new file mode 100644 index 0000000000..fec502b9e2 --- /dev/null +++ b/doc/bugs/git_annex_should_check_that_stdout_isatty_when_reporting_progress.mdwn @@ -0,0 +1,32 @@ +### Please describe the problem. + +git annex reports progress the same when when stdout is a terminal or not. +This is fine when stdout is actually a terminal, but produce lots of annoying characters when stdout is just a regular file. +This is problematic mostly when running git-annex with cron. + +### What steps will reproduce the problem? + +git annex copy --to myrepo > log + +then look at the content of log. + +### What version of git-annex are you using? On what operating system? + +5.20151019 + +Mac OS X 10.10.5 +Ubuntu 14.04 + +### Please provide any additional information below. + +[[!format sh """ +# If you can, paste a complete transcript of the problem occurring here. +# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log + + +# End of transcript or log. +"""]] + +### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders) + +