* update some comments

This commit is contained in:
djcb 2013-08-17 11:54:22 +03:00
parent f89447e65c
commit 6a098c7be3
2 changed files with 6 additions and 4 deletions

View File

@ -1013,6 +1013,8 @@ limited to the message at point and its descendants."
(let* ((msg (mu4e-message-at-point))
(thread-id (mu4e~headers-get-thread-info msg 'thread-id))
(path (mu4e~headers-get-thread-info msg 'path))
;; FIXME: e.g., for refiling we should evaluate this
;; for each line separately
(markpair
(mu4e~mark-get-markpair
(if subthread "Mark subthread with: " "Mark whole thread with: ")
@ -1248,7 +1250,7 @@ _not_ refresh the last search with the new setting for threading."
(erase-buffer)
(local-set-key (kbd "q") 'kill-buffer-and-window)
(insert (propertize "Waiting for message..."
'face 'mu4e-system-face 'intangible t))))
'face 'mu4e-system-face 'intangible t))))
mu4e~headers-loading-buf)
(defun mu4e-headers-view-message ()

View File

@ -581,9 +581,9 @@ This is used in the user-interface (the column headers in the header list, and
the fields the message view).
Most fields should be self-explanatory. A special one is
`:from-or-to', which is equal to `:from' unless `:from' matches
`mu4e-user-mail-address-regexp', in which case it will be equal to
`:to'.
`:from-or-to', which is equal to `:from' unless `:from' matches one
of the addresses in `mu4e-user-mail-address-list', in which case it
will be equal to `:to'.
Furthermore, the property `:sortable' determines whether we can
sort by this field. This can be either a boolean (nil or t), or a