Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FolderNameFilter: allow multiple tags per folder #343

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

mjg
Copy link
Contributor

@mjg mjg commented Feb 28, 2024

So far, the last entry wins when a folder is specified multiple times as a folder transform. The reason is that the folder name is a key in a dict whose values are tags. On the other hand, if a message has copies in several folders then all these rules apply.

Change (fix?) afew's FolderNameFilter so that multiple transforms for the same folder lead to multiple tags being added. Technically, this is done by using sets as values in the transform dict.

In the future, we might think about implementing notmuch-tag style notation (with the obvious quoting issues).

@mjg
Copy link
Contributor Author

mjg commented Feb 28, 2024

FTR: CI runs stone age notmuch (0.29) against py 3.12 which is doomed to fail. The fix for ConfigParser in py 3.12 is in the latest notmuch 0.38 only.

So far, the last entry wins when a folder is specified multiple times as
a folder transform. The reason is that the folder name is a key in a
dict whose values are tags. On the other hand, if a message has copies
in several folders then all these rules apply.

Change (fix?) afew's FolderNameFilter so that multiple transforms for
the same folder lead to multiple tags being added. Technically, this is
done by using sets as values in the transform dict.

In the future, we might think about implementing notmuch-tag style
notation (with the obvious quoting issues).
@mjg mjg force-pushed the multiple-folder-name-transforms branch from 8edec78 to f67f100 Compare July 17, 2024 12:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant