From: Sanjoy Mahajan <sanjoy@olin.edu>
To: <notmuch@notmuchmail.org>
Subject: slight workaround needed to use gnus-alias
Date: Thu, 12 May 2016 11:11:55 -0400 [thread overview]
Message-ID: <87lh3f1fb8.fsf@insight.mit.edu> (raw)
(I am using notmuch 0.22 from the Debian 0.22-1 package, in Emacs 24.5.1.)
I start gnus-alias in my message-setup-hook:
(add-hook 'message-setup-hook 'gnus-alias-determine-identity)
That worked fine until recently. Now it fails with the following error
(in the *Messages* buffer and minibuffer):
apply: Must be in `message-mode'.?
The problem is the following in gnus-alias.el:
(defun gnus-alias-ensure-message-mode ()
"Assert that the current buffer is a message buffer."
(when (not (eq major-mode 'message-mode))
(gnus-alias-error "Must be in `message-mode'.? ")))
The latest notmuch-mua.el doesn't use message-mode directly but rather
defines a derived mode:
(define-derived-mode notmuch-message-mode message-mode "Message[Notmuch]"
"Notmuch message composition mode. Mostly like `message-mode'"
(when notmuch-address-command
(notmuch-address-setup)))
I'm not sure what the best fix is. But I've done the following, which
works for me:
(require 'gnus-alias)
(gnus-alias-init)
;;; upstream version checks just for message-mode, but notmuch uses
;;; notmuch-message-mode, which is derived from message-mode
(defun gnus-alias-ensure-message-mode ()
"Assert that the current buffer is a message buffer."
(when (not (derived-mode-p 'notmuch-message-mode))
(gnus-alias-error "Must be in `message-mode' or mode derived from it. ")))
(add-hook 'message-setup-hook 'gnus-alias-determine-identity)
--
-Sanjoy
<http://savelongwharfpark.org/>
Save Long Wharf Park in Boston Harbor!
<http://streetfightingmath.com/>
Six reasoning tools to make hard problems easy.
next reply other threads:[~2016-05-12 15:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 15:11 Sanjoy Mahajan [this message]
2016-05-12 15:55 ` slight workaround needed to use gnus-alias David Bremner
2016-05-12 16:10 ` Sanjoy Mahajan
2016-05-12 16:23 ` David Bremner
2016-05-13 14:58 ` Sanjoy Mahajan
2016-05-13 22:45 ` 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=87lh3f1fb8.fsf@insight.mit.edu \
--to=sanjoy@olin.edu \
--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).