From: Mark Walters <markwalters1009@gmail.com>
To: notmuch@notmuchmail.org
Subject: [PATCH 0/6] Use notmuch insert for fcc
Date: Sat, 11 Jun 2016 00:02:46 +0100 [thread overview]
Message-ID: <1465599772-10297-1-git-send-email-markwalters1009@gmail.com> (raw)
This series allows the use of notmuch insert for fcc. It is rather
larger than I would like but I am fairly happy with the user
experience. A defcustom controls whether to use notmuch insert or file
fcc.
The syntax in the insert case is
Fcc: folder +tag1 -tag2
which inserts the message in folder, and +tag1 and -tag2 changes (if
present) are applied afterwards.
Since setting an fcc-header to "| notmuch insert --folder=sent"
essentially works, I will try to justify why the series ends this
big. The main reason is error handling: the pipe as above does no
error handling, so if the notmuch database is locked the fcc will be
silently lost. Unfortunately message-do-fcc which handles fcc is quite
inflexible and always passes full filename as fcc, which prevents the
syntax given above.
Thus to get this syntax we need to extract a local copy of
message-do-fcc which we simplify and rejig for our needs. The exact
rejigged form is in preparation for the postpone/resume/draft patches.
We could get rid of file fcc, but some people might still want it, and
it is used in the test suite, including by some non-emacs tests (via
emacs_fcc_message in test-lib.sh) so I am happier to keep it for now.
Best wishes
Mark
Mark Walters (6):
emacs: notmuch-check-exit-status bugfix
emacs: maildir-fcc: prepare for use of notmuch insert
emacs: maildir import message-do-fcc
emacs: simplify our local copy of message-do-fcc
Modify our local copy of message-do-fcc
emacs: maildir: add the actual insert code
emacs/notmuch-lib.el | 10 ++-
emacs/notmuch-maildir-fcc.el | 192 +++++++++++++++++++++++++++++++++++++------
emacs/notmuch-mua.el | 10 +--
test/test-lib.el | 5 ++
4 files changed, 185 insertions(+), 32 deletions(-)
--
2.1.4
next reply other threads:[~2016-06-10 23:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 23:02 Mark Walters [this message]
2016-06-10 23:02 ` [PATCH 1/6] emacs: notmuch-check-exit-status bugfix Mark Walters
2016-06-10 23:02 ` [PATCH 2/6] emacs: maildir-fcc: prepare for use of notmuch insert Mark Walters
2016-06-10 23:02 ` [PATCH 3/6] emacs: maildir import message-do-fcc Mark Walters
2016-06-10 23:02 ` [PATCH 4/6] emacs: simplify our local copy of message-do-fcc Mark Walters
2016-09-03 20:20 ` David Bremner
2016-09-03 21:42 ` Mark Walters
2016-09-03 22:36 ` David Bremner
2016-06-10 23:02 ` [PATCH 5/6] Modify " Mark Walters
2016-09-03 20:33 ` David Bremner
2016-09-03 21:39 ` Mark Walters
2016-09-03 22:37 ` David Bremner
2016-06-10 23:02 ` [PATCH 6/6] emacs: maildir: add the actual insert code Mark Walters
2016-09-03 20:43 ` [PATCH 0/6] Use notmuch insert for fcc David Bremner
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=1465599772-10297-1-git-send-email-markwalters1009@gmail.com \
--to=markwalters1009@gmail.com \
--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).