On Fri, Feb 24, 2017 at 12:11:47PM +0100, Yuri D'Elia wrote: > On Fri, Feb 24 2017, Oswald Buddenhagen wrote: > >> I'd like to know if, for instance, there's a transient failure (such as > >> connection error that I should not worry about). > >> > > really? your scriptlet below doesn't indicate that you do. what would > > you use it for? > > I don't want to post the entire script, as I do a lot more which is too > specific to be useful to others. But I do accumulate transient failures > and report an error if, for example, I get more than 3 consecutive ones > in a row and the system is actually online. > fair enough. but you could still use a notification fifo for that.
i thought some more about the format. json is trivial to parse in perl, but poses challenges in a shell script. the easiest would be actually something akin to mbsync's own config file: keyword followed by space and value (but without quoting), sections separated by an empty line: Store foo Box INBOX.bar UID 42 Action new Header-Subject you've got mail! Header-From Creative Correspondent <blubb@fake> Store baz Errno ECONNREFUSED this can be actually processed with a simple 'while read key value' loop. > >> It's actually quite simple and very powerful. I wouldn't be able to do > >> this in daemon mode, for example. > >> > > i see no inherent reason why that should be the case. > > I can control when and how to fetch just with cron. > There would be quite some extra stuff required in the daemon for such > fine control. > i think you're making some unwarranted assumptions as to what "daemon mode" should exactly be. > >> But I can actually avoid running the re-index in the vast majority of > >> the cases that even by combining them that it didn't seem necessary. > >> > > huh? > > Did you ever use "mu" or "notmuch"? > Most of what I'm doing is related to the way these tools work. > i know. i don't see how that correlates with the exit code (unnecessarily) reporting changes on the master side. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
