2021-01-10 15:00:47 +01:00
|
|
|
;;; notmuch-crypto.el --- functions for handling display of cryptographic metadata -*- lexical-binding: t -*-
|
2011-05-26 03:01:19 +02:00
|
|
|
;;
|
|
|
|
|
;; Copyright © Jameson Rollins
|
|
|
|
|
;;
|
|
|
|
|
;; 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/>.
|
2011-05-26 03:01:19 +02:00
|
|
|
;;
|
|
|
|
|
;; Authors: Jameson Rollins <jrollins@finestructure.net>
|
|
|
|
|
|
2016-04-13 09:58:47 +02:00
|
|
|
;;; Code:
|
|
|
|
|
|
2017-03-12 20:26:16 +01:00
|
|
|
(require 'epg)
|
2013-01-07 22:07:20 +01:00
|
|
|
(require 'notmuch-lib)
|
|
|
|
|
|
2020-04-15 20:28:20 +02:00
|
|
|
(declare-function notmuch-show-get-message-id "notmuch-show" (&optional bare))
|
|
|
|
|
|
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
|
|
|
|
|
|
2017-07-12 12:48:18 +02:00
|
|
|
(defcustom notmuch-crypto-process-mime t
|
2020-11-16 22:28:31 +01:00
|
|
|
"Whether to process cryptographic MIME parts.
|
2011-05-26 03:01:19 +02:00
|
|
|
|
|
|
|
|
If this variable is non-nil signatures in multipart/signed
|
|
|
|
|
messages will be verified and multipart/encrypted parts will be
|
|
|
|
|
decrypted. The result of the crypto operation will be displayed
|
|
|
|
|
in a specially colored header button at the top of the processed
|
|
|
|
|
part. Signed parts will have variously colored headers depending
|
|
|
|
|
on the success or failure of the verification process and on the
|
|
|
|
|
validity of user ID of the signer.
|
|
|
|
|
|
|
|
|
|
The effect of setting this variable can be seen temporarily by
|
2011-05-31 19:06:00 +02:00
|
|
|
providing a prefix when viewing a signed or encrypted message, or
|
|
|
|
|
by providing a prefix when reloading the message in notmuch-show
|
|
|
|
|
mode."
|
2012-01-16 11:38:33 +01:00
|
|
|
:type 'boolean
|
2017-07-12 12:48:18 +02:00
|
|
|
:package-version '(notmuch . "0.25")
|
2012-01-16 11:38:33 +01:00
|
|
|
:group 'notmuch-crypto)
|
2011-05-26 03:01:19 +02:00
|
|
|
|
2019-09-12 03:32:57 +02:00
|
|
|
(defcustom notmuch-crypto-get-keys-asynchronously t
|
2020-11-16 22:28:31 +01:00
|
|
|
"Whether to retrieve openpgp keys asynchronously."
|
2019-09-12 03:32:57 +02:00
|
|
|
:type 'boolean
|
|
|
|
|
:group 'notmuch-crypto)
|
|
|
|
|
|
2019-09-12 03:32:59 +02:00
|
|
|
(defcustom notmuch-crypto-gpg-program epg-gpg-program
|
|
|
|
|
"The gpg executable."
|
|
|
|
|
:type 'string
|
|
|
|
|
:group 'notmuch-crypto)
|
|
|
|
|
|
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
|
|
|
;;; Faces
|
|
|
|
|
|
2011-12-13 18:32:10 +01:00
|
|
|
(defface notmuch-crypto-part-header
|
2016-10-29 00:31:42 +02:00
|
|
|
'((((class color)
|
|
|
|
|
(background dark))
|
|
|
|
|
(:foreground "LightBlue1"))
|
|
|
|
|
(((class color)
|
|
|
|
|
(background light))
|
|
|
|
|
(:foreground "blue")))
|
2011-12-13 18:32:10 +01:00
|
|
|
"Face used for crypto parts headers."
|
2012-01-16 11:38:33 +01:00
|
|
|
:group 'notmuch-crypto
|
|
|
|
|
:group 'notmuch-faces)
|
2011-12-13 18:32:10 +01:00
|
|
|
|
2011-03-31 00:31:04 +02:00
|
|
|
(defface notmuch-crypto-signature-good
|
|
|
|
|
'((t (:background "green" :foreground "black")))
|
|
|
|
|
"Face used for good signatures."
|
2012-01-16 11:38:33 +01:00
|
|
|
:group 'notmuch-crypto
|
|
|
|
|
:group 'notmuch-faces)
|
2011-03-31 00:31:04 +02:00
|
|
|
|
|
|
|
|
(defface notmuch-crypto-signature-good-key
|
|
|
|
|
'((t (:background "orange" :foreground "black")))
|
|
|
|
|
"Face used for good signatures."
|
2012-01-16 11:38:33 +01:00
|
|
|
:group 'notmuch-crypto
|
|
|
|
|
:group 'notmuch-faces)
|
2011-03-31 00:31:04 +02:00
|
|
|
|
|
|
|
|
(defface notmuch-crypto-signature-bad
|
|
|
|
|
'((t (:background "red" :foreground "black")))
|
|
|
|
|
"Face used for bad signatures."
|
2012-01-16 11:38:33 +01:00
|
|
|
:group 'notmuch-crypto
|
|
|
|
|
:group 'notmuch-faces)
|
2011-03-31 00:31:04 +02:00
|
|
|
|
|
|
|
|
(defface notmuch-crypto-signature-unknown
|
|
|
|
|
'((t (:background "red" :foreground "black")))
|
|
|
|
|
"Face used for signatures of unknown status."
|
2012-01-16 11:38:33 +01:00
|
|
|
:group 'notmuch-crypto
|
|
|
|
|
:group 'notmuch-faces)
|
2011-03-31 00:31:04 +02:00
|
|
|
|
|
|
|
|
(defface notmuch-crypto-decryption
|
|
|
|
|
'((t (:background "purple" :foreground "black")))
|
|
|
|
|
"Face used for encryption/decryption status messages."
|
2012-01-16 11:38:33 +01:00
|
|
|
:group 'notmuch-crypto
|
|
|
|
|
:group 'notmuch-faces)
|
2011-03-31 00:31:04 +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
|
|
|
;;; Functions
|
|
|
|
|
|
2011-05-26 03:01:19 +02:00
|
|
|
(define-button-type 'notmuch-crypto-status-button-type
|
2021-01-10 15:00:58 +01:00
|
|
|
'action (lambda (button) (message "%s" (button-get button 'help-echo)))
|
2011-05-26 03:01:19 +02:00
|
|
|
'follow-link t
|
2013-01-07 22:07:20 +01:00
|
|
|
'help-echo "Set notmuch-crypto-process-mime to process cryptographic mime parts."
|
|
|
|
|
:supertype 'notmuch-button-type)
|
2011-05-26 03:01:19 +02:00
|
|
|
|
|
|
|
|
(defun notmuch-crypto-insert-sigstatus-button (sigstatus from)
|
2020-11-16 22:28:29 +01:00
|
|
|
"Insert a button describing the signature status SIGSTATUS sent by user FROM."
|
2011-05-26 03:01:19 +02:00
|
|
|
(let* ((status (plist-get sigstatus :status))
|
2019-04-22 19:18:14 +02:00
|
|
|
(show-button t)
|
2011-05-31 19:07:13 +02:00
|
|
|
(face 'notmuch-crypto-signature-unknown)
|
2019-09-12 03:32:58 +02:00
|
|
|
(button-action (lambda (button) (message (button-get button 'help-echo))))
|
|
|
|
|
(keyid (concat "0x" (plist-get sigstatus :keyid)))
|
|
|
|
|
label help-msg)
|
2011-05-26 03:01:19 +02:00
|
|
|
(cond
|
|
|
|
|
((string= status "good")
|
2019-09-12 03:32:58 +02:00
|
|
|
(let ((fingerprint (concat "0x" (plist-get sigstatus :fingerprint)))
|
|
|
|
|
(userid (plist-get sigstatus :userid)))
|
|
|
|
|
;; If userid is present it has full or greater validity.
|
|
|
|
|
(if userid
|
2020-08-08 13:49:40 +02:00
|
|
|
(progn
|
|
|
|
|
(setq label (concat "Good signature by: " userid))
|
|
|
|
|
(setq face 'notmuch-crypto-signature-good))
|
|
|
|
|
(setq label (concat "Good signature by key: " fingerprint))
|
|
|
|
|
(setq face 'notmuch-crypto-signature-good-key))
|
|
|
|
|
(setq button-action 'notmuch-crypto-sigstatus-good-callback)
|
|
|
|
|
(setq help-msg (concat "Click to list key ID 0x" fingerprint "."))))
|
2011-05-26 03:01:19 +02:00
|
|
|
((string= status "error")
|
2020-08-08 13:49:40 +02:00
|
|
|
(setq label (concat "Unknown key ID " keyid " or unsupported algorithm"))
|
|
|
|
|
(setq button-action 'notmuch-crypto-sigstatus-error-callback)
|
|
|
|
|
(setq help-msg (concat "Click to retrieve key ID " keyid
|
2020-08-08 13:49:55 +02:00
|
|
|
" from key server.")))
|
2011-05-26 03:01:19 +02:00
|
|
|
((string= status "bad")
|
2020-08-08 13:49:40 +02:00
|
|
|
(setq label (concat "Bad signature (claimed key ID " keyid ")"))
|
|
|
|
|
(setq face 'notmuch-crypto-signature-bad))
|
2019-04-22 19:18:14 +02:00
|
|
|
(status
|
|
|
|
|
(setq label (concat "Unknown signature status: " status)))
|
2011-05-26 03:01:19 +02:00
|
|
|
(t
|
2019-04-22 19:18:14 +02:00
|
|
|
(setq show-button nil)))
|
|
|
|
|
(when show-button
|
|
|
|
|
(insert-button
|
|
|
|
|
(concat "[ " label " ]")
|
|
|
|
|
:type 'notmuch-crypto-status-button-type
|
|
|
|
|
'help-echo help-msg
|
|
|
|
|
'face face
|
|
|
|
|
'mouse-face face
|
|
|
|
|
'action button-action
|
|
|
|
|
:notmuch-sigstatus sigstatus
|
|
|
|
|
:notmuch-from from)
|
|
|
|
|
(insert "\n"))))
|
2011-05-26 03:01:19 +02:00
|
|
|
|
2011-05-31 19:07:13 +02:00
|
|
|
(defun notmuch-crypto-sigstatus-good-callback (button)
|
2019-09-12 03:33:00 +02:00
|
|
|
(let* ((id (notmuch-show-get-message-id))
|
|
|
|
|
(sigstatus (button-get button :notmuch-sigstatus))
|
2011-05-31 19:07:13 +02:00
|
|
|
(fingerprint (concat "0x" (plist-get sigstatus :fingerprint)))
|
|
|
|
|
(buffer (get-buffer-create "*notmuch-crypto-gpg-out*"))
|
2019-09-12 03:32:58 +02:00
|
|
|
(window (display-buffer buffer)))
|
2011-05-31 19:07:13 +02:00
|
|
|
(with-selected-window window
|
|
|
|
|
(with-current-buffer buffer
|
2012-02-07 18:26:11 +01:00
|
|
|
(goto-char (point-max))
|
2019-09-12 03:33:00 +02:00
|
|
|
(insert (format "-- Key %s in message %s:\n"
|
|
|
|
|
fingerprint id))
|
2020-08-08 13:49:36 +02:00
|
|
|
(call-process notmuch-crypto-gpg-program nil t t
|
|
|
|
|
"--batch" "--no-tty" "--list-keys" fingerprint))
|
2011-05-31 19:07:13 +02:00
|
|
|
(recenter -1))))
|
|
|
|
|
|
2019-09-12 03:32:58 +02:00
|
|
|
(declare-function notmuch-show-refresh-view "notmuch-show" (&optional reset-state))
|
2020-03-18 18:11:53 +01:00
|
|
|
(declare-function notmuch-show-get-message-id "notmuch-show" (&optional bare))
|
2019-09-12 03:32:58 +02:00
|
|
|
|
2021-01-10 15:00:48 +01:00
|
|
|
(defun notmuch-crypto--async-key-sentinel (process _event)
|
2019-09-12 03:32:57 +02:00
|
|
|
"When the user asks for a GPG key to be retrieved
|
|
|
|
|
asynchronously, handle completion of that task.
|
|
|
|
|
|
|
|
|
|
If the retrieval is successful, the thread where the retrieval
|
|
|
|
|
was initiated is still displayed and the cursor has not moved,
|
|
|
|
|
redisplay the thread."
|
|
|
|
|
(let ((status (process-status process))
|
|
|
|
|
(exit-status (process-exit-status process))
|
|
|
|
|
(keyid (process-get process :gpg-key-id)))
|
|
|
|
|
(when (memq status '(exit signal))
|
|
|
|
|
(message "Getting the GPG key %s asynchronously...%s."
|
|
|
|
|
keyid
|
|
|
|
|
(if (= exit-status 0)
|
|
|
|
|
"completed"
|
|
|
|
|
"failed"))
|
|
|
|
|
;; If the original buffer is still alive and point didn't move
|
|
|
|
|
;; (i.e. the user didn't move on or away), refresh the buffer to
|
|
|
|
|
;; show the updated signature status.
|
|
|
|
|
(let ((show-buffer (process-get process :notmuch-show-buffer))
|
|
|
|
|
(show-point (process-get process :notmuch-show-point)))
|
|
|
|
|
(when (and (bufferp show-buffer)
|
|
|
|
|
(buffer-live-p show-buffer)
|
|
|
|
|
(= show-point
|
|
|
|
|
(with-current-buffer show-buffer
|
|
|
|
|
(point))))
|
|
|
|
|
(with-current-buffer show-buffer
|
|
|
|
|
(notmuch-show-refresh-view)))))))
|
|
|
|
|
|
|
|
|
|
(defun notmuch-crypto--set-button-label (button label)
|
|
|
|
|
"Set the text displayed in BUTTON to LABEL."
|
|
|
|
|
(save-excursion
|
|
|
|
|
(let ((inhibit-read-only t))
|
|
|
|
|
;; This knows rather too much about how we typically format
|
|
|
|
|
;; buttons.
|
|
|
|
|
(goto-char (button-start button))
|
|
|
|
|
(forward-char 2)
|
|
|
|
|
(delete-region (point) (- (button-end button) 2))
|
|
|
|
|
(insert label))))
|
|
|
|
|
|
2011-05-31 19:07:13 +02:00
|
|
|
(defun notmuch-crypto-sigstatus-error-callback (button)
|
2019-09-12 03:32:58 +02:00
|
|
|
"When signature validation has failed, try to retrieve the
|
|
|
|
|
corresponding key when the status button is pressed."
|
2011-05-31 19:07:13 +02:00
|
|
|
(let* ((sigstatus (button-get button :notmuch-sigstatus))
|
|
|
|
|
(keyid (concat "0x" (plist-get sigstatus :keyid)))
|
2019-09-12 03:32:57 +02:00
|
|
|
(buffer (get-buffer-create "*notmuch-crypto-gpg-out*")))
|
|
|
|
|
(if notmuch-crypto-get-keys-asynchronously
|
|
|
|
|
(progn
|
|
|
|
|
(notmuch-crypto--set-button-label
|
|
|
|
|
button (format "Retrieving key %s asynchronously..." keyid))
|
2019-09-12 03:33:00 +02:00
|
|
|
(with-current-buffer buffer
|
|
|
|
|
(goto-char (point-max))
|
|
|
|
|
(insert (format "--- Retrieving key %s:\n" keyid)))
|
2020-08-08 13:49:36 +02:00
|
|
|
(let ((p (make-process
|
|
|
|
|
:name "notmuch GPG key retrieval"
|
|
|
|
|
:connection-type 'pipe
|
|
|
|
|
:buffer buffer
|
|
|
|
|
:stderr buffer
|
|
|
|
|
:command (list notmuch-crypto-gpg-program "--recv-keys" keyid)
|
|
|
|
|
:sentinel #'notmuch-crypto--async-key-sentinel)))
|
2019-09-12 03:32:57 +02:00
|
|
|
(process-put p :gpg-key-id keyid)
|
|
|
|
|
(process-put p :notmuch-show-buffer (current-buffer))
|
|
|
|
|
(process-put p :notmuch-show-point (point))
|
2020-01-03 18:04:00 +01:00
|
|
|
(message "Getting the GPG key %s asynchronously..." keyid)))
|
2019-09-12 03:32:58 +02:00
|
|
|
(let ((window (display-buffer buffer)))
|
2019-09-12 03:32:57 +02:00
|
|
|
(with-selected-window window
|
|
|
|
|
(with-current-buffer buffer
|
|
|
|
|
(goto-char (point-max))
|
2019-09-12 03:33:00 +02:00
|
|
|
(insert (format "--- Retrieving key %s:\n" keyid))
|
2019-09-12 03:32:59 +02:00
|
|
|
(call-process notmuch-crypto-gpg-program nil t t "--recv-keys" keyid)
|
2019-09-12 03:32:57 +02:00
|
|
|
(insert "\n")
|
2019-09-12 03:32:59 +02:00
|
|
|
(call-process notmuch-crypto-gpg-program nil t t "--list-keys" keyid))
|
2019-09-12 03:32:57 +02:00
|
|
|
(recenter -1))
|
|
|
|
|
(notmuch-show-refresh-view)))))
|
2011-05-31 19:07:13 +02:00
|
|
|
|
2011-05-26 03:01:19 +02:00
|
|
|
(defun notmuch-crypto-insert-encstatus-button (encstatus)
|
2019-09-12 03:32:58 +02:00
|
|
|
"Insert a button describing the encryption status ENCSTATUS."
|
|
|
|
|
(insert-button
|
|
|
|
|
(concat "[ "
|
|
|
|
|
(let ((status (plist-get encstatus :status)))
|
|
|
|
|
(cond
|
|
|
|
|
((string= status "good")
|
|
|
|
|
"Decryption successful")
|
|
|
|
|
((string= status "bad")
|
|
|
|
|
"Decryption error")
|
|
|
|
|
(t
|
|
|
|
|
(concat "Unknown encryption status"
|
2020-08-08 13:49:41 +02:00
|
|
|
(and status (concat ": " status))))))
|
2019-09-12 03:32:58 +02:00
|
|
|
" ]")
|
|
|
|
|
:type 'notmuch-crypto-status-button-type
|
|
|
|
|
'face 'notmuch-crypto-decryption
|
|
|
|
|
'mouse-face 'notmuch-crypto-decryption)
|
|
|
|
|
(insert "\n"))
|
2011-05-26 03:01:19 +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
|
|
|
;;; _
|
2011-05-26 03:01:19 +02:00
|
|
|
|
|
|
|
|
(provide 'notmuch-crypto)
|
2016-04-13 09:58:47 +02:00
|
|
|
|
|
|
|
|
;;; notmuch-crypto.el ends here
|
