2021-01-10 15:00:47 +01:00
|
|
|
;;; notmuch-tag.el --- tag messages within emacs -*- lexical-binding: t -*-
|
2012-04-14 20:52:50 +02:00
|
|
|
;;
|
2013-03-23 12:29:54 +01:00
|
|
|
;; Copyright © Damien Cassou
|
2012-04-14 20:52:50 +02:00
|
|
|
;; Copyright © Carl Worth
|
|
|
|
;;
|
|
|
|
;; 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/>.
|
2012-04-14 20:52:50 +02:00
|
|
|
;;
|
|
|
|
;; Authors: Carl Worth <cworth@cworth.org>
|
2013-03-23 12:29:54 +01:00
|
|
|
;; Damien Cassou <damien.cassou@gmail.com>
|
2020-08-08 13:49:54 +02:00
|
|
|
|
2013-03-23 12:29:54 +01:00
|
|
|
;;; Code:
|
2012-04-14 20:52:50 +02:00
|
|
|
|
|
|
|
(require 'crm)
|
2020-04-25 22:18:07 +02:00
|
|
|
|
2012-04-14 20:52:50 +02:00
|
|
|
(require 'notmuch-lib)
|
|
|
|
|
2020-08-08 13:49:46 +02:00
|
|
|
(declare-function notmuch-search-tag "notmuch"
|
|
|
|
(tag-changes &optional beg end only-matched))
|
|
|
|
(declare-function notmuch-show-tag "notmuch-show" (tag-changes))
|
|
|
|
(declare-function notmuch-tree-tag "notmuch-tree" (tag-changes))
|
2020-08-08 13:49:52 +02:00
|
|
|
(declare-function notmuch-jump "notmuch-jump" (action-map prompt))
|
2016-09-20 21:57:16 +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
|
|
|
;;; Keys
|
|
|
|
|
2016-09-20 21:57:16 +02:00
|
|
|
(define-widget 'notmuch-tag-key-type 'list
|
|
|
|
"A single key tagging binding."
|
|
|
|
:format "%v"
|
|
|
|
:args '((list :inline t
|
|
|
|
:format "%v"
|
|
|
|
(key-sequence :tag "Key")
|
2020-08-08 13:49:36 +02:00
|
|
|
(radio :tag "Tag operations"
|
|
|
|
(repeat :tag "Tag list"
|
|
|
|
(string :format "%v" :tag "change"))
|
2016-09-20 21:57:16 +02:00
|
|
|
(variable :tag "Tag variable"))
|
|
|
|
(string :tag "Name"))))
|
|
|
|
|
|
|
|
(defcustom notmuch-tagging-keys
|
|
|
|
`((,(kbd "a") notmuch-archive-tags "Archive")
|
|
|
|
(,(kbd "u") notmuch-show-mark-read-tags "Mark read")
|
|
|
|
(,(kbd "f") ("+flagged") "Flag")
|
|
|
|
(,(kbd "s") ("+spam" "-inbox") "Mark as spam")
|
|
|
|
(,(kbd "d") ("+deleted" "-inbox") "Delete"))
|
|
|
|
"A list of keys and corresponding tagging operations.
|
|
|
|
|
|
|
|
For each key (or key sequence) you can specify a sequence of
|
|
|
|
tagging operations to apply, or a variable which contains a list
|
|
|
|
of tagging operations such as `notmuch-archive-tags'. The final
|
|
|
|
element is a name for this tagging operation. If the name is
|
|
|
|
omitted or empty then the list of tag changes, or the variable
|
2016-10-15 13:09:31 +02:00
|
|
|
name is used as the name.
|
|
|
|
|
|
|
|
The key `notmuch-tag-jump-reverse-key' (k by default) should not
|
|
|
|
be used (either as a key, or as the start of a key sequence) as
|
|
|
|
it is already bound: it switches the menu to a menu of the
|
|
|
|
reverse tagging operations. The reverse of a tagging operation is
|
2020-11-16 22:28:30 +01:00
|
|
|
the same list of individual tag-ops but with `+tag' replaced by
|
|
|
|
`-tag' and vice versa.
|
2016-09-20 21:57:16 +02:00
|
|
|
|
|
|
|
If setting this variable outside of customize then it should be a
|
|
|
|
list of triples (lists of three elements). Each triple should be
|
|
|
|
of the form (key-binding tagging-operations name). KEY-BINDING
|
|
|
|
can be a single character or a key sequence; TAGGING-OPERATIONS
|
|
|
|
should either be a list of individual tag operations each of the
|
2020-11-16 22:28:30 +01:00
|
|
|
form `+tag' or `-tag', or the variable name of a variable that is
|
2016-09-20 21:57:16 +02:00
|
|
|
a list of tagging operations; NAME should be a name for the
|
|
|
|
tagging operation, if omitted or empty than then name is taken
|
|
|
|
from TAGGING-OPERATIONS."
|
|
|
|
:tag "List of tagging bindings"
|
|
|
|
:type '(repeat notmuch-tag-key-type)
|
|
|
|
:group 'notmuch-tag)
|
|
|
|
|
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 and Formats
|
|
|
|
|
2014-03-22 12:51:07 +01:00
|
|
|
(define-widget 'notmuch-tag-format-type 'lazy
|
2020-05-24 21:17:56 +02:00
|
|
|
"Customize widget for notmuch-tag-format and friends."
|
2014-03-22 12:51:07 +01:00
|
|
|
:type '(alist :key-type (regexp :tag "Tag")
|
|
|
|
:extra-offset -3
|
|
|
|
:value-type
|
|
|
|
(radio :format "%v"
|
|
|
|
(const :tag "Hidden" nil)
|
|
|
|
(set :tag "Modified"
|
|
|
|
(string :tag "Display as")
|
|
|
|
(list :tag "Face" :extra-offset -4
|
|
|
|
(const :format "" :inline t
|
2014-03-22 12:51:08 +01:00
|
|
|
(notmuch-apply-face tag))
|
2014-03-22 12:51:07 +01:00
|
|
|
(list :format "%v"
|
|
|
|
(const :format "" quote)
|
|
|
|
custom-face-edit))
|
|
|
|
(list :format "%v" :extra-offset -4
|
|
|
|
(const :format "" :inline t
|
|
|
|
(notmuch-tag-format-image-data tag))
|
|
|
|
(choice :tag "Image"
|
|
|
|
(const :tag "Star"
|
|
|
|
(notmuch-tag-star-icon))
|
|
|
|
(const :tag "Empty star"
|
|
|
|
(notmuch-tag-star-empty-icon))
|
|
|
|
(const :tag "Tag"
|
|
|
|
(notmuch-tag-tag-icon))
|
|
|
|
(string :tag "Custom")))
|
|
|
|
(sexp :tag "Custom")))))
|
|
|
|
|
2016-08-15 00:17:42 +02:00
|
|
|
(defface notmuch-tag-unread
|
|
|
|
'((t :foreground "red"))
|
|
|
|
"Default face used for the unread tag.
|
|
|
|
|
2020-11-16 22:28:30 +01:00
|
|
|
Used in the default value of `notmuch-tag-formats'."
|
2016-08-15 00:17:42 +02:00
|
|
|
:group 'notmuch-faces)
|
|
|
|
|
|
|
|
(defface notmuch-tag-flagged
|
2016-10-29 00:31:42 +02:00
|
|
|
'((((class color)
|
|
|
|
(background dark))
|
|
|
|
(:foreground "LightBlue1"))
|
|
|
|
(((class color)
|
|
|
|
(background light))
|
|
|
|
(:foreground "blue")))
|
2016-08-15 00:17:42 +02:00
|
|
|
"Face used for the flagged tag.
|
|
|
|
|
2020-11-16 22:28:30 +01:00
|
|
|
Used in the default value of `notmuch-tag-formats'."
|
2016-08-15 00:17:42 +02:00
|
|
|
:group 'notmuch-faces)
|
|
|
|
|
2013-03-23 12:29:54 +01:00
|
|
|
(defcustom notmuch-tag-formats
|
2016-08-15 00:17:42 +02:00
|
|
|
'(("unread" (propertize tag 'face 'notmuch-tag-unread))
|
|
|
|
("flagged" (propertize tag 'face 'notmuch-tag-flagged)
|
2013-09-04 19:06:55 +02:00
|
|
|
(notmuch-tag-format-image-data tag (notmuch-tag-star-icon))))
|
2013-03-23 12:29:54 +01:00
|
|
|
"Custom formats for individual tags.
|
|
|
|
|
2021-01-10 15:01:01 +01:00
|
|
|
This is an association list of the form ((MATCH EXPR...)...),
|
|
|
|
mapping tag name regexps to lists of formatting expressions.
|
|
|
|
|
|
|
|
The first entry whose MATCH regexp-matches a tag is used to
|
|
|
|
format that tag. The regexp is implicitly anchored, so to match
|
|
|
|
a literal tag name, just use that tag name (if it contains
|
|
|
|
special regexp characters like \".\" or \"*\", these have to be
|
|
|
|
escaped).
|
|
|
|
|
|
|
|
The cdr of the matching entry gives a list of Elisp expressions
|
|
|
|
that modify the tag. If the list is empty, the tag is simply
|
|
|
|
hidden. Otherwise, each expression EXPR is evaluated in order:
|
|
|
|
for the first expression, the variable `tag' is bound to the tag
|
|
|
|
name; for each later expression, the variable `tag' is bound to
|
|
|
|
the result of the previous expression. In this way, each
|
Make keys of notmuch-tag-formats regexps and use caching
This modifies `notmuch-tag-format-tag' to treat the keys of
`notmuch-tag-formats' as (anchored) regexps, rather than literal
strings. This is clearly more flexible, as it allows for prefix
matching, defining a fallback format, etc. This may cause compatibility
problems if people have customized `notmuch-tag-formats' to match tags
that contain regexp specials, but this seems unlikely.
Regular expression matching has quite a performance hit over string
lookup, so this also introduces a simple cache from exact tags to
formatted strings. The number of unique tags is likely to be quite
small, so this cache should have a high hit rate. In addition to
eliminating the regexp lookup in the common case, this cache stores
fully formatted tags, eliminating the repeated evaluation of potentially
expensive, user-specified formatting code. This makes regexp lookup at
least as fast as assoc for unformatted tags (e.g., inbox) and *faster*
than the current code for formatted tags (e.g., unread):
inbox (usec) unread (usec)
assoc: 0.4 2.8
regexp: 3.2 7.2
regexp+caching: 0.4 0.4
(Though even at 7.2 usec, tag formatting is not our top bottleneck.)
This cache must be explicitly cleared to keep it coherent, so this adds
the appropriate clearing calls.
2014-03-22 12:51:06 +01:00
|
|
|
expression can build on the formatting performed by the previous
|
2021-01-10 15:01:01 +01:00
|
|
|
expression. The result of the last expression is displayed in
|
Make keys of notmuch-tag-formats regexps and use caching
This modifies `notmuch-tag-format-tag' to treat the keys of
`notmuch-tag-formats' as (anchored) regexps, rather than literal
strings. This is clearly more flexible, as it allows for prefix
matching, defining a fallback format, etc. This may cause compatibility
problems if people have customized `notmuch-tag-formats' to match tags
that contain regexp specials, but this seems unlikely.
Regular expression matching has quite a performance hit over string
lookup, so this also introduces a simple cache from exact tags to
formatted strings. The number of unique tags is likely to be quite
small, so this cache should have a high hit rate. In addition to
eliminating the regexp lookup in the common case, this cache stores
fully formatted tags, eliminating the repeated evaluation of potentially
expensive, user-specified formatting code. This makes regexp lookup at
least as fast as assoc for unformatted tags (e.g., inbox) and *faster*
than the current code for formatted tags (e.g., unread):
inbox (usec) unread (usec)
assoc: 0.4 2.8
regexp: 3.2 7.2
regexp+caching: 0.4 0.4
(Though even at 7.2 usec, tag formatting is not our top bottleneck.)
This cache must be explicitly cleared to keep it coherent, so this adds
the appropriate clearing calls.
2014-03-22 12:51:06 +01:00
|
|
|
place of the tag.
|
2013-03-23 12:29:54 +01:00
|
|
|
|
|
|
|
For example, to replace a tag with another string, simply use
|
|
|
|
that string as a formatting expression. To change the foreground
|
|
|
|
of a tag to red, use the expression
|
|
|
|
(propertize tag 'face '(:foreground \"red\"))
|
|
|
|
|
|
|
|
See also `notmuch-tag-format-image', which can help replace tags
|
|
|
|
with images."
|
|
|
|
:group 'notmuch-search
|
|
|
|
:group 'notmuch-show
|
2014-03-22 12:51:08 +01:00
|
|
|
:group 'notmuch-faces
|
|
|
|
:type 'notmuch-tag-format-type)
|
|
|
|
|
2016-08-15 00:17:42 +02:00
|
|
|
(defface notmuch-tag-deleted
|
2016-09-18 12:57:32 +02:00
|
|
|
'((((class color) (supports :strike-through "red")) :strike-through "red")
|
2016-08-15 00:17:42 +02:00
|
|
|
(t :inverse-video t))
|
|
|
|
"Face used to display deleted tags.
|
|
|
|
|
2020-11-16 22:28:30 +01:00
|
|
|
Used in the default value of `notmuch-tag-deleted-formats'."
|
2016-08-15 00:17:42 +02:00
|
|
|
:group 'notmuch-faces)
|
|
|
|
|
2014-03-22 12:51:08 +01:00
|
|
|
(defcustom notmuch-tag-deleted-formats
|
2016-08-15 00:17:42 +02:00
|
|
|
'(("unread" (notmuch-apply-face bare-tag `notmuch-tag-deleted))
|
|
|
|
(".*" (notmuch-apply-face tag `notmuch-tag-deleted)))
|
2014-03-22 12:51:08 +01:00
|
|
|
"Custom formats for tags when deleted.
|
|
|
|
|
2020-11-16 22:28:30 +01:00
|
|
|
For deleted tags the formats in `notmuch-tag-formats' are applied
|
2014-03-22 12:51:08 +01:00
|
|
|
first and then these formats are applied on top; that is `tag'
|
|
|
|
passed to the function is the tag with all these previous
|
|
|
|
formattings applied. The formatted can access the original
|
|
|
|
unformatted tag as `bare-tag'.
|
|
|
|
|
|
|
|
By default this shows deleted tags with strike-through in red,
|
|
|
|
unless strike-through is not available (e.g., emacs is running in
|
|
|
|
a terminal) in which case it uses inverse video. To hide deleted
|
|
|
|
tags completely set this to
|
|
|
|
'((\".*\" nil))
|
|
|
|
|
|
|
|
See `notmuch-tag-formats' for full documentation."
|
|
|
|
:group 'notmuch-show
|
|
|
|
:group 'notmuch-faces
|
|
|
|
:type 'notmuch-tag-format-type)
|
|
|
|
|
2016-08-15 00:17:42 +02:00
|
|
|
(defface notmuch-tag-added
|
|
|
|
'((t :underline "green"))
|
|
|
|
"Default face used for added tags.
|
|
|
|
|
2020-11-16 22:28:30 +01:00
|
|
|
Used in the default value for `notmuch-tag-added-formats'."
|
2016-08-15 00:17:42 +02:00
|
|
|
:group 'notmuch-faces)
|
|
|
|
|
2014-03-22 12:51:08 +01:00
|
|
|
(defcustom notmuch-tag-added-formats
|
2016-08-15 00:17:42 +02:00
|
|
|
'((".*" (notmuch-apply-face tag 'notmuch-tag-added)))
|
2014-03-22 12:51:08 +01:00
|
|
|
"Custom formats for tags when added.
|
|
|
|
|
2020-11-16 22:28:30 +01:00
|
|
|
For added tags the formats in `notmuch-tag-formats' are applied
|
2014-03-22 12:51:08 +01:00
|
|
|
first and then these formats are applied on top.
|
|
|
|
|
|
|
|
To disable special formatting of added tags, set this variable to
|
|
|
|
nil.
|
|
|
|
|
|
|
|
See `notmuch-tag-formats' for full documentation."
|
|
|
|
:group 'notmuch-show
|
|
|
|
:group 'notmuch-faces
|
2014-03-22 12:51:07 +01:00
|
|
|
:type 'notmuch-tag-format-type)
|
2013-03-23 12:29:54 +01: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
|
|
|
;;; Icons
|
|
|
|
|
2013-03-23 12:29:54 +01:00
|
|
|
(defun notmuch-tag-format-image-data (tag data)
|
|
|
|
"Replace TAG with image DATA, if available.
|
|
|
|
|
|
|
|
This function returns a propertized string that will display image
|
|
|
|
DATA in place of TAG.This is designed for use in
|
|
|
|
`notmuch-tag-formats'.
|
|
|
|
|
|
|
|
DATA is the content of an SVG picture (e.g., as returned by
|
|
|
|
`notmuch-tag-star-icon')."
|
|
|
|
(propertize tag 'display
|
|
|
|
`(image :type svg
|
|
|
|
:data ,data
|
|
|
|
:ascent center
|
|
|
|
:mask heuristic)))
|
|
|
|
|
|
|
|
(defun notmuch-tag-star-icon ()
|
|
|
|
"Return SVG data representing a star icon.
|
|
|
|
This can be used with `notmuch-tag-format-image-data'."
|
2020-08-08 13:49:38 +02:00
|
|
|
"<?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"no\"?>
|
2022-01-14 14:15:00 +01:00
|
|
|
<svg version=\"1.1\" width=\"16\" height=\"16\" xmlns=\"http://www.w3.org/2000/svg\">
|
2013-03-23 12:29:54 +01:00
|
|
|
<g transform=\"translate(-242.81601,-315.59635)\">
|
|
|
|
<path
|
|
|
|
d=\"m 290.25762,334.31206 -17.64143,-11.77975 -19.70508,7.85447 5.75171,-20.41814 -13.55925,-16.31348 21.19618,-0.83936 11.325,-17.93675 7.34825,19.89939 20.55849,5.22795 -16.65471,13.13786 z\"
|
|
|
|
transform=\"matrix(0.2484147,-0.02623394,0.02623394,0.2484147,174.63605,255.37691)\"
|
|
|
|
style=\"fill:#ffff00;fill-rule:evenodd;stroke:#000000;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1\" />
|
|
|
|
</g>
|
|
|
|
</svg>")
|
|
|
|
|
|
|
|
(defun notmuch-tag-star-empty-icon ()
|
|
|
|
"Return SVG data representing an empty star icon.
|
|
|
|
This can be used with `notmuch-tag-format-image-data'."
|
|
|
|
"<?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"no\"?>
|
2022-01-14 14:15:00 +01:00
|
|
|
<svg version=\"1.1\" width=\"16\" height=\"16\" xmlns=\"http://www.w3.org/2000/svg\">
|
2013-03-23 12:29:54 +01:00
|
|
|
<g transform=\"translate(-242.81601,-315.59635)\">
|
|
|
|
<path
|
|
|
|
d=\"m 290.25762,334.31206 -17.64143,-11.77975 -19.70508,7.85447 5.75171,-20.41814 -13.55925,-16.31348 21.19618,-0.83936 11.325,-17.93675 7.34825,19.89939 20.55849,5.22795 -16.65471,13.13786 z\"
|
|
|
|
transform=\"matrix(0.2484147,-0.02623394,0.02623394,0.2484147,174.63605,255.37691)\"
|
|
|
|
style=\"fill:#d6d6d1;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1\" />
|
|
|
|
</g>
|
|
|
|
</svg>")
|
|
|
|
|
|
|
|
(defun notmuch-tag-tag-icon ()
|
|
|
|
"Return SVG data representing a tag icon.
|
|
|
|
This can be used with `notmuch-tag-format-image-data'."
|
|
|
|
"<?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"no\"?>
|
2022-01-14 14:15:00 +01:00
|
|
|
<svg version=\"1.1\" width=\"16\" height=\"16\" xmlns=\"http://www.w3.org/2000/svg\">
|
2013-03-23 12:29:54 +01:00
|
|
|
<g transform=\"translate(0,-1036.3622)\">
|
|
|
|
<path
|
|
|
|
d=\"m 0.44642857,1040.9336 12.50000043,0 2.700893,3.6161 -2.700893,3.616 -12.50000043,0 z\"
|
|
|
|
style=\"fill:#ffff00;fill-opacity:1;fill-rule:evenodd;stroke:#000000;stroke-width:0.25;stroke-linecap:butt;stroke-linejoin:miter;stroke-miterlimit:4;stroke-opacity:1\" />
|
|
|
|
</g>
|
|
|
|
</svg>")
|
|
|
|
|
2022-02-12 21:27:38 +01:00
|
|
|
;;; track history of tag operations
|
|
|
|
(defvar-local notmuch-tag-history nil
|
|
|
|
"Buffer local history of `notmuch-tag' function.")
|
2022-02-12 21:27:39 +01:00
|
|
|
(put 'notmuch-tag-history 'permanent-local t)
|
2022-02-12 21:27:38 +01: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
|
|
|
;;; Format Handling
|
|
|
|
|
Make keys of notmuch-tag-formats regexps and use caching
This modifies `notmuch-tag-format-tag' to treat the keys of
`notmuch-tag-formats' as (anchored) regexps, rather than literal
strings. This is clearly more flexible, as it allows for prefix
matching, defining a fallback format, etc. This may cause compatibility
problems if people have customized `notmuch-tag-formats' to match tags
that contain regexp specials, but this seems unlikely.
Regular expression matching has quite a performance hit over string
lookup, so this also introduces a simple cache from exact tags to
formatted strings. The number of unique tags is likely to be quite
small, so this cache should have a high hit rate. In addition to
eliminating the regexp lookup in the common case, this cache stores
fully formatted tags, eliminating the repeated evaluation of potentially
expensive, user-specified formatting code. This makes regexp lookup at
least as fast as assoc for unformatted tags (e.g., inbox) and *faster*
than the current code for formatted tags (e.g., unread):
inbox (usec) unread (usec)
assoc: 0.4 2.8
regexp: 3.2 7.2
regexp+caching: 0.4 0.4
(Though even at 7.2 usec, tag formatting is not our top bottleneck.)
This cache must be explicitly cleared to keep it coherent, so this adds
the appropriate clearing calls.
2014-03-22 12:51:06 +01:00
|
|
|
(defvar notmuch-tag--format-cache (make-hash-table :test 'equal)
|
|
|
|
"Cache of tag format lookup. Internal to `notmuch-tag-format-tag'.")
|
|
|
|
|
|
|
|
(defun notmuch-tag-clear-cache ()
|
|
|
|
"Clear the internal cache of tag formats."
|
|
|
|
(clrhash notmuch-tag--format-cache))
|
|
|
|
|
2021-01-10 15:00:49 +01:00
|
|
|
(defun notmuch-tag--get-formats (tag alist)
|
emacs: show: mark tags changed since buffer loaded
This allows (and requires) the original-tags to be passed along with
the current-tags to be passed to notmuch-tag-format-tags. This allows
the tag formatting to show added and deleted tags.By default a removed
tag is displayed with strike-through in red (if strike-through is not
available, eg on a terminal, inverse video is used instead) and an
added tag is displayed underlined in green.
If the caller does not wish to use the new feature it can pass
current-tags for both arguments and, at this point, we do exactly that
in the three callers of this function.
Note, we cannot tidily allow original-tags to be optional because we would
need to distinguish nil meaning "we are not specifying original-tags"
from nil meaning there were no original-tags (an empty list).
We use this in subsequent patches to make it clear when a message was
unread when you first loaded a show buffer (previously the unread tag
could be removed before a user realised that it had been unread).
The code adds into the existing tag formatting code. The user can
specify exactly how a tag should be displayed normally, when deleted,
or when added.
Since the formatting code matches regexps a user can match all deleted
tags with a ".*" in notmuch-tag-deleted-formats. For example setting
notmuch-tag-deleted-formats to '((".*" nil)) tells notmuch not to show
deleted tags at all.
All the variables are customizable; however, more complicated cases
like changing the face depending on the type of display will require
custom lisp.
Currently this overrides notmuch-tag-deleted-formats for the tests
setting it to '((".*" nil)) so that they get removed from the display
and, thus, all tests still pass.
2014-03-22 12:51:09 +01:00
|
|
|
"Find the first item whose car regexp-matches TAG."
|
|
|
|
(save-match-data
|
|
|
|
;; Don't use assoc-default since there's no way to distinguish a
|
|
|
|
;; missing key from a present key with a null cdr.
|
2021-01-10 15:00:49 +01:00
|
|
|
(cl-assoc tag alist
|
2020-04-25 22:18:07 +02:00
|
|
|
:test (lambda (tag key)
|
|
|
|
(and (eq (string-match key tag) 0)
|
|
|
|
(= (match-end 0) (length tag)))))))
|
emacs: show: mark tags changed since buffer loaded
This allows (and requires) the original-tags to be passed along with
the current-tags to be passed to notmuch-tag-format-tags. This allows
the tag formatting to show added and deleted tags.By default a removed
tag is displayed with strike-through in red (if strike-through is not
available, eg on a terminal, inverse video is used instead) and an
added tag is displayed underlined in green.
If the caller does not wish to use the new feature it can pass
current-tags for both arguments and, at this point, we do exactly that
in the three callers of this function.
Note, we cannot tidily allow original-tags to be optional because we would
need to distinguish nil meaning "we are not specifying original-tags"
from nil meaning there were no original-tags (an empty list).
We use this in subsequent patches to make it clear when a message was
unread when you first loaded a show buffer (previously the unread tag
could be removed before a user realised that it had been unread).
The code adds into the existing tag formatting code. The user can
specify exactly how a tag should be displayed normally, when deleted,
or when added.
Since the formatting code matches regexps a user can match all deleted
tags with a ".*" in notmuch-tag-deleted-formats. For example setting
notmuch-tag-deleted-formats to '((".*" nil)) tells notmuch not to show
deleted tags at all.
All the variables are customizable; however, more complicated cases
like changing the face depending on the type of display will require
custom lisp.
Currently this overrides notmuch-tag-deleted-formats for the tests
setting it to '((".*" nil)) so that they get removed from the display
and, thus, all tests still pass.
2014-03-22 12:51:09 +01:00
|
|
|
|
2021-01-10 15:00:47 +01:00
|
|
|
(defun notmuch-tag--do-format (bare-tag tag formats)
|
emacs: show: mark tags changed since buffer loaded
This allows (and requires) the original-tags to be passed along with
the current-tags to be passed to notmuch-tag-format-tags. This allows
the tag formatting to show added and deleted tags.By default a removed
tag is displayed with strike-through in red (if strike-through is not
available, eg on a terminal, inverse video is used instead) and an
added tag is displayed underlined in green.
If the caller does not wish to use the new feature it can pass
current-tags for both arguments and, at this point, we do exactly that
in the three callers of this function.
Note, we cannot tidily allow original-tags to be optional because we would
need to distinguish nil meaning "we are not specifying original-tags"
from nil meaning there were no original-tags (an empty list).
We use this in subsequent patches to make it clear when a message was
unread when you first loaded a show buffer (previously the unread tag
could be removed before a user realised that it had been unread).
The code adds into the existing tag formatting code. The user can
specify exactly how a tag should be displayed normally, when deleted,
or when added.
Since the formatting code matches regexps a user can match all deleted
tags with a ".*" in notmuch-tag-deleted-formats. For example setting
notmuch-tag-deleted-formats to '((".*" nil)) tells notmuch not to show
deleted tags at all.
All the variables are customizable; however, more complicated cases
like changing the face depending on the type of display will require
custom lisp.
Currently this overrides notmuch-tag-deleted-formats for the tests
setting it to '((".*" nil)) so that they get removed from the display
and, thus, all tests still pass.
2014-03-22 12:51:09 +01:00
|
|
|
"Apply a tag-formats entry to TAG."
|
|
|
|
(cond ((null formats) ;; - Tag not in `formats',
|
2021-01-10 15:00:47 +01:00
|
|
|
tag) ;; the format is the tag itself.
|
emacs: show: mark tags changed since buffer loaded
This allows (and requires) the original-tags to be passed along with
the current-tags to be passed to notmuch-tag-format-tags. This allows
the tag formatting to show added and deleted tags.By default a removed
tag is displayed with strike-through in red (if strike-through is not
available, eg on a terminal, inverse video is used instead) and an
added tag is displayed underlined in green.
If the caller does not wish to use the new feature it can pass
current-tags for both arguments and, at this point, we do exactly that
in the three callers of this function.
Note, we cannot tidily allow original-tags to be optional because we would
need to distinguish nil meaning "we are not specifying original-tags"
from nil meaning there were no original-tags (an empty list).
We use this in subsequent patches to make it clear when a message was
unread when you first loaded a show buffer (previously the unread tag
could be removed before a user realised that it had been unread).
The code adds into the existing tag formatting code. The user can
specify exactly how a tag should be displayed normally, when deleted,
or when added.
Since the formatting code matches regexps a user can match all deleted
tags with a ".*" in notmuch-tag-deleted-formats. For example setting
notmuch-tag-deleted-formats to '((".*" nil)) tells notmuch not to show
deleted tags at all.
All the variables are customizable; however, more complicated cases
like changing the face depending on the type of display will require
custom lisp.
Currently this overrides notmuch-tag-deleted-formats for the tests
setting it to '((".*" nil)) so that they get removed from the display
and, thus, all tests still pass.
2014-03-22 12:51:09 +01:00
|
|
|
((null (cdr formats)) ;; - Tag was deliberately hidden,
|
|
|
|
nil) ;; no format must be returned
|
|
|
|
(t
|
|
|
|
;; Tag was found and has formats, we must apply all the
|
|
|
|
;; formats. TAG may be null so treat that as a special case.
|
2021-01-10 15:00:47 +01:00
|
|
|
(let ((return-tag (copy-sequence (or tag ""))))
|
emacs: show: mark tags changed since buffer loaded
This allows (and requires) the original-tags to be passed along with
the current-tags to be passed to notmuch-tag-format-tags. This allows
the tag formatting to show added and deleted tags.By default a removed
tag is displayed with strike-through in red (if strike-through is not
available, eg on a terminal, inverse video is used instead) and an
added tag is displayed underlined in green.
If the caller does not wish to use the new feature it can pass
current-tags for both arguments and, at this point, we do exactly that
in the three callers of this function.
Note, we cannot tidily allow original-tags to be optional because we would
need to distinguish nil meaning "we are not specifying original-tags"
from nil meaning there were no original-tags (an empty list).
We use this in subsequent patches to make it clear when a message was
unread when you first loaded a show buffer (previously the unread tag
could be removed before a user realised that it had been unread).
The code adds into the existing tag formatting code. The user can
specify exactly how a tag should be displayed normally, when deleted,
or when added.
Since the formatting code matches regexps a user can match all deleted
tags with a ".*" in notmuch-tag-deleted-formats. For example setting
notmuch-tag-deleted-formats to '((".*" nil)) tells notmuch not to show
deleted tags at all.
All the variables are customizable; however, more complicated cases
like changing the face depending on the type of display will require
custom lisp.
Currently this overrides notmuch-tag-deleted-formats for the tests
setting it to '((".*" nil)) so that they get removed from the display
and, thus, all tests still pass.
2014-03-22 12:51:09 +01:00
|
|
|
(dolist (format (cdr formats))
|
2021-01-10 15:00:47 +01:00
|
|
|
(setq return-tag
|
|
|
|
(eval format
|
|
|
|
`((bare-tag . ,bare-tag)
|
|
|
|
(tag . ,return-tag)))))
|
|
|
|
(if (and (null tag) (equal return-tag ""))
|
emacs: show: mark tags changed since buffer loaded
This allows (and requires) the original-tags to be passed along with
the current-tags to be passed to notmuch-tag-format-tags. This allows
the tag formatting to show added and deleted tags.By default a removed
tag is displayed with strike-through in red (if strike-through is not
available, eg on a terminal, inverse video is used instead) and an
added tag is displayed underlined in green.
If the caller does not wish to use the new feature it can pass
current-tags for both arguments and, at this point, we do exactly that
in the three callers of this function.
Note, we cannot tidily allow original-tags to be optional because we would
need to distinguish nil meaning "we are not specifying original-tags"
from nil meaning there were no original-tags (an empty list).
We use this in subsequent patches to make it clear when a message was
unread when you first loaded a show buffer (previously the unread tag
could be removed before a user realised that it had been unread).
The code adds into the existing tag formatting code. The user can
specify exactly how a tag should be displayed normally, when deleted,
or when added.
Since the formatting code matches regexps a user can match all deleted
tags with a ".*" in notmuch-tag-deleted-formats. For example setting
notmuch-tag-deleted-formats to '((".*" nil)) tells notmuch not to show
deleted tags at all.
All the variables are customizable; however, more complicated cases
like changing the face depending on the type of display will require
custom lisp.
Currently this overrides notmuch-tag-deleted-formats for the tests
setting it to '((".*" nil)) so that they get removed from the display
and, thus, all tests still pass.
2014-03-22 12:51:09 +01:00
|
|
|
nil
|
2021-01-10 15:00:47 +01:00
|
|
|
return-tag)))))
|
emacs: show: mark tags changed since buffer loaded
This allows (and requires) the original-tags to be passed along with
the current-tags to be passed to notmuch-tag-format-tags. This allows
the tag formatting to show added and deleted tags.By default a removed
tag is displayed with strike-through in red (if strike-through is not
available, eg on a terminal, inverse video is used instead) and an
added tag is displayed underlined in green.
If the caller does not wish to use the new feature it can pass
current-tags for both arguments and, at this point, we do exactly that
in the three callers of this function.
Note, we cannot tidily allow original-tags to be optional because we would
need to distinguish nil meaning "we are not specifying original-tags"
from nil meaning there were no original-tags (an empty list).
We use this in subsequent patches to make it clear when a message was
unread when you first loaded a show buffer (previously the unread tag
could be removed before a user realised that it had been unread).
The code adds into the existing tag formatting code. The user can
specify exactly how a tag should be displayed normally, when deleted,
or when added.
Since the formatting code matches regexps a user can match all deleted
tags with a ".*" in notmuch-tag-deleted-formats. For example setting
notmuch-tag-deleted-formats to '((".*" nil)) tells notmuch not to show
deleted tags at all.
All the variables are customizable; however, more complicated cases
like changing the face depending on the type of display will require
custom lisp.
Currently this overrides notmuch-tag-deleted-formats for the tests
setting it to '((".*" nil)) so that they get removed from the display
and, thus, all tests still pass.
2014-03-22 12:51:09 +01:00
|
|
|
|
|
|
|
(defun notmuch-tag-format-tag (tags orig-tags tag)
|
|
|
|
"Format TAG according to `notmuch-tag-formats'.
|
|
|
|
|
|
|
|
TAGS and ORIG-TAGS are lists of the current tags and the original
|
|
|
|
tags; tags which have been deleted (i.e., are in ORIG-TAGS but
|
|
|
|
are not in TAGS) are shown using formats from
|
|
|
|
`notmuch-tag-deleted-formats'; tags which have been added (i.e.,
|
|
|
|
are in TAGS but are not in ORIG-TAGS) are shown using formats
|
|
|
|
from `notmuch-tag-added-formats' and tags which have not been
|
|
|
|
changed (the normal case) are shown using formats from
|
2020-05-24 21:17:56 +02:00
|
|
|
`notmuch-tag-formats'."
|
emacs: show: mark tags changed since buffer loaded
This allows (and requires) the original-tags to be passed along with
the current-tags to be passed to notmuch-tag-format-tags. This allows
the tag formatting to show added and deleted tags.By default a removed
tag is displayed with strike-through in red (if strike-through is not
available, eg on a terminal, inverse video is used instead) and an
added tag is displayed underlined in green.
If the caller does not wish to use the new feature it can pass
current-tags for both arguments and, at this point, we do exactly that
in the three callers of this function.
Note, we cannot tidily allow original-tags to be optional because we would
need to distinguish nil meaning "we are not specifying original-tags"
from nil meaning there were no original-tags (an empty list).
We use this in subsequent patches to make it clear when a message was
unread when you first loaded a show buffer (previously the unread tag
could be removed before a user realised that it had been unread).
The code adds into the existing tag formatting code. The user can
specify exactly how a tag should be displayed normally, when deleted,
or when added.
Since the formatting code matches regexps a user can match all deleted
tags with a ".*" in notmuch-tag-deleted-formats. For example setting
notmuch-tag-deleted-formats to '((".*" nil)) tells notmuch not to show
deleted tags at all.
All the variables are customizable; however, more complicated cases
like changing the face depending on the type of display will require
custom lisp.
Currently this overrides notmuch-tag-deleted-formats for the tests
setting it to '((".*" nil)) so that they get removed from the display
and, thus, all tests still pass.
2014-03-22 12:51:09 +01:00
|
|
|
(let* ((tag-state (cond ((not (member tag tags)) 'deleted)
|
|
|
|
((not (member tag orig-tags)) 'added)))
|
2020-08-08 13:49:36 +02:00
|
|
|
(formatted-tag (gethash (cons tag tag-state)
|
|
|
|
notmuch-tag--format-cache
|
|
|
|
'missing)))
|
emacs: show: mark tags changed since buffer loaded
This allows (and requires) the original-tags to be passed along with
the current-tags to be passed to notmuch-tag-format-tags. This allows
the tag formatting to show added and deleted tags.By default a removed
tag is displayed with strike-through in red (if strike-through is not
available, eg on a terminal, inverse video is used instead) and an
added tag is displayed underlined in green.
If the caller does not wish to use the new feature it can pass
current-tags for both arguments and, at this point, we do exactly that
in the three callers of this function.
Note, we cannot tidily allow original-tags to be optional because we would
need to distinguish nil meaning "we are not specifying original-tags"
from nil meaning there were no original-tags (an empty list).
We use this in subsequent patches to make it clear when a message was
unread when you first loaded a show buffer (previously the unread tag
could be removed before a user realised that it had been unread).
The code adds into the existing tag formatting code. The user can
specify exactly how a tag should be displayed normally, when deleted,
or when added.
Since the formatting code matches regexps a user can match all deleted
tags with a ".*" in notmuch-tag-deleted-formats. For example setting
notmuch-tag-deleted-formats to '((".*" nil)) tells notmuch not to show
deleted tags at all.
All the variables are customizable; however, more complicated cases
like changing the face depending on the type of display will require
custom lisp.
Currently this overrides notmuch-tag-deleted-formats for the tests
setting it to '((".*" nil)) so that they get removed from the display
and, thus, all tests still pass.
2014-03-22 12:51:09 +01:00
|
|
|
(when (eq formatted-tag 'missing)
|
|
|
|
(let ((base (notmuch-tag--get-formats tag notmuch-tag-formats))
|
2020-04-25 22:18:07 +02:00
|
|
|
(over (cl-case tag-state
|
emacs: show: mark tags changed since buffer loaded
This allows (and requires) the original-tags to be passed along with
the current-tags to be passed to notmuch-tag-format-tags. This allows
the tag formatting to show added and deleted tags.By default a removed
tag is displayed with strike-through in red (if strike-through is not
available, eg on a terminal, inverse video is used instead) and an
added tag is displayed underlined in green.
If the caller does not wish to use the new feature it can pass
current-tags for both arguments and, at this point, we do exactly that
in the three callers of this function.
Note, we cannot tidily allow original-tags to be optional because we would
need to distinguish nil meaning "we are not specifying original-tags"
from nil meaning there were no original-tags (an empty list).
We use this in subsequent patches to make it clear when a message was
unread when you first loaded a show buffer (previously the unread tag
could be removed before a user realised that it had been unread).
The code adds into the existing tag formatting code. The user can
specify exactly how a tag should be displayed normally, when deleted,
or when added.
Since the formatting code matches regexps a user can match all deleted
tags with a ".*" in notmuch-tag-deleted-formats. For example setting
notmuch-tag-deleted-formats to '((".*" nil)) tells notmuch not to show
deleted tags at all.
All the variables are customizable; however, more complicated cases
like changing the face depending on the type of display will require
custom lisp.
Currently this overrides notmuch-tag-deleted-formats for the tests
setting it to '((".*" nil)) so that they get removed from the display
and, thus, all tests still pass.
2014-03-22 12:51:09 +01:00
|
|
|
(deleted (notmuch-tag--get-formats
|
|
|
|
tag notmuch-tag-deleted-formats))
|
|
|
|
(added (notmuch-tag--get-formats
|
|
|
|
tag notmuch-tag-added-formats))
|
|
|
|
(otherwise nil))))
|
|
|
|
(setq formatted-tag (notmuch-tag--do-format tag tag base))
|
|
|
|
(setq formatted-tag (notmuch-tag--do-format tag formatted-tag over))
|
|
|
|
(puthash (cons tag tag-state) formatted-tag notmuch-tag--format-cache)))
|
|
|
|
formatted-tag))
|
|
|
|
|
|
|
|
(defun notmuch-tag-format-tags (tags orig-tags &optional face)
|
2013-03-23 12:29:54 +01:00
|
|
|
"Return a string representing formatted TAGS."
|
emacs: show: mark tags changed since buffer loaded
This allows (and requires) the original-tags to be passed along with
the current-tags to be passed to notmuch-tag-format-tags. This allows
the tag formatting to show added and deleted tags.By default a removed
tag is displayed with strike-through in red (if strike-through is not
available, eg on a terminal, inverse video is used instead) and an
added tag is displayed underlined in green.
If the caller does not wish to use the new feature it can pass
current-tags for both arguments and, at this point, we do exactly that
in the three callers of this function.
Note, we cannot tidily allow original-tags to be optional because we would
need to distinguish nil meaning "we are not specifying original-tags"
from nil meaning there were no original-tags (an empty list).
We use this in subsequent patches to make it clear when a message was
unread when you first loaded a show buffer (previously the unread tag
could be removed before a user realised that it had been unread).
The code adds into the existing tag formatting code. The user can
specify exactly how a tag should be displayed normally, when deleted,
or when added.
Since the formatting code matches regexps a user can match all deleted
tags with a ".*" in notmuch-tag-deleted-formats. For example setting
notmuch-tag-deleted-formats to '((".*" nil)) tells notmuch not to show
deleted tags at all.
All the variables are customizable; however, more complicated cases
like changing the face depending on the type of display will require
custom lisp.
Currently this overrides notmuch-tag-deleted-formats for the tests
setting it to '((".*" nil)) so that they get removed from the display
and, thus, all tests still pass.
2014-03-22 12:51:09 +01:00
|
|
|
(let ((face (or face 'notmuch-tag-face))
|
|
|
|
(all-tags (sort (delete-dups (append tags orig-tags nil)) #'string<)))
|
2014-03-22 12:51:05 +01:00
|
|
|
(notmuch-apply-face
|
2014-01-11 22:49:52 +01:00
|
|
|
(mapconcat #'identity
|
|
|
|
;; nil indicated that the tag was deliberately hidden
|
2020-08-08 13:49:36 +02:00
|
|
|
(delq nil (mapcar (apply-partially #'notmuch-tag-format-tag
|
|
|
|
tags orig-tags)
|
|
|
|
all-tags))
|
2014-01-11 22:49:52 +01:00
|
|
|
" ")
|
|
|
|
face
|
|
|
|
t)))
|
2013-03-23 12:29:54 +01: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
|
|
|
;;; Hooks
|
|
|
|
|
2012-04-14 20:52:50 +02:00
|
|
|
(defcustom notmuch-before-tag-hook nil
|
|
|
|
"Hooks that are run before tags of a message are modified.
|
|
|
|
|
2015-06-16 23:47:20 +02:00
|
|
|
'tag-changes' will contain the tags that are about to be added or removed as
|
2012-04-14 20:52:50 +02:00
|
|
|
a list of strings of the form \"+TAG\" or \"-TAG\".
|
|
|
|
'query' will be a string containing the search query that determines
|
2020-05-24 21:17:56 +02:00
|
|
|
the messages that are about to be tagged."
|
2012-04-14 20:52:50 +02:00
|
|
|
:type 'hook
|
|
|
|
:options '(notmuch-hl-line-mode)
|
|
|
|
:group 'notmuch-hooks)
|
|
|
|
|
|
|
|
(defcustom notmuch-after-tag-hook nil
|
|
|
|
"Hooks that are run after tags of a message are modified.
|
|
|
|
|
2015-06-16 23:47:20 +02:00
|
|
|
'tag-changes' will contain the tags that were added or removed as
|
2012-04-14 20:52:50 +02:00
|
|
|
a list of strings of the form \"+TAG\" or \"-TAG\".
|
|
|
|
'query' will be a string containing the search query that determines
|
2020-05-24 21:17:56 +02:00
|
|
|
the messages that were tagged."
|
2012-04-14 20:52:50 +02:00
|
|
|
:type 'hook
|
|
|
|
:options '(notmuch-hl-line-mode)
|
|
|
|
:group 'notmuch-hooks)
|
|
|
|
|
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
|
|
|
;;; User Input
|
|
|
|
|
2012-04-14 20:52:50 +02:00
|
|
|
(defvar notmuch-select-tag-history nil
|
2021-01-10 15:01:01 +01:00
|
|
|
"Minibuffer history of `notmuch-select-tag-with-completion' function.")
|
2012-04-14 20:52:50 +02:00
|
|
|
|
|
|
|
(defvar notmuch-read-tag-changes-history nil
|
2021-01-10 15:01:01 +01:00
|
|
|
"Minibuffer history of `notmuch-read-tag-changes' function.")
|
2012-04-14 20:52:50 +02:00
|
|
|
|
2013-10-23 02:21:55 +02:00
|
|
|
(defun notmuch-tag-completions (&rest search-terms)
|
|
|
|
"Return a list of tags for messages matching SEARCH-TERMS.
|
|
|
|
|
2021-01-10 15:01:01 +01:00
|
|
|
Return all tags if no search terms are given."
|
2020-08-08 13:49:42 +02:00
|
|
|
(unless search-terms
|
|
|
|
(setq search-terms (list "*")))
|
2012-04-14 20:52:50 +02:00
|
|
|
(split-string
|
|
|
|
(with-output-to-string
|
|
|
|
(with-current-buffer standard-output
|
2021-09-11 16:04:08 +02:00
|
|
|
(apply 'notmuch--call-process notmuch-command nil t
|
2012-04-14 20:52:50 +02:00
|
|
|
nil "search" "--output=tags" "--exclude=false" search-terms)))
|
|
|
|
"\n+" t))
|
|
|
|
|
|
|
|
(defun notmuch-select-tag-with-completion (prompt &rest search-terms)
|
2021-01-10 15:01:06 +01:00
|
|
|
(completing-read prompt
|
|
|
|
(apply #'notmuch-tag-completions search-terms)
|
|
|
|
nil nil nil 'notmuch-select-tag-history))
|
2012-04-14 20:52:50 +02:00
|
|
|
|
2013-10-23 02:21:55 +02:00
|
|
|
(defun notmuch-read-tag-changes (current-tags &optional prompt initial-input)
|
|
|
|
"Prompt for tag changes in the minibuffer.
|
|
|
|
|
2021-01-10 15:01:01 +01:00
|
|
|
CURRENT-TAGS is a list of tags that are present on the message
|
|
|
|
or messages to be changed. These are offered as tag removal
|
2013-10-23 02:21:55 +02:00
|
|
|
completions. CURRENT-TAGS may contain duplicates. PROMPT, if
|
|
|
|
non-nil, is the query string to present in the minibuffer. It
|
|
|
|
defaults to \"Tags\". INITIAL-INPUT, if non-nil, will be the
|
|
|
|
initial input in the minibuffer."
|
2012-04-14 20:52:50 +02:00
|
|
|
(let* ((all-tag-list (notmuch-tag-completions))
|
|
|
|
(add-tag-list (mapcar (apply-partially 'concat "+") all-tag-list))
|
2013-10-23 02:21:55 +02:00
|
|
|
(remove-tag-list (mapcar (apply-partially 'concat "-") current-tags))
|
2012-04-14 20:52:50 +02:00
|
|
|
(tag-list (append add-tag-list remove-tag-list))
|
2013-10-23 02:21:55 +02:00
|
|
|
(prompt (concat (or prompt "Tags") " (+add -drop): "))
|
2012-04-14 20:52:50 +02:00
|
|
|
(crm-separator " ")
|
|
|
|
;; By default, space is bound to "complete word" function.
|
|
|
|
;; Re-bind it to insert a space instead. Note that <tab>
|
|
|
|
;; still does the completion.
|
|
|
|
(crm-local-completion-map
|
|
|
|
(let ((map (make-sparse-keymap)))
|
|
|
|
(set-keymap-parent map crm-local-completion-map)
|
|
|
|
(define-key map " " 'self-insert-command)
|
|
|
|
map)))
|
2021-10-23 19:05:24 +02:00
|
|
|
(completing-read-multiple prompt tag-list
|
|
|
|
nil nil initial-input
|
|
|
|
'notmuch-read-tag-changes-history)))
|
2012-04-14 20:52:50 +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
|
|
|
;;; Tagging
|
|
|
|
|
2012-04-14 20:52:50 +02:00
|
|
|
(defun notmuch-update-tags (tags tag-changes)
|
|
|
|
"Return a copy of TAGS with additions and removals from TAG-CHANGES.
|
|
|
|
|
|
|
|
TAG-CHANGES must be a list of tags names, each prefixed with
|
|
|
|
either a \"+\" to indicate the tag should be added to TAGS if not
|
|
|
|
present or a \"-\" to indicate that the tag should be removed
|
|
|
|
from TAGS if present."
|
|
|
|
(let ((result-tags (copy-sequence tags)))
|
|
|
|
(dolist (tag-change tag-changes)
|
2021-01-10 15:01:09 +01:00
|
|
|
(let ((tag (and (not (string-empty-p tag-change))
|
2021-01-13 18:37:50 +01:00
|
|
|
(substring tag-change 1))))
|
2021-01-10 15:01:06 +01:00
|
|
|
(cl-case (aref tag-change 0)
|
2012-04-14 20:52:50 +02:00
|
|
|
(?+ (unless (member tag result-tags)
|
|
|
|
(push tag result-tags)))
|
|
|
|
(?- (setq result-tags (delete tag result-tags)))
|
|
|
|
(otherwise
|
|
|
|
(error "Changed tag must be of the form `+this_tag' or `-that_tag'")))))
|
|
|
|
(sort result-tags 'string<)))
|
|
|
|
|
2013-10-24 17:19:07 +02:00
|
|
|
(defconst notmuch-tag-argument-limit 1000
|
|
|
|
"Use batch tagging if the tagging query is longer than this.
|
|
|
|
|
|
|
|
This limits the length of arguments passed to the notmuch CLI to
|
2022-02-12 21:27:37 +01:00
|
|
|
avoid system argument length limits and performance problems.
|
|
|
|
|
|
|
|
NOTE: this variable is no longer used.")
|
|
|
|
|
|
|
|
(make-obsolete-variable 'notmuch-tag-argument-limit nil "notmuch 0.36")
|
2013-10-24 17:19:07 +02:00
|
|
|
|
2022-02-12 21:27:38 +01:00
|
|
|
(defun notmuch-tag (query tag-changes &optional omit-hist)
|
2012-04-14 20:52:50 +02:00
|
|
|
"Add/remove tags in TAG-CHANGES to messages matching QUERY.
|
|
|
|
|
2012-04-14 22:49:07 +02:00
|
|
|
QUERY should be a string containing the search-terms.
|
2022-02-12 21:27:38 +01:00
|
|
|
TAG-CHANGES is a list of strings of the form \"+tag\" or \"-tag\"
|
|
|
|
to add or remove tags, respectively. OMIT-HIST disables history
|
|
|
|
tracking if non-nil.
|
2012-04-14 20:52:50 +02:00
|
|
|
|
2017-08-14 07:54:56 +02:00
|
|
|
Note: Other code should always use this function to alter tags of
|
2012-04-14 20:52:50 +02:00
|
|
|
messages instead of running (notmuch-call-notmuch-process \"tag\" ..)
|
|
|
|
directly, so that hooks specified in notmuch-before-tag-hook and
|
|
|
|
notmuch-after-tag-hook will be run."
|
|
|
|
;; Perform some validation
|
2021-01-13 18:37:50 +01:00
|
|
|
(dolist (tag-change tag-changes)
|
|
|
|
(unless (string-match-p "^[-+]\\S-+$" tag-change)
|
|
|
|
(error "Tag must be of the form `+this_tag' or `-that_tag'")))
|
2014-05-21 11:58:50 +02:00
|
|
|
(unless query
|
|
|
|
(error "Nothing to tag!"))
|
2021-01-13 18:37:50 +01:00
|
|
|
(when tag-changes
|
2021-05-08 14:11:12 +02:00
|
|
|
(notmuch-dlet ((tag-changes tag-changes)
|
|
|
|
(query query))
|
|
|
|
(run-hooks 'notmuch-before-tag-hook))
|
2022-02-12 21:27:38 +01:00
|
|
|
(with-temp-buffer
|
|
|
|
(insert (concat (mapconcat #'notmuch-hex-encode tag-changes " ") " -- " query))
|
|
|
|
(unless (= 0
|
|
|
|
(notmuch--call-process-region
|
|
|
|
(point-min) (point-max) notmuch-command t t nil "tag" "--batch"))
|
|
|
|
(notmuch-logged-error "notmuch tag failed" (buffer-string))))
|
|
|
|
(unless omit-hist
|
|
|
|
(push (list :query query :tag-changes tag-changes) notmuch-tag-history)))
|
2022-02-12 21:27:37 +01:00
|
|
|
(notmuch-dlet ((tag-changes tag-changes)
|
2022-02-12 21:27:38 +01:00
|
|
|
(query query))
|
|
|
|
(run-hooks 'notmuch-after-tag-hook)))
|
2012-04-14 20:52:50 +02:00
|
|
|
|
2022-02-12 21:27:39 +01:00
|
|
|
(defun notmuch-tag-undo ()
|
|
|
|
"Undo the previous tagging operation in the current buffer. Uses
|
|
|
|
buffer local variable `notmuch-tag-history' to determine what
|
|
|
|
that operation was."
|
|
|
|
(interactive)
|
|
|
|
(when (null notmuch-tag-history)
|
|
|
|
(error "no further notmuch undo information"))
|
|
|
|
(let* ((action (pop notmuch-tag-history))
|
|
|
|
(query (plist-get action :query))
|
|
|
|
(changes (notmuch-tag-change-list (plist-get action :tag-changes) t)))
|
|
|
|
(notmuch-tag query changes t))
|
|
|
|
(notmuch-refresh-this-buffer))
|
|
|
|
|
2012-09-06 17:32:37 +02:00
|
|
|
(defun notmuch-tag-change-list (tags &optional reverse)
|
|
|
|
"Convert TAGS into a list of tag changes.
|
|
|
|
|
|
|
|
Add a \"+\" prefix to any tag in TAGS list that doesn't already
|
|
|
|
begin with a \"+\" or a \"-\". If REVERSE is non-nil, replace all
|
|
|
|
\"+\" prefixes with \"-\" and vice versa in the result."
|
|
|
|
(mapcar (lambda (str)
|
|
|
|
(let ((s (if (string-match "^[+-]" str) str (concat "+" str))))
|
|
|
|
(if reverse
|
|
|
|
(concat (if (= (string-to-char s) ?-) "+" "-")
|
|
|
|
(substring s 1))
|
|
|
|
s)))
|
|
|
|
tags))
|
|
|
|
|
2016-10-06 23:59:00 +02:00
|
|
|
(defvar notmuch-tag-jump-reverse-key "k"
|
|
|
|
"The key in tag-jump to switch to the reverse tag changes.")
|
|
|
|
|
2016-09-20 21:57:16 +02:00
|
|
|
(defun notmuch-tag-jump (reverse)
|
|
|
|
"Create a jump menu for tagging operations.
|
|
|
|
|
|
|
|
Creates and displays a jump menu for the tagging operations
|
|
|
|
specified in `notmuch-tagging-keys'. If REVERSE is set then it
|
|
|
|
offers a menu of the reverses of the operations specified in
|
2020-11-16 22:28:30 +01:00
|
|
|
`notmuch-tagging-keys'; i.e. each `+tag' is replaced by `-tag'
|
2016-09-20 21:57:16 +02:00
|
|
|
and vice versa."
|
|
|
|
;; In principle this function is simple, but it has to deal with
|
|
|
|
;; lots of cases: different modes (search/show/tree), whether a name
|
|
|
|
;; is specified, whether the tagging operations is a list of
|
|
|
|
;; tag-ops, or a symbol that evaluates to such a list, and whether
|
|
|
|
;; REVERSE is specified.
|
|
|
|
(interactive "P")
|
|
|
|
(let (action-map)
|
2020-04-25 22:18:07 +02:00
|
|
|
(pcase-dolist (`(,key ,tag ,name) notmuch-tagging-keys)
|
|
|
|
(let* ((tag-function (cl-case major-mode
|
2016-09-20 21:57:16 +02:00
|
|
|
(notmuch-search-mode #'notmuch-search-tag)
|
|
|
|
(notmuch-show-mode #'notmuch-show-tag)
|
|
|
|
(notmuch-tree-mode #'notmuch-tree-tag)))
|
2020-04-25 22:18:07 +02:00
|
|
|
(tag (if (symbolp tag)
|
|
|
|
(symbol-value tag)
|
|
|
|
tag))
|
2016-09-20 21:57:16 +02:00
|
|
|
(tag-change (if reverse
|
2020-11-16 22:28:41 +01:00
|
|
|
(notmuch-tag-change-list tag t)
|
2020-04-25 22:18:07 +02:00
|
|
|
tag))
|
|
|
|
(name (or (and (not (string= name ""))
|
|
|
|
name)
|
|
|
|
(and (symbolp name)
|
|
|
|
(symbol-name name))))
|
2016-09-20 21:57:16 +02:00
|
|
|
(name-string (if name
|
2020-08-08 13:49:44 +02:00
|
|
|
(if reverse
|
|
|
|
(concat "Reverse " name)
|
2016-09-20 21:57:16 +02:00
|
|
|
name)
|
|
|
|
(mapconcat #'identity tag-change " "))))
|
|
|
|
(push (list key name-string
|
2021-07-19 13:31:05 +02:00
|
|
|
(lambda () (funcall tag-function tag-change)))
|
2016-09-20 21:57:16 +02:00
|
|
|
action-map)))
|
2016-10-06 23:59:00 +02:00
|
|
|
(push (list notmuch-tag-jump-reverse-key
|
|
|
|
(if reverse
|
|
|
|
"Forward tag changes "
|
|
|
|
"Reverse tag changes")
|
2016-09-20 21:57:16 +02:00
|
|
|
(apply-partially 'notmuch-tag-jump (not reverse)))
|
|
|
|
action-map)
|
|
|
|
(setq action-map (nreverse action-map))
|
|
|
|
(notmuch-jump action-map "Tag: ")))
|
2012-09-06 17:32:37 +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
|
|
|
;;; _
|
2012-04-14 20:52:50 +02:00
|
|
|
|
|
|
|
(provide 'notmuch-tag)
|
2020-08-08 13:50:00 +02:00
|
|
|
|
|
|
|
;;; notmuch-tag.el ends here
|