Hi,
I sent an email about determining if changes were done or not.
Unfortunately it seems something got messed up with my
subscription to the list so while I can see the answers in the
archives I can't reply to them directly (nor did I receive any
direct replies).
Anyway, thanks Yuri for the patch.
In the meantime I wrote my own patch, though I picked a different
route. I added a --force-progress output which makes mbsync always
output the progress information regardless if stdout is a TTY or
not. The patch is extremely simple, see attached.
Is this something you would consider including in mbsync? If not,
why? Can an alternative design be made? I really don't want to
maintain my own private tree of mbsync ;)
Kind regards,
Kristian.
diff --git a/src/main.c b/src/main.c
index eadd81f..027f28e 100644
--- a/src/main.c
+++ b/src/main.c
@@ -82,6 +82,7 @@ PACKAGE " " VERSION " - mailbox synchronizer\n"
" -c, --config CONFIG read an alternate config file (default: ~/." EXE "rc)\n"
" -D, --debug debugging modes (see manual)\n"
" -V, --verbose display what is happening\n"
+" --force-progress force progress output even when not on a TTY\n"
" -q, --quiet don't display progress counters\n"
" -v, --version display version\n"
" -h, --help display this help message\n"
@@ -455,6 +456,8 @@ main( int argc, char **argv )
DFlags |= VERYQUIET;
else
DFlags |= QUIET;
+ } else if (!strcmp( opt, "force-progress" )) {
+ DFlags |= PROGRESS;
} else if (!strcmp( opt, "verbose" )) {
DFlags |= VERBOSE;
} else if (starts_with( opt, -1, "debug", 5 )) {
--
Kristian Larsson
krist...@spritelink.net
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
