11.1 Defining actions ¶

Defining a new custom action comes down to writing an elisp-function to do the work. Functions that operate on messages receive a msg parameter, which corresponds to the message at point. Something like:

(defun my-action-func (msg)
  "Describe my message function."
  ;; do stuff
  )

Functions that operate on attachments receive a msg parameter, which corresponds to the message at point, and an attachment-num, which is the number of the attachment as seen in the message view. An attachment function looks like:

(defun my-attachment-action-func (msg attachment-num)
  "Describe my attachment function."
  ;; do stuff
  )

After you have defined your function, you can add it to the list of actions¹⁷, either mu4e-headers-actions, mu4e-view-actions or mu4e-view-mime-part-actions. The format¹⁸ of each action is a cons-cell, (DESCRIPTION . VALUE); see below for some examples. If your shortcut is not also the first character of the description, simply prefix the description with that character.

Let’s look at some examples.