Sean Whitton writes:
>
> Either instead or in addition to something size-based, how about
> requiring --force if there do not exist any tags with the prefix in the
> notmuch database already? The size thing is brittle; in my scripting
> attempts, I've encountered several annoying edge cases.
>
Hello,
On Sat 07 May 2022 at 09:01pm -03, David Bremner wrote:
> Sean Whitton writes:
>
>> Just looking at my current usage, there are two cases where I've wrapped
>> nmbug in some additional myrepos scripting. The first is a status
>> command:
>>
>> status =
>> nmbug-spw status |
Sean Whitton writes:
> [please keep me CCed]
>
> Hello David,
>
> On Sat 23 Apr 2022 at 10:38am -03, David Bremner wrote:
>
> Just looking at my current usage, there are two cases where I've wrapped
> nmbug in some additional myrepos scripting. The first is a status
> command:
>
> status =
[please keep me CCed]
Hello David,
On Sat 23 Apr 2022 at 10:38am -03, David Bremner wrote:
> One of the things that new (and old) users of notmuch often miss is a
> way to sync tags between hosts. muchsync exists, but it's a third
> party tool, and (if I understand correctly) it directly
David Bremner writes:
> - the (new) man page is inadequate
> - notmuch git doesn't understand the common arguments to notmuch (--config
> and friends)
> - the defaults for prefix and git repo are wrong for most users. I was
> thinking about either a
> --nmbug argument to set the old
