From: Jesse Rosenthal <jrosenthal@jhu.edu>
To: Sebastian Spaeth <Sebastian@SSpaeth.de>,
Jameson Rollins <jrollins@finestructure.net>,
notmuch@notmuchmail.org
Subject: Re: Fcc, Maildir, and Emacs message-mode -- a bit of code
Date: Fri, 29 Jan 2010 09:54:33 -0500 [thread overview]
Message-ID: <87mxzxyn9y.fsf@jhu.edu> (raw)
In-Reply-To: <87ockdoxl7.fsf@SSpaeth.de>
On Fri, 29 Jan 2010 14:21:56 +0100, Sebastian Spaeth <Sebastian@SSpaeth.de> wrote:
> First, I think this FCC method is phantastic and it works like a
> charm. I agree that we should include the snippets at least in some
> "contrib" directory (or doc/examples) to make it easier to find.
I'm glad it's proved useful. However, I should say that I'd be wary of
distributing it, or even recommending it, without at least rudimentary
error checking -- even if it's just the delivery function returning
either 0 or -1, and the emacs wrapper reporting failure back to the user
in a sensible fashion. As it is now, a failed delivery will either go
silently by, or muck everything up in a not-so-useful way.
Returning some sort of success/fail would just take a couple of
try/except lines. I would have put that in myself, but I just whipped it
up for personal use (and then never used it).
Best,
Jesse
next prev parent reply other threads:[~2010-01-29 14:55 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 18:36 Fcc, Maildir, and Emacs message-mode -- a bit of code Jesse Rosenthal
2010-01-27 14:44 ` Jameson Rollins
2010-01-29 13:21 ` Sebastian Spaeth
2010-01-29 14:46 ` Jameson Rollins
2010-01-29 14:54 ` Jesse Rosenthal [this message]
2010-04-07 20:04 ` Dirk Hohndel
2010-04-22 9:06 ` Sebastian Spaeth
2010-04-22 9:07 ` [PATCH 1/6] Add elisp file for FCC to maildir solution Sebastian Spaeth
2010-04-22 9:07 ` [PATCH] notmuch.el: Make notmuch-show buffer name first subject, instead of thread-id (supersedes V1--3) Sebastian Spaeth
2010-04-22 13:34 ` Sebastian Spaeth
2010-04-22 9:07 ` [PATCH 2/6] Integrate notmuch-maildir-fcc into notmuch Sebastian Spaeth
2010-04-22 9:07 ` [PATCH 3/6] notmuch-maildir-fcc: rename all jkr/* functions to notmuch-maildir-fcc-* Sebastian Spaeth
2010-04-22 9:07 ` [PATCH 4/6] add documentation example Sebastian Spaeth
2010-04-22 9:07 ` [PATCH 5/6] notmuch-maildir-fcc: use insert-buffer-substring Sebastian Spaeth
2010-04-22 9:07 ` [PATCH 6/6] notmuch-maildir-fcc: replace caddr with (car (cdr (cdr))) Sebastian Spaeth
2010-04-22 23:17 ` Fcc, Maildir, and Emacs message-mode -- a bit of code Dirk Hohndel
2010-04-23 7:13 ` Sebastian Spaeth
2010-04-23 10:08 ` Updated elisp FCC patches (was: Fcc, Maildir, and Emacs message-mode) Sebastian Spaeth
2010-04-23 14:01 ` Dirk Hohndel
2010-04-23 19:01 ` [PATCH 1/4] Add elisp file for FCC to maildir solution Sebastian Spaeth
2010-04-23 19:01 ` [PATCH 2/4] Integrate notmuch-maildir-fcc into notmuch Sebastian Spaeth
2010-04-23 19:01 ` [PATCH 3/4] notmuch-maildir-fcc: elisp syntax fixes Sebastian Spaeth
2010-04-23 19:01 ` [PATCH 4/4] Integrate notmuch-fcc mechansim Sebastian Spaeth
2010-04-23 9:38 ` [PATCH 7/7] " Sebastian Spaeth
2010-04-24 23:10 ` Dirk Hohndel
2010-04-26 8:23 ` [PATCH v3 1/4] Add elisp file for FCC to maildir solution Sebastian Spaeth
2010-04-26 21:21 ` Carl Worth
2010-04-26 8:23 ` [PATCH v3 2/4] Integrate notmuch-maildir-fcc into notmuch Sebastian Spaeth
2010-04-26 8:23 ` [PATCH v3 3/4] notmuch-maildir-fcc: elisp syntax fixes Sebastian Spaeth
2010-04-26 8:23 ` [PATCH v3 4/4] Integrate notmuch-fcc mechansim Sebastian Spaeth
2010-04-27 0:29 ` [PATCH] emacs: fcc should fail at the right time if it doesn't point to a maildir Jesse Rosenthal
2010-04-27 1:33 ` [PATCH] emacs: add prompt to create maildir for fcc if it does not exist Jesse Rosenthal
2010-04-27 3:08 ` [PATCH] emacs: Ensure that message-directory for Fcc has a trailing slash Jesse Rosenthal
2010-04-27 2:51 ` [PATCH] emacs: fcc should fail at the right time if it doesn't point to a maildir Dirk Hohndel
2010-04-27 6:10 ` Carl Worth
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=87mxzxyn9y.fsf@jhu.edu \
--to=jrosenthal@jhu.edu \
--cc=Sebastian@SSpaeth.de \
--cc=jrollins@finestructure.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).