* update some comments
This commit is contained in:
@ -1013,6 +1013,8 @@ limited to the message at point and its descendants."
|
|||||||
(let* ((msg (mu4e-message-at-point))
|
(let* ((msg (mu4e-message-at-point))
|
||||||
(thread-id (mu4e~headers-get-thread-info msg 'thread-id))
|
(thread-id (mu4e~headers-get-thread-info msg 'thread-id))
|
||||||
(path (mu4e~headers-get-thread-info msg 'path))
|
(path (mu4e~headers-get-thread-info msg 'path))
|
||||||
|
;; FIXME: e.g., for refiling we should evaluate this
|
||||||
|
;; for each line separately
|
||||||
(markpair
|
(markpair
|
||||||
(mu4e~mark-get-markpair
|
(mu4e~mark-get-markpair
|
||||||
(if subthread "Mark subthread with: " "Mark whole thread with: ")
|
(if subthread "Mark subthread with: " "Mark whole thread with: ")
|
||||||
|
|||||||
@ -581,9 +581,9 @@ This is used in the user-interface (the column headers in the header list, and
|
|||||||
the fields the message view).
|
the fields the message view).
|
||||||
|
|
||||||
Most fields should be self-explanatory. A special one is
|
Most fields should be self-explanatory. A special one is
|
||||||
`:from-or-to', which is equal to `:from' unless `:from' matches
|
`:from-or-to', which is equal to `:from' unless `:from' matches one
|
||||||
`mu4e-user-mail-address-regexp', in which case it will be equal to
|
of the addresses in `mu4e-user-mail-address-list', in which case it
|
||||||
`:to'.
|
will be equal to `:to'.
|
||||||
|
|
||||||
Furthermore, the property `:sortable' determines whether we can
|
Furthermore, the property `:sortable' determines whether we can
|
||||||
sort by this field. This can be either a boolean (nil or t), or a
|
sort by this field. This can be either a boolean (nil or t), or a
|
||||||
|
|||||||
Reference in New Issue
Block a user