| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
Don't synchronize maildir flags if the user doesn't want it.
|
| |
|
|
| |
Known broken, notmuch insert does not respect the config option.
|
| |
|
|
|
| |
There isn't a reported issue this would fix. Spotted by reading the
test.
|
| |
|
|
| |
Specifically test maildir flag syncing with insert.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
notmuch_message_tags_to_maildir_flags() unconditionally moves messages from
maildir directory "new/" to maildir directory "cur/", which makes messages lose
their "new" status in the MUA. However some users want to keep this "new"
status after, for instance, an auto-tagging of new messages.
However, as Austin mentioned and according to the maildir specification,
messages living in "new/" are not allowed to have flags, even if mutt allows it
to happen. For this reason, this patch prevents moving messages from "new/" to
"cur/", only if no flags have to be changed. It's hopefully enough to satisfy
mutt (and maybe other MUAs showing the "new" status) users checking the "new"
status.
Changelog:
* v2: Fix bool type as well as NULL returned despite having no errors (Austin
Clements)
* v4: Tag the related test (contributed by Michal Sojka) as working
Signed-off-by: Louis Rilling <l.rilling@av7.net>
[Condition for keeping messages in new/ was extended to satisfy all
tests from the previous patch. -Michal Sojka]
[Added by David Bremner, to keep the tests passing at each commit]
update insert tests for new maildir synchronization rules
As of id:1355952747-27350-4-git-send-email-sojkam1@fel.cvut.cz
we are more conservative about moving messages from ./new to ./cur.
This updates the insert tests to match
|
| |
|
|
| |
Add tests for notmuch insert --create-folder option.
|
| |
|
|
| |
Add tests for notmuch insert --folder option.
|
|
|
Add tests for new 'insert' command.
|
Jani Nikula
Louis Rilling
Peter Wang