(setq notmuch-saved-searches '((:name "inbox"
:query "tag:inbox"
:count-query "tag:inbox and tag:unread"
- :sort-order 'oldest-first)))
+ :sort-order oldest-first)))
specifies a single saved search for inbox, but the number displayed by
the search will be the number of unread messages in the inbox, and the
from notmuch. It also includes a vim plugin.
You can perform tab-completion using any of these programs.
-Just add the following to your [notmuch init file](#notmuch_init_file):
+Just add the following to your [notmuch init file](/notmuch-emacs#notmuch_init_file):
(require 'notmuch-address)
(setq notmuch-address-command "/path/to/address_fetching_program")
You will find the akonadimailsearch binary in the build/src directory. Copy it to ~/bin .
You can now add the following settings to your
-[notmuch init file](#notmuch_init_file):
+[notmuch init file](/notmuch-emacs#notmuch_init_file):
(require 'notmuch-address)
(setq notmuch-address-command "~/bin/akonadimailsearch")
## Resending (or bouncing) messages
-Add the following to your [notmuch init file](#notmuch_init_file) to be able
+Add the following to your [notmuch init file](/notmuch-emacs#notmuch_init_file) to be able
to resend the current message in show mode.
(define-key notmuch-show-mode-map "b"
## `notmuch-hello` refresh status message
-Add the following to your [notmuch init file](#notmuch_init_file) to get a
+Add the following to your [notmuch init file](/notmuch-emacs#notmuch_init_file) to get a
status message about the change in the number of messages in the mail store
when refreshing the `notmuch-hello` buffer.
Mailman mailing list software rewrites and rewraps long message subjects in
a way that causes TABs to appear in the middle of the subject and header
-lines. Add this to your [notmuch init file](#notmuch_init_file) to replace
+lines. Add this to your [notmuch init file](/notmuch-emacs#notmuch_init_file) to replace
tabs with spaces in subject lines:
(defun notmuch-show-subject-tabs-to-spaces ()
Add a new entry with "Function returning the URL:" set to:
- (lambda (message-id)
- (concat "http://patchwork.example.com/patch/"
- (nth 0
- (process-lines "/path/to/pwclient" "search"
- "-p" "the-project"
- "-m" (concat "<" message-id ">")
- "-n" "1"
- "-f" "%{id}"))))
+ (lambda (message-id)
+ (concat "http://patchwork.example.com/patch/"
+ (nth 0
+ (process-lines "/path/to/pwclient" "search"
+ "-p" "the-project"
+ "-m" (concat "<" message-id ">")
+ "-n" "1"
+ "-f" "%{id}"))))
Replacing `http://patchwork.example.com/patch/`, `/path/to/pwclient`, and
`the-project` appropiately. You should now be able to stash the Patchwork URL
Going further, if the patch has been committed, you can get the commit hash with
this:
- (lambda (message-id)
- (nth 0
- (process-lines "/path/to/pwclient" "search"
- "-p" "the-project"
- "-m" (concat "<" message-id ">")
- "-n" "1"
- "-f" "%{commit_ref}")))
+ (lambda (message-id)
+ (nth 0
+ (process-lines "/path/to/pwclient" "search"
+ "-p" "the-project"
+ "-m" (concat "<" message-id ">")
+ "-n" "1"
+ "-f" "%{commit_ref}")))
And finally, if the project has a web interface to its source repository, you
can turn the commit hash into a URL pointing there, for example:
- (lambda (message-id)
- (concat "http://cgit.example.com/the-project/commit/?id="
- (nth 0
- (process-lines "/path/to/pwclient" "search"
- "-p" "the-project"
- "-m" (concat "<" message-id ">")
- "-n" "1"
- "-f" "%{commit_ref}"))))
+ (lambda (message-id)
+ (concat "http://cgit.example.com/the-project/commit/?id="
+ (nth 0
+ (process-lines "/path/to/pwclient" "search"
+ "-p" "the-project"
+ "-m" (concat "<" message-id ">")
+ "-n" "1"
+ "-f" "%{commit_ref}"))))