From: Karl Fogel <kfogel@red-bean.com>
To: notmuch@notmuchmail.org
Subject: [PATCH] emacs: add missing paren to fix defun in notmuch-address.el.
Date: Sat, 06 Apr 2013 14:33:26 -0400 [thread overview]
Message-ID: <87wqsfik5l.fsf@floss.red-bean.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 209 bytes --]
This patch fixes a trivial missing-paren problem in notmuch-address.el
(and reindents the following defun accordingly). I'm not subscribed
to this list, so please keep me CC'd on any followups.
Best,
-Karl
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Trivial fix to restore missing paren in notmuch-address.el. --]
[-- Type: text/x-diff, Size: 1619 bytes --]
From 4c74ad313f608f0834961c63c70d1f811ef103b7 Mon Sep 17 00:00:00 2001
From: Karl Fogel <kfogel@red-bean.com>
Date: Sat, 6 Apr 2013 13:21:54 -0400
Subject: [PATCH] emacs: add missing paren to close
`notmuch-bbdb/snarf-headers' definition.
This unbreaks emacs/notmuch-address.el. Without this fix,
the notmuch build process fails with this error:
$ make
...
In toplevel form:
emacs/notmuch.el:56:1:Error: End of file during parsing: \
/path/to/source/tree/notmuch/emacs/notmuch-address.el
make: *** [emacs/notmuch.elc] Error 1
$
---
emacs/notmuch-address.el | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/emacs/notmuch-address.el b/emacs/notmuch-address.el
index 32c8490..4eda098 100644
--- a/emacs/notmuch-address.el
+++ b/emacs/notmuch-address.el
@@ -107,13 +107,13 @@ line."
(let ((addrs (bbdb-get-addresses nil nil 'notmuch-bbdb/get-header-content))
(bbdb-get-addresses-headers headers) ; headers to read
(bbdb-gag-messages t)) ; suppress m/n processed message)
- (bbdb-update-records addrs t t))
+ (bbdb-update-records addrs t t)))
- (defun notmuch-bbdb/snarf-from ()
- "Import the sender of the current message into BBDB"
- (interactive)
- (notmuch-bbdb/snarf-headers
- (list (assoc 'authors bbdb-get-addresses-headers))))
+(defun notmuch-bbdb/snarf-from ()
+ "Import the sender of the current message into BBDB"
+ (interactive)
+ (notmuch-bbdb/snarf-headers
+ (list (assoc 'authors bbdb-get-addresses-headers))))
(defun notmuch-bbdb/snarf-to ()
"Import all recipients of the current message into BBDB"
--
1.7.10.4
next reply other threads:[~2013-04-06 18:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-06 18:33 Karl Fogel [this message]
2013-04-07 13:52 ` [PATCH] emacs: add missing paren to fix defun in notmuch-address.el David Bremner
2013-04-07 21:50 ` Karl Fogel
2013-04-08 8:16 ` Tomi Ollila
2013-04-08 8:40 ` Jani Nikula
2013-04-08 10:50 ` David Bremner
2013-04-09 1:12 ` Jed Brown
2013-04-09 6:32 ` Tomi Ollila
2013-04-09 11:50 ` David Bremner
2013-04-09 12:12 ` Tomi Ollila
2014-07-04 0:38 ` Sebastian Lipp
2014-07-04 0:56 ` Karl Fogel
2014-07-04 9:25 ` Sebastian Lipp
2014-07-05 18:18 ` Karl Fogel
2014-07-06 20:41 ` Sebastian Lipp
2014-07-07 17:35 ` Karl Fogel
2014-07-06 20:37 ` Sebastian Lipp
2014-07-07 17:40 ` Karl Fogel
2014-07-08 8:56 ` Tomi Ollila
2014-07-08 17:59 ` Karl Fogel
2014-07-04 16:31 ` 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=87wqsfik5l.fsf@floss.red-bean.com \
--to=kfogel@red-bean.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).