friendly ping I've started to actively use this in my mu4e setup: mbsync takes a while to sync all the mailboxes but I'm actually interested in being notified as early as possible only for one, the others are pretty much low-volume. So, I'm using
(setq mu4e-get-mail-command "cmdseq 10 \"mbsync op\" 1 \"mbsync -a\"") to sync everything only once every ten invocations. Omar Polo <[email protected]> writes: > Laurence Tratt <[email protected]> writes: > >> Please find attached a port for cmdseq-0.2 >> <https://tratt.net/laurie/src/cmdseq/>: >> >> cmdseq allows users to execute interleaved sequences of commands. Assuming >> the same counts and commands, on each execution cmdseq executes one of the >> commands, cycling through the sequence and wrapping back to the beginning >> when it is complete. For example, consider the following sequence: >> >> $ cmdseq 2 "echo cmd1" 1 "echo cmd2" >> cmd1 >> $ cmdseq 2 "echo cmd1" 1 "echo cmd2" >> cmd1 >> $ cmdseq 2 "echo cmd1" 1 "echo cmd2" >> cmd2 >> $ cmdseq 2 "echo cmd1" 1 "echo cmd2" >> cmd1 >> >> >> Laurie >> >> [2. application/x-tar-gz; cmdseq.tgz]... > > Hello, > > The port looks fine, I'd just switch HOMEPAGE to https, set PKG_ARCH=* > and drop CONFIGURE_STYLE. I'm attaching an updated tarball and a diff > against your Makefile. I'm sorry but I couldn't help myself to not > slightly tweak MASTER_SITES: I know I'm bikeshedding, but I think that > it's more readable, even if it has a couple of extra characters in it. > Just a suggestion, I'm obviously fine either the way :) > > The utility also works as advertised. It's ok for me to import it. > > I'd like to ask what's the intended usage though. Honestly, it seems > powerful to cycle different commands but -without having given it too > much thoughts- I can't come up with anything. I think it'd be > interesting so see some more elaborate examples of its usage. > > Cheers > > Omar Polo
cmdseq.tar.gz
Description: Binary data
