Lightly copyedit the documentation and docstrings

This commit is contained in:
mjn 2014-08-08 13:18:29 +02:00
parent daa46612ab
commit c99ccf9a19
3 changed files with 9 additions and 9 deletions

View File

@ -133,7 +133,7 @@ of the message, as listed in the following table:
p,passed Passed ('Handled')
r,replied Replied
s,seen Seen
t,thrashed Marked for deletion
t,trashed Marked for deletion
a,attach Has attachment
z,signed Signed message
x,encrypted Encrypted message

View File

@ -138,7 +138,7 @@ The following marks are available, and the corresponding props:
`flag' n mark this message for flagging
`move' y move the message to some folder
`read' n mark the message as read
`trash' y thrash the message to some folder
`trash' y trash the message to some folder
`unflag' n mark this message for unflagging
`untrash' n remove the 'trashed' flag from a message
`unmark' n unmark this message
@ -286,7 +286,7 @@ user which one)."
mu4e~mark-map))))
(defun mu4e~mark-check-target (target)
"Check if the target exists if not, offer to create it."
"Check if the target exists; if not, offer to create it."
(let ((fulltarget (concat mu4e-maildir target)))
(if (not (mu4e-create-maildir-maybe fulltarget))
(mu4e-error "Target dir %s does not exist " fulltarget)
@ -298,9 +298,9 @@ user which one)."
After the actions have been executed succesfully, the affected
messages are *hidden* from the current header list. Since the
headers are the result of a search, we cannot be certain that the
messages no longer matches the current one - to get that
messages no longer match the current one - to get that
certainty, we need to rerun the search, but we don't want to do
that automatically, as it may be too slow and/or break the users
that automatically, as it may be too slow and/or break the user's
flow. Therefore, we hide the message, which in practice seems to
work well.

View File

@ -810,7 +810,7 @@ W toggle include-related
marking
-------
d mark for moving to the trash folder
= mark for remove thrash flags ('untrash')
= mark for removing trash flag ('untrash')
DEL,D mark for complete deletion
m mark for moving to another maildir folder
r mark for refiling
@ -1076,7 +1076,7 @@ M-right next query
marking
-------
d mark for moving to the trash folder
= mark for remove thrash flags ('untrash')
= mark for removing trash flag ('untrash')
DEL,D mark for complete deletion
m mark for moving to another maildir folder
r mark for refiling
@ -1836,12 +1836,12 @@ previous/next queries, you can use @kbd{M-x mu4e-headers-forget-queries}.
It can be useful to narrow existing search results, that is, to add some
clauses to the current query to match fewer messages.
For example, suppose you're looking at the some mailing list, perhaps by
For example, suppose you're looking at some mailing list, perhaps by
jumping to a maildir (@kbd{M-x mu4e-headers-jump-to-maildir}, @key{j}) or
because you followed some bookmark (@kbd{M-x mu4e-headers-search-bookmark},
@key{b}). Now, you want to narrow things down to only those messages that have
attachments.
1
This is when @kbd{M-x mu4e-headers-search-narrow} (@key{/}) comes in handy. It
asks for an additional search pattern, which is appended to the current search
query, in effect getting you the subset of the currently shown headers that