unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: "inwit" <inwit@sindominio.net>
To: "erik colson" <eco@ecocode.net>, <notmuch@notmuchmail.org>
Subject: Re: moving mail to another maildir based on tags and renaming files
Date: Tue, 24 May 2022 11:15:56 +0200	[thread overview]
Message-ID: <CK7VMK1DGF5M.2N5PP0T1B7IFR@bisio> (raw)
In-Reply-To: <87bkvndi3g.fsf@beavernet.be>

On Tue May 24, 2022 at 12:01 AM CEST, erik colson wrote:
> Do I understand correctly that I only have to remove the U=... part from
> the filename when moving a message?  That seems so easy I hardly believe
> it ;)

Yeah, that is correct. But it proved trickier than it seemed to me (thus the
safeMove2 attempt). 

I must confess that I've holding this tag/folder scheme for over a year now, and
that I'm more and more inclined to reduce the amount of folders that I keep
(I've recently fused 3 or 4 of my biggest folders into Archive, for example).
I'm trying to reduce my use of portable devices, and the truth is that search
engines offered by webmail are slowly getting better, so I feel less exposed by
not having my mail ranged in folders. I guess the whole tag-based paradigm is
also settling down on my mind, although I still feel that its nowadays a bit odd
to rely on a single local copy instead of a cloud-based solution. For this last
problem, there have been some interesting developments recently that I need to
investigate (precisely, the nmbug evolution).

Anyway, notmuch rocks. :)

  reply	other threads:[~2022-05-24  9:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23 21:02 moving mail to another maildir based on tags and renaming files erik colson
2022-05-23 21:19 ` inwit
2022-05-23 22:01   ` erik colson
2022-05-24  9:15     ` inwit [this message]
2022-05-24  9:45       ` erik colson
2022-05-24 12:26         ` David Bremner
2022-05-24 14:08           ` erik colson
2022-05-24  0:48 ` João Pedro
2022-05-24  8:49   ` erik colson

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=CK7VMK1DGF5M.2N5PP0T1B7IFR@bisio \
    --to=inwit@sindominio.net \
    --cc=eco@ecocode.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).