From 10c0507665649080be152fe1392630471cce0ff1 Mon Sep 17 00:00:00 2001 From: Sebastian Miele Date: Mon, 11 Mar 2019 13:30:19 +0100 Subject: [PATCH] mu4e: Fix some typos --- mu4e/mu4e-vars.el | 2 +- mu4e/mu4e.texi | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/mu4e/mu4e-vars.el b/mu4e/mu4e-vars.el index c0886632..eb36deca 100644 --- a/mu4e/mu4e-vars.el +++ b/mu4e/mu4e-vars.el @@ -830,7 +830,7 @@ sort by this field. This can be either a boolean (nil or t), or a symbol for /another/ field. For example, the `:human-date' field uses `:date' for that. -Fields with which have the property `:require-full' set to +Fields which have the property `:require-full' set to non-nil require a full message; in practice this means that you cannot use such fieds as part of `mu4e-headers-fields', but only in `mu4e-view-fields.' diff --git a/mu4e/mu4e.texi b/mu4e/mu4e.texi index d7f9efc3..1a01764b 100644 --- a/mu4e/mu4e.texi +++ b/mu4e/mu4e.texi @@ -813,11 +813,11 @@ custom fields using @code{mu4e-header-info-custom}; see @ref{HV Custom headers} for details. @item By default, the date is shown with the @t{:human-date} field, which shows the @emph{time} for today's messages, and the @emph{date} for older -messages. If you want to distinguish between `today' and `older', you can use +messages. If you do not want to distinguish between `today' and `older', you can use the @t{:date} field instead. @item You can customize the date and time formats with the variable @code{mu4e-headers-date-format} and @code{mu4e-headers-time-format}, -respectively. In the example, we use @code{:human-date}, which shows when the +respectively. In the example, we use @code{:human-date}, which shows the time when the message was sent today, and the date otherwise. @item By default, the subject is shown using the @t{:subject} field; however, it is also possible to use @t{:thread-subject}, which shows