From: Felipe Contreras <felipe.contreras@gmail.com>
To: David Bremner <david@tethera.net>
Cc: "notmuch@notmuchmail.org" <notmuch@notmuchmail.org>
Subject: Re: Is there a reason why the trashed flag is not synced?
Date: Sun, 9 May 2021 15:43:17 -0500 [thread overview]
Message-ID: <CAMP44s0sgvFPYEk43JahhKyLOwnGQi+38H82jp=EDc-azZPymg@mail.gmail.com> (raw)
In-Reply-To: <87bl9kjlgo.fsf@tethera.net>
On Sun, May 9, 2021 at 4:38 AM David Bremner <david@tethera.net> wrote:
> Felipe Contreras <felipe.contreras@gmail.com> writes:
> > I understand deleting files is complex, but what's wrong with simply
> > tagging the T (trashed) messages as 'deleted'?
> >
> > I'm using synchronize_flags=true.
>
> The current lack of synchronization is intentional, with the reasoning
> explained in the commit message of [1]. I don't know if a one way sync
> (only from T -> deleted) has been discussed.
> https://git.notmuchmail.org/git/notmuch/commit/2c262042ac174d7bc96d6035ab9c88bd0abe7f35
This rationale makes sense to me, and I agree with the conclusion that
such behavior "can be potentially dangerous".
But the fact that something is potentially dangerous doesn't mean that
it necessarily is.
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 way it's the responsibility of the user to ensure that such
potentially dangerous behavior can't happen before doing
synchronize_flags=all.
Cheers.
--
Felipe Contreras
next prev parent reply other threads:[~2021-05-09 20:43 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 [this message]
2021-05-10 12:04 ` David Bremner
2021-05-10 13:31 ` Michael J Gruber
2021-05-10 14:45 ` omgitsaheadcrab
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='CAMP44s0sgvFPYEk43JahhKyLOwnGQi+38H82jp=EDc-azZPymg@mail.gmail.com' \
--to=felipe.contreras@gmail.com \
--cc=david@tethera.net \
--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).