unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Michael J Gruber <git@grubix.eu>
Cc: "notmuch@notmuchmail.org" <notmuch@notmuchmail.org>
Subject: Re: Is there a reason why the trashed flag is not synced?
Date: Wed, 12 May 2021 14:52:59 -0500	[thread overview]
Message-ID: <CAMP44s2zTrsNwEM78BeCqqVFwTSJ9xVcB-Qnbj-o3rrgnvCzhA@mail.gmail.com> (raw)
In-Reply-To: <162080862357.6226.1101569739755943518.git@grubix.eu>

On Wed, May 12, 2021 at 3:37 AM Michael J Gruber <git@grubix.eu> wrote:

> But really, if you use folders as a tag substitute you should think
> about moving files to a trash folder rather than marking them trashed,
> in which case we don't have to worry about "T". (Notmuch's lack of
> T-syncing made me do this and it works fine.)

In my case trashed doesn't mean deleted, it means it's no longer
reachable from any of the directories I'm synchronizing.

Right now I'm only tracking a single label. If I remove that label
from the message in Gmail, that would translate as a trashed flag in
IMAP.

I'm not actually deleting anything, I just don't want to see those
messages in my notmuch client (thanks to excluded_tags).

-- 
Felipe Contreras

      reply	other threads:[~2021-05-12 19:53 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
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 [this message]

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=CAMP44s2zTrsNwEM78BeCqqVFwTSJ9xVcB-Qnbj-o3rrgnvCzhA@mail.gmail.com \
    --to=felipe.contreras@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).