From: omgitsaheadcrab <omgitsaheadcrab@gmail.com>
To: Michael J Gruber <git@grubix.eu>
Cc: notmuch@notmuchmail.org
Subject: Re: Is there a reason why the trashed flag is not synced?
Date: Mon, 10 May 2021 15:45:23 +0100 [thread overview]
Message-ID: <CAMU84=e-js=RCnVjk+6btEsP_ZFpMsUeJxErH6RmWmwDjp-kng@mail.gmail.com> (raw)
In-Reply-To: <162065351282.5824.14225420932746058853.git@grubix.eu>
[-- Attachment #1.1: Type: text/plain, Size: 2239 bytes --]
My use is similar to Michael's.
That being said, I think giving users the option, assuming they are aware
of the risks,
is a good idea.
I do however think that this should be a separate flag as I dislike
extra options being bolted on to booleans.
On Mon, May 10, 2021 at 2:32 PM Michael J Gruber <git@grubix.eu> wrote:
> David Bremner venit, vidit, dixit 2021-05-10 14:04:27:
> > Felipe Contreras <felipe.contreras@gmail.com> writes:
> >
> > >
> > > It makes sense that by default synchronize_flags=true doesn't sync the
> > > trash flag, but what's wrong with a new configuration
> > > synchronize_flags=all that does?
> > >
> >
> > That seems plausible to me, but I'd like more input in case I missed
> > something.
>
> What happens if you have multiple copies of the same message, some "unseen"
> or "replied" etc.? notmuch synchronizes them with the flag on the
> message and in turn with all message copies, and this works "as
> expected" because, for example, there is no "unseen" flag but a "seen"
> flag.
>
> Well, partially. What happens if you mark a message unread (clear the
> "seen" flag) in one account? Notmuch will see a changed message file for
> one copy - will it reread all files for this mid and reconstruct the
> flags (thereby overwriting the unseen with the seen from the other one)?
> (Honest question, I don't know.)
>
> Deleting by chance is more harmful, yes. But is it more typical to clear
> out duplicate files using "T" or to delete a message (i.e. all it's file
> copies)? I'd even argue for the latter, at least for supporting
> "maildir.synchronize_deleted" in both directions. To be super-safe, one
> could special case this to take an AND of all message delete flags:
> "unread" already acts as if it was an AND of the unread flags of all
> copies (because it's the negation of an OR of seen flags).
>
> A one-sync, however, can be confusing, I'm afraid.
>
> Personally, I use trash folders synced with flags (through mbsync+afew,
> gmailieer) togther with the typical 30day clean-up. Has worked well so
> far.
>
> Cheers
> Michael
> _______________________________________________
> notmuch mailing list -- notmuch@notmuchmail.org
> To unsubscribe send an email to notmuch-leave@notmuchmail.org
>
[-- Attachment #1.2: Type: text/html, Size: 3052 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2021-05-10 14:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-08 23:24 Is there a reason why the trashed flag is not synced? Felipe Contreras
2021-05-09 9:38 ` David Bremner
2021-05-09 20:43 ` Felipe Contreras
2021-05-10 12:04 ` David Bremner
2021-05-10 13:31 ` Michael J Gruber
2021-05-10 14:45 ` omgitsaheadcrab [this message]
2021-05-11 6:23 ` Reto
2021-05-11 6:48 ` Michael J Gruber
2021-05-12 5:10 ` Reto
2021-05-12 8:37 ` Michael J Gruber
2021-05-12 19:52 ` Felipe Contreras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMU84=e-js=RCnVjk+6btEsP_ZFpMsUeJxErH6RmWmwDjp-kng@mail.gmail.com' \
--to=omgitsaheadcrab@gmail.com \
--cc=git@grubix.eu \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).