From: "inwit" <inwit@sindominio.net>
To: <notmuch@notmuchmail.org>
Subject: Folder+tags
Date: Wed, 23 Dec 2020 12:53:14 +0100 [thread overview]
Message-ID: <C8057C8XE75K.3LCO6MVLH9IJR@bisio> (raw)
Hi!
This is my first message so I'll start by congratulating all the
community around notmuch. Great piece of work you have here!
I guess that my question must have been surely asked before, but I can't
seem to find it in the lists' archive. My excuses if it is the case that
my search abilities have failed. It has happened before.
So, what I'm trying is to have a notmuch system up and running while
preserving my folder structure fully functional in the IMAP server. I
know that most of you will agree that folders are a thing from the past,
but the fact is that, in the past, I've devoted quite a lot of time to
sort my mails, and now I have a 3-level subfolder structure which is
hard-wired in my brain, so up to now sometimes I'm still keen to
searching messages in their expected folders. I guess it's a matter of
time until I abandon this scheme and dive fully into tag based email,
but for the time being I'm afraid of losing that folder structure for
good.
Anyway, I've been reading all around the web about this, and the closest
I got is using the aerc client, where I can configure a Maildir worker
and a notmuch worker, being able to use the former for reading and
classifying mail into folders and the later for tag-based searching.
This works, but at the same time, no matter how exciting the development
of aerc is (and it is a beautiful little piece of code), it is still
very far from emacs mail-mode.
What I would like to, then, is to use notmuch-el to read and classify my
mail. And the functionality I'm missing at the moment is a way to move
an email from the inbox to its corresponding folder, hopefully updating
its folder tags at the same time. That is: I would (mb)sync my mail from
my company's IMAP server to my Maildir folder structure, then I'd go to
the Inbox tag/folder, I'd read my mail and then, by hitting Shift+m, for
example, I'd be able to move that precise email, both in files and tags,
to its corresponding Maildir folder, so my next call to mbsync actually
moves the message in the IMAP server folders as well. Does that make
sense? Does anyone know how would I get to something like that?
Again, sorry if this is redundant, and congratulations on the good work.
Salud,
next reply other threads:[~2020-12-23 12:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 11:53 inwit [this message]
2020-12-24 13:59 ` Folder+tags Alan Schmitt
2020-12-25 16:41 ` Folder+tags inwit
2020-12-25 8:04 ` Folder+tags Jaume Devesa
2020-12-25 17:27 ` Folder+tags inwit
2020-12-27 11:59 ` Folder+tags inwit
2020-12-27 13:12 ` Folder+tags Tomi Ollila
2020-12-27 17:14 ` Folder+tags inwit
2020-12-27 21:09 ` Folder+tags Tomi Ollila
2020-12-28 16:51 ` Folder+tags inwit
2021-01-03 18:09 ` Folder+tags inwit
2021-01-03 20:01 ` Folder+tags Tomi Ollila
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=C8057C8XE75K.3LCO6MVLH9IJR@bisio \
--to=inwit@sindominio.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).