Feature: allow setting autosync.interval in minutes

[quite]

It would be useful to be able to set autosync interval with greater granularity. I think minutes could be enough, seconds won't be needed.

To be backwards compatible, we'd move the setting to a string, and still interpret a clean number as days, but accept an m suffix for interpreting the number as minutes.

[AnomalRoil]

Autosync isn't run in the background when used in REPL mode, or is it?

Because iiuc it's run before another command if delay has passed, and optionally if set to 0, it's run every time a command is run, no?

So to me, having a granularity below a day is not really better than setting it to 0, no?

Or am I missing a use case?

Edit, sorry I misclicked on Close.

[quite]

Yes granularity of for example hours (or minutes, for completeness) would be much better than days. Consider that you may be showing/inserting a lot of passwords throughout the day, while (physically) moving between installations of gopass. Having for example 90m would be much better than 0. The former would possible help out greatly with getting things opportunistically synced. The latter would result in tedious sync all the time. And having 1 (day) given this use-case would result in a number of merge conflicts.

[AnomalRoil]

Closed in #2731