2021-01-10 15:00:47 +01:00
|
|
|
;;; notmuch-mua.el --- emacs style mail-user-agent -*- lexical-binding: t -*-
|
2010-04-22 11:03:32 +02:00
|
|
|
;;
|
|
|
|
;; Copyright © David Edmondson
|
|
|
|
;;
|
|
|
|
;; This file is part of Notmuch.
|
|
|
|
;;
|
|
|
|
;; Notmuch is free software: you can redistribute it and/or modify it
|
|
|
|
;; under the terms of the GNU General Public License as published by
|
|
|
|
;; the Free Software Foundation, either version 3 of the License, or
|
|
|
|
;; (at your option) any later version.
|
|
|
|
;;
|
|
|
|
;; Notmuch is distributed in the hope that it will be useful, but
|
|
|
|
;; WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
|
|
|
;; General Public License for more details.
|
|
|
|
;;
|
|
|
|
;; You should have received a copy of the GNU General Public License
|
2016-06-02 18:26:14 +02:00
|
|
|
;; along with Notmuch. If not, see <https://www.gnu.org/licenses/>.
|
2010-04-22 11:03:32 +02:00
|
|
|
;;
|
|
|
|
;; Authors: David Edmondson <dme@dme.org>
|
|
|
|
|
2016-04-13 09:58:47 +02:00
|
|
|
;;; Code:
|
|
|
|
|
2020-04-25 22:18:07 +02:00
|
|
|
(eval-when-compile (require 'cl-lib))
|
|
|
|
|
2010-04-22 11:03:32 +02:00
|
|
|
(require 'message)
|
2012-05-05 21:30:37 +02:00
|
|
|
(require 'mm-view)
|
2012-03-18 17:32:42 +01:00
|
|
|
(require 'format-spec)
|
2010-04-22 11:03:32 +02:00
|
|
|
|
|
|
|
(require 'notmuch-lib)
|
2010-04-26 12:48:33 +02:00
|
|
|
(require 'notmuch-address)
|
2016-11-13 15:08:49 +01:00
|
|
|
(require 'notmuch-draft)
|
2019-04-12 14:01:11 +02:00
|
|
|
(require 'notmuch-message)
|
2010-04-22 11:03:32 +02:00
|
|
|
|
2016-02-20 19:24:38 +01:00
|
|
|
(declare-function notmuch-show-insert-body "notmuch-show" (msg body depth))
|
2016-02-06 18:55:43 +01:00
|
|
|
(declare-function notmuch-fcc-header-setup "notmuch-maildir-fcc" ())
|
2016-09-04 00:59:40 +02:00
|
|
|
(declare-function notmuch-maildir-message-do-fcc "notmuch-maildir-fcc" ())
|
2016-11-13 15:08:48 +01:00
|
|
|
(declare-function notmuch-draft-postpone "notmuch-draft" ())
|
|
|
|
(declare-function notmuch-draft-save "notmuch-draft" ())
|
2013-09-01 19:59:53 +02:00
|
|
|
|
2021-01-10 15:00:47 +01:00
|
|
|
(defvar notmuch-show-indent-multipart)
|
|
|
|
(defvar notmuch-show-insert-header-p-function)
|
|
|
|
(defvar notmuch-show-max-text-part-size)
|
|
|
|
(defvar notmuch-show-insert-text/plain-hook)
|
|
|
|
|
emacs: make headings outline-minor-mode compatible
`outline-minor-mode' treats comments that begin with three or more
semicolons as headings. That makes it very convenient to navigate
code and to show/hide parts of a file.
Elips libraries typically have four top-level sections, e.g.:
;;; notmuch.el --- run notmuch within emacs...
;;; Commentary:...
;;; Code:...
;;; notmuch.el ends here
In this package many libraries lack a "Commentary:" section, which is
not optimal but okay for most libraries, except major entry points.
Depending on how one chooses to look at it, the "... ends here" line
is not really a heading that begins a section, because it should never
have a "section" body (after all it marks eof).
If the file is rather short, then I left "Code:" as the only section
that contains code. Otherwise I split the file into multiple sibling
sections. The "Code:" section continues to contain `require' and
`declare-function' forms and other such "front matter".
If and only if I have split the code into multiple sections anyway,
then I also added an additional section named just "_" before the
`provide' form and shortly before the "...end here" line. This
section could also be called "Back matter", but I feel it would be
distracting to be that explicit about it. (The IMO unnecessary but
unfortunately still obligatory "... ends here" line is already
distracting enough as far as I am concerned.)
Before this commit some libraries already uses section headings, some
of them consistently. When a library already had some headings, then
this commit often sticks to that style, even at the cost inconsistent
styling across all libraries.
A very limited number of variable and function definitions have to be
moved around because they would otherwise end up in sections they do
not belong into.
Sections, including but not limited to their heading, can and should
be further improved in the future.
2021-01-10 15:00:46 +01:00
|
|
|
;;; Options
|
2010-04-22 11:03:32 +02:00
|
|
|
|
2020-09-12 06:45:40 +02:00
|
|
|
(defcustom notmuch-mua-send-hook nil
|
2010-04-22 11:03:32 +02:00
|
|
|
"Hook run before sending messages."
|
2012-01-16 11:38:33 +01:00
|
|
|
:type 'hook
|
|
|
|
:group 'notmuch-send
|
|
|
|
:group 'notmuch-hooks)
|
2010-04-22 11:03:32 +02:00
|
|
|
|
2012-05-04 12:37:56 +02:00
|
|
|
(defcustom notmuch-mua-compose-in 'current-window
|
2020-11-16 22:28:24 +01:00
|
|
|
"Where to create the mail buffer used to compose a new message.
|
2012-05-04 12:37:56 +02:00
|
|
|
Possible values are `current-window' (default), `new-window' and
|
|
|
|
`new-frame'. If set to `current-window', the mail buffer will be
|
|
|
|
displayed in the current window, so the old buffer will be
|
|
|
|
restored when the mail buffer is killed. If set to `new-window'
|
|
|
|
or `new-frame', the mail buffer will be displayed in a new
|
|
|
|
window/frame that will be destroyed when the buffer is killed.
|
|
|
|
You may want to customize `message-kill-buffer-on-exit'
|
|
|
|
accordingly."
|
|
|
|
:group 'notmuch-send
|
|
|
|
:type '(choice (const :tag "Compose in the current window" current-window)
|
|
|
|
(const :tag "Compose mail in a new window" new-window)
|
|
|
|
(const :tag "Compose mail in a new frame" new-frame)))
|
|
|
|
|
2016-08-09 01:35:17 +02:00
|
|
|
(defcustom notmuch-mua-user-agent-function nil
|
2020-11-16 22:28:28 +01:00
|
|
|
"Function used to generate a `User-Agent:' string.
|
|
|
|
If this is `nil' then no `User-Agent:' will be generated."
|
2011-12-20 20:53:14 +01:00
|
|
|
:type '(choice (const :tag "No user agent string" nil)
|
|
|
|
(const :tag "Full" notmuch-mua-user-agent-full)
|
|
|
|
(const :tag "Notmuch" notmuch-mua-user-agent-notmuch)
|
|
|
|
(const :tag "Emacs" notmuch-mua-user-agent-emacs)
|
|
|
|
(function :tag "Custom user agent function"
|
2012-01-16 11:38:33 +01:00
|
|
|
:value notmuch-mua-user-agent-full))
|
|
|
|
:group 'notmuch-send)
|
2010-04-22 11:03:32 +02:00
|
|
|
|
2016-08-09 01:35:17 +02:00
|
|
|
(defcustom notmuch-mua-hidden-headers nil
|
2020-11-16 22:28:29 +01:00
|
|
|
"Headers that are added to the `message-mode' hidden headers list."
|
2012-01-16 11:38:33 +01:00
|
|
|
:type '(repeat string)
|
|
|
|
:group 'notmuch-send)
|
2010-04-26 13:50:59 +02:00
|
|
|
|
2015-01-14 20:57:49 +01:00
|
|
|
(defgroup notmuch-reply nil
|
|
|
|
"Replying to messages in notmuch"
|
|
|
|
:group 'notmuch)
|
|
|
|
|
|
|
|
(defcustom notmuch-mua-cite-function 'message-cite-original
|
2020-11-16 22:28:31 +01:00
|
|
|
"Function for citing an original message.
|
|
|
|
|
2015-01-14 20:57:49 +01:00
|
|
|
Predefined functions include `message-cite-original' and
|
2020-11-16 22:28:31 +01:00
|
|
|
`message-cite-original-without-signature'. Note that these
|
|
|
|
functions use `mail-citation-hook' if that is non-nil."
|
2015-01-14 20:57:49 +01:00
|
|
|
:type '(radio (function-item message-cite-original)
|
|
|
|
(function-item message-cite-original-without-signature)
|
|
|
|
(function-item sc-cite-original)
|
|
|
|
(function :tag "Other"))
|
|
|
|
:link '(custom-manual "(message)Insertion Variables")
|
|
|
|
:group 'notmuch-reply)
|
|
|
|
|
2016-02-20 19:24:40 +01:00
|
|
|
(defcustom notmuch-mua-reply-insert-header-p-function
|
2016-03-16 09:19:55 +01:00
|
|
|
'notmuch-show-reply-insert-header-p-never
|
2016-02-20 19:24:40 +01:00
|
|
|
"Function to decide which parts get a header when replying.
|
|
|
|
|
|
|
|
This function specifies which parts of a mime message with
|
2018-03-18 03:30:25 +01:00
|
|
|
multiple parts get a header."
|
2016-03-16 09:19:55 +01:00
|
|
|
:type '(radio (const :tag "No part headers"
|
2020-08-08 13:49:38 +02:00
|
|
|
notmuch-show-reply-insert-header-p-never)
|
2016-03-16 09:19:55 +01:00
|
|
|
(const :tag "All except multipart/* and hidden parts"
|
2020-08-08 13:49:38 +02:00
|
|
|
notmuch-show-reply-insert-header-p-trimmed)
|
2016-02-20 19:24:40 +01:00
|
|
|
(const :tag "Only for included text parts"
|
2020-08-08 13:49:38 +02:00
|
|
|
notmuch-show-reply-insert-header-p-minimal)
|
2016-02-20 19:24:40 +01:00
|
|
|
(const :tag "Exactly as in show view"
|
2020-08-08 13:49:38 +02:00
|
|
|
notmuch-show-insert-header-p)
|
2016-02-20 19:24:40 +01:00
|
|
|
(function :tag "Other"))
|
|
|
|
:group 'notmuch-reply)
|
|
|
|
|
2018-09-08 23:40:40 +02:00
|
|
|
(defcustom notmuch-mua-attachment-regexp
|
|
|
|
"\\b\\(attache\?ment\\|attached\\|attach\\|pi[èe]ce\s+jointe?\\)\\b"
|
|
|
|
"Message body text indicating that an attachment is expected.
|
|
|
|
|
|
|
|
This is not used unless `notmuch-mua-attachment-check' is added
|
2019-04-15 15:35:19 +02:00
|
|
|
to `notmuch-mua-send-hook'."
|
|
|
|
:type 'regexp
|
|
|
|
:group 'notmuch-send)
|
2018-09-08 23:40:40 +02:00
|
|
|
|
emacs: make headings outline-minor-mode compatible
`outline-minor-mode' treats comments that begin with three or more
semicolons as headings. That makes it very convenient to navigate
code and to show/hide parts of a file.
Elips libraries typically have four top-level sections, e.g.:
;;; notmuch.el --- run notmuch within emacs...
;;; Commentary:...
;;; Code:...
;;; notmuch.el ends here
In this package many libraries lack a "Commentary:" section, which is
not optimal but okay for most libraries, except major entry points.
Depending on how one chooses to look at it, the "... ends here" line
is not really a heading that begins a section, because it should never
have a "section" body (after all it marks eof).
If the file is rather short, then I left "Code:" as the only section
that contains code. Otherwise I split the file into multiple sibling
sections. The "Code:" section continues to contain `require' and
`declare-function' forms and other such "front matter".
If and only if I have split the code into multiple sections anyway,
then I also added an additional section named just "_" before the
`provide' form and shortly before the "...end here" line. This
section could also be called "Back matter", but I feel it would be
distracting to be that explicit about it. (The IMO unnecessary but
unfortunately still obligatory "... ends here" line is already
distracting enough as far as I am concerned.)
Before this commit some libraries already uses section headings, some
of them consistently. When a library already had some headings, then
this commit often sticks to that style, even at the cost inconsistent
styling across all libraries.
A very limited number of variable and function definitions have to be
moved around because they would otherwise end up in sections they do
not belong into.
Sections, including but not limited to their heading, can and should
be further improved in the future.
2021-01-10 15:00:46 +01:00
|
|
|
;;; Various functions
|
2010-04-22 11:03:32 +02:00
|
|
|
|
2018-09-08 23:40:40 +02:00
|
|
|
(defun notmuch-mua-attachment-check ()
|
|
|
|
"Signal an error if the message text indicates that an
|
|
|
|
attachment is expected but no MML referencing an attachment is
|
|
|
|
found.
|
|
|
|
|
|
|
|
Typically this is added to `notmuch-mua-send-hook'."
|
|
|
|
(when (and
|
|
|
|
;; When the message mentions attachment...
|
|
|
|
(save-excursion
|
|
|
|
(message-goto-body)
|
2019-12-13 00:35:35 +01:00
|
|
|
;; Limit search from reaching other possible parts of the message
|
|
|
|
(let ((search-limit (search-forward "\n<#" nil t)))
|
|
|
|
(message-goto-body)
|
2020-04-25 22:18:07 +02:00
|
|
|
(cl-loop while (re-search-forward notmuch-mua-attachment-regexp
|
|
|
|
search-limit t)
|
|
|
|
;; For every instance of the "attachment" string
|
|
|
|
;; found, examine the text properties. If the text
|
|
|
|
;; has either a `face' or `syntax-table' property
|
|
|
|
;; then it is quoted text and should *not* cause the
|
|
|
|
;; user to be asked about a missing attachment.
|
|
|
|
if (let ((props (text-properties-at (match-beginning 0))))
|
|
|
|
(not (or (memq 'syntax-table props)
|
|
|
|
(memq 'face props))))
|
|
|
|
return t
|
|
|
|
finally return nil)))
|
2018-09-08 23:40:40 +02:00
|
|
|
;; ...but doesn't have a part with a filename...
|
|
|
|
(save-excursion
|
|
|
|
(message-goto-body)
|
|
|
|
(not (re-search-forward "^<#part [^>]*filename=" nil t)))
|
|
|
|
;; ...and that's not okay...
|
|
|
|
(not (y-or-n-p "Attachment mentioned, but no attachment - is that okay?")))
|
|
|
|
;; ...signal an error.
|
|
|
|
(error "Missing attachment")))
|
|
|
|
|
2012-05-04 12:37:56 +02:00
|
|
|
(defun notmuch-mua-get-switch-function ()
|
|
|
|
"Get a switch function according to `notmuch-mua-compose-in'."
|
|
|
|
(cond ((eq notmuch-mua-compose-in 'current-window)
|
|
|
|
'switch-to-buffer)
|
|
|
|
((eq notmuch-mua-compose-in 'new-window)
|
|
|
|
'switch-to-buffer-other-window)
|
|
|
|
((eq notmuch-mua-compose-in 'new-frame)
|
|
|
|
'switch-to-buffer-other-frame)
|
|
|
|
(t (error "Invalid value for `notmuch-mua-compose-in'"))))
|
|
|
|
|
|
|
|
(defun notmuch-mua-maybe-set-window-dedicated ()
|
2020-11-16 22:28:29 +01:00
|
|
|
"Set the selected window as dedicated according to `notmuch-mua-compose-in'."
|
2012-05-04 12:37:56 +02:00
|
|
|
(when (or (eq notmuch-mua-compose-in 'new-frame)
|
|
|
|
(eq notmuch-mua-compose-in 'new-window))
|
|
|
|
(set-window-dedicated-p (selected-window) t)))
|
|
|
|
|
2010-04-22 11:03:32 +02:00
|
|
|
(defun notmuch-mua-user-agent-full ()
|
|
|
|
"Generate a `User-Agent:' string suitable for notmuch."
|
|
|
|
(concat (notmuch-mua-user-agent-notmuch)
|
|
|
|
" "
|
|
|
|
(notmuch-mua-user-agent-emacs)))
|
|
|
|
|
|
|
|
(defun notmuch-mua-user-agent-notmuch ()
|
|
|
|
"Generate a `User-Agent:' string suitable for notmuch."
|
2015-08-02 16:48:14 +02:00
|
|
|
(let ((notmuch-version (if (string= notmuch-emacs-version "unknown")
|
|
|
|
(notmuch-cli-version)
|
|
|
|
notmuch-emacs-version)))
|
2016-06-02 18:26:14 +02:00
|
|
|
(concat "Notmuch/" notmuch-version " (https://notmuchmail.org)")))
|
2010-04-22 11:03:32 +02:00
|
|
|
|
|
|
|
(defun notmuch-mua-user-agent-emacs ()
|
|
|
|
"Generate a `User-Agent:' string suitable for notmuch."
|
|
|
|
(concat "Emacs/" emacs-version " (" system-configuration ")"))
|
|
|
|
|
2010-04-26 13:50:59 +02:00
|
|
|
(defun notmuch-mua-add-more-hidden-headers ()
|
|
|
|
"Add some headers to the list that are hidden by default."
|
|
|
|
(mapc (lambda (header)
|
2020-08-08 13:49:42 +02:00
|
|
|
(unless (member header message-hidden-headers)
|
2010-04-26 13:50:59 +02:00
|
|
|
(push header message-hidden-headers)))
|
|
|
|
notmuch-mua-hidden-headers))
|
|
|
|
|
2014-04-05 11:18:06 +02:00
|
|
|
(defun notmuch-mua-reply-crypto (parts)
|
2014-04-14 21:40:50 +02:00
|
|
|
"Add mml sign-encrypt flag if any part of original message is encrypted."
|
2020-04-25 22:18:07 +02:00
|
|
|
(cl-loop for part in parts
|
2020-08-08 13:49:36 +02:00
|
|
|
if (notmuch-match-content-type (plist-get part :content-type)
|
|
|
|
"multipart/encrypted")
|
|
|
|
do (mml-secure-message-sign-encrypt)
|
|
|
|
else if (notmuch-match-content-type (plist-get part :content-type)
|
|
|
|
"multipart/*")
|
|
|
|
do (notmuch-mua-reply-crypto (plist-get part :content))))
|
2014-04-05 11:18:06 +02:00
|
|
|
|
2020-11-16 22:28:24 +01:00
|
|
|
;; There is a bug in Emacs' message.el that results in a newline
|
2012-04-01 17:24:23 +02:00
|
|
|
;; not being inserted after the References header, so the next header
|
|
|
|
;; is concatenated to the end of it. This function fixes the problem,
|
|
|
|
;; while guarding against the possibility that some current or future
|
|
|
|
;; version of emacs has the bug fixed.
|
|
|
|
(defun notmuch-mua-insert-references (original-func header references)
|
|
|
|
(funcall original-func header references)
|
|
|
|
(unless (bolp) (insert "\n")))
|
|
|
|
|
emacs: make headings outline-minor-mode compatible
`outline-minor-mode' treats comments that begin with three or more
semicolons as headings. That makes it very convenient to navigate
code and to show/hide parts of a file.
Elips libraries typically have four top-level sections, e.g.:
;;; notmuch.el --- run notmuch within emacs...
;;; Commentary:...
;;; Code:...
;;; notmuch.el ends here
In this package many libraries lack a "Commentary:" section, which is
not optimal but okay for most libraries, except major entry points.
Depending on how one chooses to look at it, the "... ends here" line
is not really a heading that begins a section, because it should never
have a "section" body (after all it marks eof).
If the file is rather short, then I left "Code:" as the only section
that contains code. Otherwise I split the file into multiple sibling
sections. The "Code:" section continues to contain `require' and
`declare-function' forms and other such "front matter".
If and only if I have split the code into multiple sections anyway,
then I also added an additional section named just "_" before the
`provide' form and shortly before the "...end here" line. This
section could also be called "Back matter", but I feel it would be
distracting to be that explicit about it. (The IMO unnecessary but
unfortunately still obligatory "... ends here" line is already
distracting enough as far as I am concerned.)
Before this commit some libraries already uses section headings, some
of them consistently. When a library already had some headings, then
this commit often sticks to that style, even at the cost inconsistent
styling across all libraries.
A very limited number of variable and function definitions have to be
moved around because they would otherwise end up in sections they do
not belong into.
Sections, including but not limited to their heading, can and should
be further improved in the future.
2021-01-10 15:00:46 +01:00
|
|
|
;;; Mua reply
|
|
|
|
|
2012-01-14 15:46:17 +01:00
|
|
|
(defun notmuch-mua-reply (query-string &optional sender reply-all)
|
2017-07-17 17:06:11 +02:00
|
|
|
(let ((args '("reply" "--format=sexp" "--format-version=4"))
|
2014-04-05 11:18:06 +02:00
|
|
|
(process-crypto notmuch-show-process-crypto)
|
2012-03-18 17:32:42 +01:00
|
|
|
reply
|
|
|
|
original)
|
2014-04-05 11:18:06 +02:00
|
|
|
(when process-crypto
|
2017-12-19 17:40:55 +01:00
|
|
|
(setq args (append args '("--decrypt=true"))))
|
2012-01-14 15:46:17 +01:00
|
|
|
(if reply-all
|
|
|
|
(setq args (append args '("--reply-to=all")))
|
|
|
|
(setq args (append args '("--reply-to=sender"))))
|
2011-05-26 03:01:19 +02:00
|
|
|
(setq args (append args (list query-string)))
|
2013-07-06 14:49:51 +02:00
|
|
|
;; Get the reply object as SEXP, and parse it into an elisp object.
|
2013-06-24 01:43:18 +02:00
|
|
|
(setq reply (apply #'notmuch-call-notmuch-sexp args))
|
2012-03-18 17:32:42 +01:00
|
|
|
;; Extract the original message to simplify the following code.
|
|
|
|
(setq original (plist-get reply :original))
|
|
|
|
;; Extract the headers of both the reply and the original message.
|
|
|
|
(let* ((original-headers (plist-get original :headers))
|
|
|
|
(reply-headers (plist-get reply :reply-headers)))
|
|
|
|
;; If sender is non-nil, set the From: header to its value.
|
|
|
|
(when sender
|
|
|
|
(plist-put reply-headers :From sender))
|
|
|
|
(let
|
|
|
|
;; Overlay the composition window on that being used to read
|
|
|
|
;; the original message.
|
|
|
|
((same-window-regexps '("\\*mail .*")))
|
2020-08-08 13:49:36 +02:00
|
|
|
;; We modify message-header-format-alist to get around
|
|
|
|
;; a bug in message.el. See the comment above on
|
|
|
|
;; notmuch-mua-insert-references.
|
2012-04-01 17:24:23 +02:00
|
|
|
(let ((message-header-format-alist
|
2020-04-25 22:18:07 +02:00
|
|
|
(cl-loop for pair in message-header-format-alist
|
|
|
|
if (eq (car pair) 'References)
|
|
|
|
collect (cons 'References
|
|
|
|
(apply-partially
|
|
|
|
'notmuch-mua-insert-references
|
|
|
|
(cdr pair)))
|
|
|
|
else
|
|
|
|
collect pair)))
|
2012-04-01 17:24:23 +02:00
|
|
|
(notmuch-mua-mail (plist-get reply-headers :To)
|
2017-09-26 20:26:08 +02:00
|
|
|
(notmuch-sanitize (plist-get reply-headers :Subject))
|
2012-05-04 12:37:56 +02:00
|
|
|
(notmuch-headers-plist-to-alist reply-headers)
|
|
|
|
nil (notmuch-mua-get-switch-function))))
|
2020-08-08 13:49:36 +02:00
|
|
|
;; Create a buffer-local queue for tag changes triggered when
|
|
|
|
;; sending the reply.
|
2019-04-12 14:01:11 +02:00
|
|
|
(when notmuch-message-replied-tags
|
|
|
|
(setq-local notmuch-message-queued-tag-changes
|
|
|
|
(list (cons query-string notmuch-message-replied-tags))))
|
2012-03-18 17:32:42 +01:00
|
|
|
;; Insert the message body - but put it in front of the signature
|
2013-09-06 16:32:18 +02:00
|
|
|
;; if one is present, and after any other content
|
|
|
|
;; message*setup-hooks may have added to the message body already.
|
|
|
|
(save-restriction
|
|
|
|
(message-goto-body)
|
|
|
|
(narrow-to-region (point) (point-max))
|
|
|
|
(goto-char (point-max))
|
|
|
|
(if (re-search-backward message-signature-separator nil t)
|
2020-08-08 13:49:43 +02:00
|
|
|
(when message-signature-insert-empty-line
|
|
|
|
(forward-line -1))
|
2013-09-06 16:32:18 +02:00
|
|
|
(goto-char (point-max))))
|
2012-03-18 17:32:42 +01:00
|
|
|
(let ((from (plist-get original-headers :From))
|
|
|
|
(date (plist-get original-headers :Date))
|
|
|
|
(start (point)))
|
2015-01-14 20:57:49 +01:00
|
|
|
;; notmuch-mua-cite-function constructs a citation line based
|
|
|
|
;; on the From and Date headers of the original message, which
|
|
|
|
;; are assumed to be in the buffer.
|
2012-03-18 17:32:42 +01:00
|
|
|
(insert "From: " from "\n")
|
|
|
|
(insert "Date: " date "\n\n")
|
2020-08-08 13:49:36 +02:00
|
|
|
(insert
|
|
|
|
(with-temp-buffer
|
|
|
|
(let
|
|
|
|
;; Don't attempt to clean up messages, excerpt
|
|
|
|
;; citations, etc. in the original message before
|
|
|
|
;; quoting.
|
|
|
|
((notmuch-show-insert-text/plain-hook nil)
|
|
|
|
;; Don't omit long parts.
|
|
|
|
(notmuch-show-max-text-part-size 0)
|
|
|
|
;; Insert headers for parts as appropriate for replying.
|
|
|
|
(notmuch-show-insert-header-p-function
|
|
|
|
notmuch-mua-reply-insert-header-p-function)
|
|
|
|
;; Ensure that any encrypted parts are
|
|
|
|
;; decrypted during the generation of the reply
|
|
|
|
;; text.
|
|
|
|
(notmuch-show-process-crypto process-crypto)
|
|
|
|
;; Don't indent multipart sub-parts.
|
|
|
|
(notmuch-show-indent-multipart nil))
|
|
|
|
;; We don't want sigstatus buttons (an information leak and usually wrong anyway).
|
|
|
|
(cl-letf (((symbol-function 'notmuch-crypto-insert-sigstatus-button) #'ignore)
|
|
|
|
((symbol-function 'notmuch-crypto-insert-encstatus-button) #'ignore))
|
|
|
|
(notmuch-show-insert-body original (plist-get original :body) 0)
|
|
|
|
(buffer-substring-no-properties (point-min) (point-max))))))
|
2012-03-18 17:32:42 +01:00
|
|
|
(set-mark (point))
|
|
|
|
(goto-char start)
|
|
|
|
;; Quote the original message according to the user's configured style.
|
2015-01-14 20:57:49 +01:00
|
|
|
(funcall notmuch-mua-cite-function)))
|
2014-04-14 21:40:50 +02:00
|
|
|
;; Crypto processing based crypto content of the original message
|
2014-04-05 11:18:06 +02:00
|
|
|
(when process-crypto
|
|
|
|
(notmuch-mua-reply-crypto (plist-get original :body))))
|
2014-03-28 19:04:25 +01:00
|
|
|
;; Push mark right before signature, if any.
|
|
|
|
(message-goto-signature)
|
|
|
|
(unless (eobp)
|
|
|
|
(end-of-line -1))
|
2012-03-18 17:32:42 +01:00
|
|
|
(push-mark)
|
|
|
|
(message-goto-body)
|
|
|
|
(set-buffer-modified-p nil))
|
2010-04-22 11:03:32 +02:00
|
|
|
|
emacs: make headings outline-minor-mode compatible
`outline-minor-mode' treats comments that begin with three or more
semicolons as headings. That makes it very convenient to navigate
code and to show/hide parts of a file.
Elips libraries typically have four top-level sections, e.g.:
;;; notmuch.el --- run notmuch within emacs...
;;; Commentary:...
;;; Code:...
;;; notmuch.el ends here
In this package many libraries lack a "Commentary:" section, which is
not optimal but okay for most libraries, except major entry points.
Depending on how one chooses to look at it, the "... ends here" line
is not really a heading that begins a section, because it should never
have a "section" body (after all it marks eof).
If the file is rather short, then I left "Code:" as the only section
that contains code. Otherwise I split the file into multiple sibling
sections. The "Code:" section continues to contain `require' and
`declare-function' forms and other such "front matter".
If and only if I have split the code into multiple sections anyway,
then I also added an additional section named just "_" before the
`provide' form and shortly before the "...end here" line. This
section could also be called "Back matter", but I feel it would be
distracting to be that explicit about it. (The IMO unnecessary but
unfortunately still obligatory "... ends here" line is already
distracting enough as far as I am concerned.)
Before this commit some libraries already uses section headings, some
of them consistently. When a library already had some headings, then
this commit often sticks to that style, even at the cost inconsistent
styling across all libraries.
A very limited number of variable and function definitions have to be
moved around because they would otherwise end up in sections they do
not belong into.
Sections, including but not limited to their heading, can and should
be further improved in the future.
2021-01-10 15:00:46 +01:00
|
|
|
;;; Mode and keymap
|
|
|
|
|
2020-11-08 20:02:46 +01:00
|
|
|
(defvar notmuch-message-mode-map
|
|
|
|
(let ((map (make-sparse-keymap)))
|
|
|
|
(define-key map (kbd "C-c C-c") #'notmuch-mua-send-and-exit)
|
|
|
|
(define-key map (kbd "C-c C-s") #'notmuch-mua-send)
|
|
|
|
(define-key map (kbd "C-c C-p") #'notmuch-draft-postpone)
|
|
|
|
(define-key map (kbd "C-x C-s") #'notmuch-draft-save)
|
|
|
|
map)
|
|
|
|
"Keymap for `notmuch-message-mode'.")
|
|
|
|
|
2015-08-01 11:44:56 +02:00
|
|
|
(define-derived-mode notmuch-message-mode message-mode "Message[Notmuch]"
|
2020-05-24 21:17:56 +02:00
|
|
|
"Notmuch message composition mode. Mostly like `message-mode'."
|
2016-05-20 22:13:02 +02:00
|
|
|
(notmuch-address-setup))
|
2015-08-01 11:44:55 +02:00
|
|
|
|
2015-11-03 22:02:12 +01:00
|
|
|
(put 'notmuch-message-mode 'flyspell-mode-predicate 'mail-mode-flyspell-verify)
|
|
|
|
|
emacs: make headings outline-minor-mode compatible
`outline-minor-mode' treats comments that begin with three or more
semicolons as headings. That makes it very convenient to navigate
code and to show/hide parts of a file.
Elips libraries typically have four top-level sections, e.g.:
;;; notmuch.el --- run notmuch within emacs...
;;; Commentary:...
;;; Code:...
;;; notmuch.el ends here
In this package many libraries lack a "Commentary:" section, which is
not optimal but okay for most libraries, except major entry points.
Depending on how one chooses to look at it, the "... ends here" line
is not really a heading that begins a section, because it should never
have a "section" body (after all it marks eof).
If the file is rather short, then I left "Code:" as the only section
that contains code. Otherwise I split the file into multiple sibling
sections. The "Code:" section continues to contain `require' and
`declare-function' forms and other such "front matter".
If and only if I have split the code into multiple sections anyway,
then I also added an additional section named just "_" before the
`provide' form and shortly before the "...end here" line. This
section could also be called "Back matter", but I feel it would be
distracting to be that explicit about it. (The IMO unnecessary but
unfortunately still obligatory "... ends here" line is already
distracting enough as far as I am concerned.)
Before this commit some libraries already uses section headings, some
of them consistently. When a library already had some headings, then
this commit often sticks to that style, even at the cost inconsistent
styling across all libraries.
A very limited number of variable and function definitions have to be
moved around because they would otherwise end up in sections they do
not belong into.
Sections, including but not limited to their heading, can and should
be further improved in the future.
2021-01-10 15:00:46 +01:00
|
|
|
;;; New messages
|
|
|
|
|
2016-01-02 17:47:45 +01:00
|
|
|
(defun notmuch-mua-pop-to-buffer (name switch-function)
|
2020-11-16 22:28:29 +01:00
|
|
|
"Pop to buffer NAME, and warn if it already exists and is modified.
|
|
|
|
Like `message-pop-to-buffer' but enable `notmuch-message-mode'
|
|
|
|
instead of `message-mode' and SWITCH-FUNCTION is mandatory."
|
2015-12-21 10:41:15 +01:00
|
|
|
(let ((buffer (get-buffer name)))
|
|
|
|
(if (and buffer
|
|
|
|
(buffer-name buffer))
|
|
|
|
(let ((window (get-buffer-window buffer 0)))
|
|
|
|
(if window
|
|
|
|
;; Raise the frame already displaying the message buffer.
|
|
|
|
(progn
|
2018-10-04 11:45:45 +02:00
|
|
|
(select-frame-set-input-focus (window-frame window))
|
2015-12-21 10:41:15 +01:00
|
|
|
(select-window window))
|
2016-01-02 17:47:45 +01:00
|
|
|
(funcall switch-function buffer)
|
2015-12-21 10:41:15 +01:00
|
|
|
(set-buffer buffer))
|
|
|
|
(when (and (buffer-modified-p)
|
|
|
|
(not (prog1
|
|
|
|
(y-or-n-p
|
|
|
|
"Message already being composed; erase? ")
|
|
|
|
(message nil))))
|
|
|
|
(error "Message being composed")))
|
2016-01-02 17:47:45 +01:00
|
|
|
(funcall switch-function name)
|
2015-12-21 10:41:15 +01:00
|
|
|
(set-buffer name))
|
|
|
|
(erase-buffer)
|
|
|
|
(notmuch-message-mode)))
|
|
|
|
|
|
|
|
(defun notmuch-mua-mail (&optional to subject other-headers continue
|
|
|
|
switch-function yank-action send-actions
|
|
|
|
return-action &rest ignored)
|
|
|
|
"Invoke the notmuch mail composition window."
|
2010-04-22 11:03:32 +02:00
|
|
|
(interactive)
|
|
|
|
(when notmuch-mua-user-agent-function
|
|
|
|
(let ((user-agent (funcall notmuch-mua-user-agent-function)))
|
2020-08-08 13:49:42 +02:00
|
|
|
(unless (string= "" user-agent)
|
2012-04-01 17:24:21 +02:00
|
|
|
(push (cons 'User-Agent user-agent) other-headers))))
|
|
|
|
(unless (assq 'From other-headers)
|
2016-04-08 23:43:27 +02:00
|
|
|
(push (cons 'From (message-make-from
|
2020-08-08 13:49:36 +02:00
|
|
|
(notmuch-user-name)
|
|
|
|
(notmuch-user-primary-email)))
|
|
|
|
other-headers))
|
2016-01-02 17:47:45 +01:00
|
|
|
(notmuch-mua-pop-to-buffer (message-buffer-name "mail" to)
|
2020-08-08 13:49:36 +02:00
|
|
|
(or switch-function
|
|
|
|
(notmuch-mua-get-switch-function)))
|
2016-01-02 17:47:44 +01:00
|
|
|
(let ((headers
|
2016-01-06 22:28:45 +01:00
|
|
|
(append
|
|
|
|
;; The following is copied from `message-mail'
|
2016-01-02 17:47:44 +01:00
|
|
|
`((To . ,(or to "")) (Subject . ,(or subject "")))
|
|
|
|
;; C-h f compose-mail says that headers should be specified as
|
|
|
|
;; (string . value); however all the rest of message expects
|
|
|
|
;; headers to be symbols, not strings (eg message-header-format-alist).
|
2016-06-02 18:26:14 +02:00
|
|
|
;; https://lists.gnu.org/archive/html/emacs-devel/2011-01/msg00337.html
|
2016-01-02 17:47:44 +01:00
|
|
|
;; We need to convert any string input, eg from rmail-start-mail.
|
|
|
|
(dolist (h other-headers other-headers)
|
2020-08-08 13:49:43 +02:00
|
|
|
(when (stringp (car h))
|
|
|
|
(setcar h (intern (capitalize (car h))))))))
|
2016-04-30 08:51:48 +02:00
|
|
|
;; Cause `message-setup-1' to do things relevant for mail,
|
|
|
|
;; such as observe `message-default-mail-headers'.
|
|
|
|
(message-this-is-mail t))
|
2020-11-16 22:28:23 +01:00
|
|
|
(message-setup-1 headers yank-action send-actions return-action))
|
2015-08-01 11:44:56 +02:00
|
|
|
(notmuch-fcc-header-setup)
|
2010-04-26 13:22:40 +02:00
|
|
|
(message-sort-headers)
|
2010-04-26 16:01:25 +02:00
|
|
|
(message-hide-headers)
|
|
|
|
(set-buffer-modified-p nil)
|
2012-05-04 12:37:56 +02:00
|
|
|
(notmuch-mua-maybe-set-window-dedicated)
|
2010-04-26 16:01:25 +02:00
|
|
|
(message-goto-to))
|
2010-04-22 11:03:32 +02:00
|
|
|
|
2011-05-26 10:41:30 +02:00
|
|
|
(defcustom notmuch-identities nil
|
|
|
|
"Identities that can be used as the From: address when composing a new message.
|
|
|
|
|
|
|
|
If this variable is left unset, then a list will be constructed from the
|
|
|
|
name and addresses configured in the notmuch configuration file."
|
2012-01-16 11:38:33 +01:00
|
|
|
:type '(repeat string)
|
|
|
|
:group 'notmuch-send)
|
2011-05-26 10:41:30 +02:00
|
|
|
|
2011-05-26 19:22:41 +02:00
|
|
|
(defcustom notmuch-always-prompt-for-sender nil
|
2011-05-28 23:51:55 +02:00
|
|
|
"Always prompt for the From: address when composing or forwarding a message.
|
|
|
|
|
|
|
|
This is not taken into account when replying to a message, because in that case
|
|
|
|
the From: header is already filled in by notmuch."
|
2012-01-16 11:38:33 +01:00
|
|
|
:type 'boolean
|
|
|
|
:group 'notmuch-send)
|
2011-05-26 19:22:41 +02:00
|
|
|
|
2011-05-26 10:41:30 +02:00
|
|
|
(defvar notmuch-mua-sender-history nil)
|
|
|
|
|
|
|
|
(defun notmuch-mua-prompt-for-sender ()
|
2014-02-27 19:10:54 +01:00
|
|
|
"Prompt for a sender from the user's configured identities."
|
|
|
|
(if notmuch-identities
|
|
|
|
(ido-completing-read "Send mail from: " notmuch-identities
|
|
|
|
nil nil nil 'notmuch-mua-sender-history
|
|
|
|
(car notmuch-identities))
|
|
|
|
(let* ((name (notmuch-user-name))
|
|
|
|
(addrs (cons (notmuch-user-primary-email)
|
|
|
|
(notmuch-user-other-email)))
|
|
|
|
(address
|
|
|
|
(ido-completing-read (concat "Sender address for " name ": ") addrs
|
|
|
|
nil nil nil 'notmuch-mua-sender-history
|
|
|
|
(car addrs))))
|
2016-04-08 23:43:27 +02:00
|
|
|
(message-make-from name address))))
|
2011-05-26 10:41:30 +02:00
|
|
|
|
2013-10-06 05:22:47 +02:00
|
|
|
(put 'notmuch-mua-new-mail 'notmuch-prefix-doc "... and prompt for sender")
|
2011-05-26 10:41:31 +02:00
|
|
|
(defun notmuch-mua-new-mail (&optional prompt-for-sender)
|
2013-10-06 05:22:47 +02:00
|
|
|
"Compose new mail.
|
2011-05-26 10:41:31 +02:00
|
|
|
|
|
|
|
If PROMPT-FOR-SENDER is non-nil, the user will be prompted for
|
|
|
|
the From: address first."
|
|
|
|
(interactive "P")
|
|
|
|
(let ((other-headers
|
2020-08-08 13:49:41 +02:00
|
|
|
(and (or prompt-for-sender notmuch-always-prompt-for-sender)
|
|
|
|
(list (cons 'From (notmuch-mua-prompt-for-sender))))))
|
2012-05-04 12:37:56 +02:00
|
|
|
(notmuch-mua-mail nil nil other-headers nil (notmuch-mua-get-switch-function))))
|
2011-05-26 10:41:31 +02:00
|
|
|
|
2016-02-08 12:34:21 +01:00
|
|
|
(defun notmuch-mua-new-forward-messages (messages &optional prompt-for-sender)
|
|
|
|
"Compose a new message forwarding MESSAGES.
|
|
|
|
|
|
|
|
If PROMPT-FOR-SENDER is non-nil, the user will be prompteed for
|
|
|
|
the From: address."
|
|
|
|
(let* ((other-headers
|
2020-08-08 13:49:41 +02:00
|
|
|
(and (or prompt-for-sender notmuch-always-prompt-for-sender)
|
|
|
|
(list (cons 'From (notmuch-mua-prompt-for-sender)))))
|
2020-08-08 13:49:38 +02:00
|
|
|
;; Comes from the first message and is applied later.
|
|
|
|
forward-subject
|
|
|
|
;; List of accumulated message-references of forwarded messages.
|
|
|
|
forward-references
|
|
|
|
;; List of corresponding message-query.
|
|
|
|
forward-queries)
|
2016-02-08 12:34:21 +01:00
|
|
|
;; Generate the template for the outgoing message.
|
|
|
|
(notmuch-mua-mail nil "" other-headers nil (notmuch-mua-get-switch-function))
|
|
|
|
(save-excursion
|
|
|
|
;; Insert all of the forwarded messages.
|
|
|
|
(mapc (lambda (id)
|
|
|
|
(let ((temp-buffer (get-buffer-create
|
|
|
|
(concat "*notmuch-fwd-raw-" id "*"))))
|
|
|
|
;; Get the raw version of this message in the buffer.
|
|
|
|
(with-current-buffer temp-buffer
|
|
|
|
(erase-buffer)
|
|
|
|
(let ((coding-system-for-read 'no-conversion))
|
2020-08-08 13:49:36 +02:00
|
|
|
(call-process notmuch-command nil t nil
|
|
|
|
"show" "--format=raw" id))
|
2016-02-08 12:34:21 +01:00
|
|
|
;; Because we process the messages in reverse order,
|
|
|
|
;; always generate a forwarded subject, then use the
|
|
|
|
;; last (i.e. first) one.
|
2019-04-12 14:01:10 +02:00
|
|
|
(setq forward-subject (message-make-forward-subject))
|
2019-04-12 14:01:12 +02:00
|
|
|
(push (message-fetch-field "Message-ID") forward-references)
|
|
|
|
(push id forward-queries))
|
2016-02-08 12:34:21 +01:00
|
|
|
;; Make a copy ready to be forwarded in the
|
|
|
|
;; composition buffer.
|
|
|
|
(message-forward-make-body temp-buffer)
|
|
|
|
;; Kill the temporary buffer.
|
|
|
|
(kill-buffer temp-buffer)))
|
|
|
|
;; `message-forward-make-body' always puts the message at
|
|
|
|
;; the top, so do them in reverse order.
|
|
|
|
(reverse messages))
|
|
|
|
;; Add in the appropriate subject.
|
|
|
|
(save-restriction
|
|
|
|
(message-narrow-to-headers)
|
|
|
|
(message-remove-header "Subject")
|
2019-04-12 14:01:10 +02:00
|
|
|
(message-add-header (concat "Subject: " forward-subject))
|
|
|
|
(message-remove-header "References")
|
|
|
|
(message-add-header (concat "References: "
|
|
|
|
(mapconcat 'identity forward-references " "))))
|
2020-08-08 13:49:36 +02:00
|
|
|
;; Create a buffer-local queue for tag changes triggered when
|
|
|
|
;; sending the message.
|
2019-04-12 14:01:12 +02:00
|
|
|
(when notmuch-message-forwarded-tags
|
|
|
|
(setq-local notmuch-message-queued-tag-changes
|
2020-04-25 22:18:07 +02:00
|
|
|
(cl-loop for id in forward-queries
|
|
|
|
collect
|
|
|
|
(cons id notmuch-message-forwarded-tags))))
|
2016-02-08 12:34:21 +01:00
|
|
|
;; `message-forward-make-body' shows the User-agent header. Hide
|
|
|
|
;; it again.
|
|
|
|
(message-hide-headers)
|
|
|
|
(set-buffer-modified-p nil))))
|
|
|
|
|
2012-01-14 15:46:17 +01:00
|
|
|
(defun notmuch-mua-new-reply (query-string &optional prompt-for-sender reply-all)
|
2013-10-06 05:22:44 +02:00
|
|
|
"Compose a reply to the message identified by QUERY-STRING.
|
|
|
|
|
|
|
|
If PROMPT-FOR-SENDER is non-nil, the user will be prompted for
|
|
|
|
the From: address first. If REPLY-ALL is non-nil, the message
|
|
|
|
will be addressed to all recipients of the source message."
|
2020-11-16 22:28:24 +01:00
|
|
|
;; `select-active-regions' is t by default. The reply insertion code
|
|
|
|
;; sets the region to the quoted message to make it easy to delete
|
|
|
|
;; (kill-region or C-w). These two things combine to put the quoted
|
|
|
|
;; message in the primary selection.
|
2020-08-08 13:49:38 +02:00
|
|
|
;;
|
|
|
|
;; This is not what the user wanted and is a privacy risk (accidental
|
|
|
|
;; pasting of the quoted message). We can avoid some of the problems
|
|
|
|
;; by let-binding select-active-regions to nil. This fixes if the
|
|
|
|
;; primary selection was previously in a non-emacs window but not if
|
|
|
|
;; it was in an emacs window. To avoid the problem in the latter case
|
|
|
|
;; we deactivate mark.
|
2020-08-08 13:49:41 +02:00
|
|
|
(let ((sender (and prompt-for-sender
|
|
|
|
(notmuch-mua-prompt-for-sender)))
|
2013-11-17 13:04:09 +01:00
|
|
|
(select-active-regions nil))
|
|
|
|
(notmuch-mua-reply query-string sender reply-all)
|
|
|
|
(deactivate-mark)))
|
2011-05-26 10:41:33 +02:00
|
|
|
|
emacs: make headings outline-minor-mode compatible
`outline-minor-mode' treats comments that begin with three or more
semicolons as headings. That makes it very convenient to navigate
code and to show/hide parts of a file.
Elips libraries typically have four top-level sections, e.g.:
;;; notmuch.el --- run notmuch within emacs...
;;; Commentary:...
;;; Code:...
;;; notmuch.el ends here
In this package many libraries lack a "Commentary:" section, which is
not optimal but okay for most libraries, except major entry points.
Depending on how one chooses to look at it, the "... ends here" line
is not really a heading that begins a section, because it should never
have a "section" body (after all it marks eof).
If the file is rather short, then I left "Code:" as the only section
that contains code. Otherwise I split the file into multiple sibling
sections. The "Code:" section continues to contain `require' and
`declare-function' forms and other such "front matter".
If and only if I have split the code into multiple sections anyway,
then I also added an additional section named just "_" before the
`provide' form and shortly before the "...end here" line. This
section could also be called "Back matter", but I feel it would be
distracting to be that explicit about it. (The IMO unnecessary but
unfortunately still obligatory "... ends here" line is already
distracting enough as far as I am concerned.)
Before this commit some libraries already uses section headings, some
of them consistently. When a library already had some headings, then
this commit often sticks to that style, even at the cost inconsistent
styling across all libraries.
A very limited number of variable and function definitions have to be
moved around because they would otherwise end up in sections they do
not belong into.
Sections, including but not limited to their heading, can and should
be further improved in the future.
2021-01-10 15:00:46 +01:00
|
|
|
;;; Checks
|
|
|
|
|
2016-10-08 22:05:23 +02:00
|
|
|
(defun notmuch-mua-check-no-misplaced-secure-tag ()
|
|
|
|
"Query user if there is a misplaced secure mml tag.
|
|
|
|
|
|
|
|
Emacs message-send will (probably) ignore a secure mml tag unless
|
|
|
|
it is at the start of the body. Returns t if there is no such
|
|
|
|
tag, or the user confirms they mean it."
|
|
|
|
(save-excursion
|
|
|
|
(let ((body-start (progn (message-goto-body) (point))))
|
|
|
|
(goto-char (point-max))
|
|
|
|
(or
|
|
|
|
;; We are always fine if there is no secure tag.
|
2020-11-16 22:28:41 +01:00
|
|
|
(not (search-backward "<#secure" nil t))
|
2016-10-08 22:05:23 +02:00
|
|
|
;; There is a secure tag, so it must be at the start of the
|
|
|
|
;; body, with no secure tag earlier (i.e., in the headers).
|
|
|
|
(and (= (point) body-start)
|
2020-11-16 22:28:41 +01:00
|
|
|
(not (search-backward "<#secure" nil t)))
|
2016-10-08 22:05:23 +02:00
|
|
|
;; The user confirms they means it.
|
|
|
|
(yes-or-no-p "\
|
|
|
|
There is a <#secure> tag not at the start of the body. It is
|
|
|
|
likely that the message will be sent unsigned and unencrypted.
|
|
|
|
Really send? ")))))
|
|
|
|
|
|
|
|
(defun notmuch-mua-check-secure-tag-has-newline ()
|
|
|
|
"Query if the secure mml tag has a newline following it.
|
|
|
|
|
|
|
|
Emacs message-send will (probably) ignore a correctly placed
|
|
|
|
secure mml tag unless it is followed by a newline. Returns t if
|
|
|
|
any secure tag is followed by a newline, or the user confirms
|
|
|
|
they mean it."
|
|
|
|
(save-excursion
|
|
|
|
(message-goto-body)
|
|
|
|
(or
|
|
|
|
;; There is no (correctly placed) secure tag.
|
|
|
|
(not (looking-at "<#secure"))
|
|
|
|
;; The secure tag is followed by a newline.
|
|
|
|
(looking-at "<#secure[^\n>]*>\n")
|
|
|
|
;; The user confirms they means it.
|
|
|
|
(yes-or-no-p "\
|
|
|
|
The <#secure> tag at the start of the body is not followed by a
|
|
|
|
newline. It is likely that the message will be sent unsigned and
|
|
|
|
unencrypted. Really send? "))))
|
|
|
|
|
emacs: make headings outline-minor-mode compatible
`outline-minor-mode' treats comments that begin with three or more
semicolons as headings. That makes it very convenient to navigate
code and to show/hide parts of a file.
Elips libraries typically have four top-level sections, e.g.:
;;; notmuch.el --- run notmuch within emacs...
;;; Commentary:...
;;; Code:...
;;; notmuch.el ends here
In this package many libraries lack a "Commentary:" section, which is
not optimal but okay for most libraries, except major entry points.
Depending on how one chooses to look at it, the "... ends here" line
is not really a heading that begins a section, because it should never
have a "section" body (after all it marks eof).
If the file is rather short, then I left "Code:" as the only section
that contains code. Otherwise I split the file into multiple sibling
sections. The "Code:" section continues to contain `require' and
`declare-function' forms and other such "front matter".
If and only if I have split the code into multiple sections anyway,
then I also added an additional section named just "_" before the
`provide' form and shortly before the "...end here" line. This
section could also be called "Back matter", but I feel it would be
distracting to be that explicit about it. (The IMO unnecessary but
unfortunately still obligatory "... ends here" line is already
distracting enough as far as I am concerned.)
Before this commit some libraries already uses section headings, some
of them consistently. When a library already had some headings, then
this commit often sticks to that style, even at the cost inconsistent
styling across all libraries.
A very limited number of variable and function definitions have to be
moved around because they would otherwise end up in sections they do
not belong into.
Sections, including but not limited to their heading, can and should
be further improved in the future.
2021-01-10 15:00:46 +01:00
|
|
|
;;; Finishing commands
|
|
|
|
|
2016-10-08 22:05:22 +02:00
|
|
|
(defun notmuch-mua-send-common (arg &optional exit)
|
2010-04-22 11:03:32 +02:00
|
|
|
(interactive "P")
|
2018-09-25 17:09:10 +02:00
|
|
|
(run-hooks 'notmuch-mua-send-hook)
|
2016-10-08 22:05:23 +02:00
|
|
|
(when (and (notmuch-mua-check-no-misplaced-secure-tag)
|
|
|
|
(notmuch-mua-check-secure-tag-has-newline))
|
2020-08-08 13:49:36 +02:00
|
|
|
(cl-letf (((symbol-function 'message-do-fcc)
|
|
|
|
#'notmuch-maildir-message-do-fcc))
|
2020-04-25 22:18:07 +02:00
|
|
|
(if exit
|
|
|
|
(message-send-and-exit arg)
|
|
|
|
(message-send arg)))))
|
2016-10-08 22:05:22 +02:00
|
|
|
|
|
|
|
(defun notmuch-mua-send-and-exit (&optional arg)
|
|
|
|
(interactive "P")
|
2020-11-16 22:28:41 +01:00
|
|
|
(notmuch-mua-send-common arg t))
|
2015-08-01 11:44:56 +02:00
|
|
|
|
|
|
|
(defun notmuch-mua-send (&optional arg)
|
|
|
|
(interactive "P")
|
2016-10-08 22:05:22 +02:00
|
|
|
(notmuch-mua-send-common arg))
|
2010-04-22 11:03:32 +02:00
|
|
|
|
|
|
|
(defun notmuch-mua-kill-buffer ()
|
|
|
|
(interactive)
|
|
|
|
(message-kill-buffer))
|
|
|
|
|
emacs: make headings outline-minor-mode compatible
`outline-minor-mode' treats comments that begin with three or more
semicolons as headings. That makes it very convenient to navigate
code and to show/hide parts of a file.
Elips libraries typically have four top-level sections, e.g.:
;;; notmuch.el --- run notmuch within emacs...
;;; Commentary:...
;;; Code:...
;;; notmuch.el ends here
In this package many libraries lack a "Commentary:" section, which is
not optimal but okay for most libraries, except major entry points.
Depending on how one chooses to look at it, the "... ends here" line
is not really a heading that begins a section, because it should never
have a "section" body (after all it marks eof).
If the file is rather short, then I left "Code:" as the only section
that contains code. Otherwise I split the file into multiple sibling
sections. The "Code:" section continues to contain `require' and
`declare-function' forms and other such "front matter".
If and only if I have split the code into multiple sections anyway,
then I also added an additional section named just "_" before the
`provide' form and shortly before the "...end here" line. This
section could also be called "Back matter", but I feel it would be
distracting to be that explicit about it. (The IMO unnecessary but
unfortunately still obligatory "... ends here" line is already
distracting enough as far as I am concerned.)
Before this commit some libraries already uses section headings, some
of them consistently. When a library already had some headings, then
this commit often sticks to that style, even at the cost inconsistent
styling across all libraries.
A very limited number of variable and function definitions have to be
moved around because they would otherwise end up in sections they do
not belong into.
Sections, including but not limited to their heading, can and should
be further improved in the future.
2021-01-10 15:00:46 +01:00
|
|
|
;;; _
|
2010-04-22 11:03:32 +02:00
|
|
|
|
|
|
|
(define-mail-user-agent 'notmuch-user-agent
|
|
|
|
'notmuch-mua-mail 'notmuch-mua-send-and-exit
|
|
|
|
'notmuch-mua-kill-buffer 'notmuch-mua-send-hook)
|
|
|
|
|
2010-04-26 13:50:59 +02:00
|
|
|
;; Add some more headers to the list that `message-mode' hides when
|
|
|
|
;; composing a message.
|
|
|
|
(notmuch-mua-add-more-hidden-headers)
|
|
|
|
|
2010-04-22 11:03:32 +02:00
|
|
|
(provide 'notmuch-mua)
|
2016-04-13 09:58:47 +02:00
|
|
|
|
|
|
|
;;; notmuch-mua.el ends here
|