Previously in #notmuch we discussed how it would be convenient to
control part preferences on the basis of message attributes. This
patch is an attempt to provide that.
My own setting for `notmuch-multipart/alternative-discouraged' is:
(setq notmuch-multipart/alternative-discouraged
'(cond
Currently the preference for which sub-part of a multipart/alternative
part is shown is global. Allow to the user to override the settings on a
per-message basis by providing two new options:
- the ability to call a function that has access to the message to
return the discouraged type
On Tue 2016-01-12 11:44:18 -0500, David Bremner wrote:
> [gaudenz wrote:]
>> When sending encrypted mail the key lookup to encrypt to is done case
>> sensitive on the mail address. As mail addresses are case insensitive
>> this should be done case insensitive. Otherwise keys for users which
On Sun 2015-12-13 06:17:07 -0500, Tomi Ollila wrote:
> Actually now that I sent this mail it kept rolling on my mind... If anyone
> else than me (and libgpgme?) thinks that '.' should not be in search path
> we could do
fwiw, i agree that . should *not* be in the search path.
> if
On Thu 2016-01-14 16:20:59 -0500, Daniel Kahn Gillmor wrote:
> This suggests that if i include a bogus message-id in my References:
> list for any mail i send to a notmuch user, then access to their
> database will let me tell whether they ever saw it or not, regardless of
> whether they deleted
notmuch_database_remove_message has no leading underscore in its name.
---
lib/message.cc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/message.cc b/lib/message.cc
index 6894190..8d72ea2 100644
--- a/lib/message.cc
+++ b/lib/message.cc
@@ -728,7 +728,7 @@
