From c5ff7abbb1eb159699de3cba8e5ae5ba1dd04ed8 Mon Sep 17 00:00:00 2001 From: Tristan Riehs Date: Fri, 28 Jun 2024 10:47:05 +0900 Subject: [PATCH 1/2] Add a missing verb --- mu4e/mu4e.texi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mu4e/mu4e.texi b/mu4e/mu4e.texi index 7100c3ce..72f303d6 100644 --- a/mu4e/mu4e.texi +++ b/mu4e/mu4e.texi @@ -789,7 +789,7 @@ changes indeed. So it is mostly useful for tracking changes while you are @emph{not} using @t{mu4e}. For this reason, you can reset the baseline manually, e.g. by visiting the main view . -By comparing current results with the baseline, you can quickly what new +By comparing current results with the baseline, you can quickly see what new messages have arrived since the last time you looked. The baseline@footnote{For debugging, it can be useful to see the time for the From f1132ec7d24f9070c8fac2f011b3289ed5461b81 Mon Sep 17 00:00:00 2001 From: Tristan Riehs Date: Fri, 28 Jun 2024 10:48:57 +0900 Subject: [PATCH 2/2] Correct period misplacement --- mu4e/mu4e.texi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mu4e/mu4e.texi b/mu4e/mu4e.texi index 72f303d6..911e6318 100644 --- a/mu4e/mu4e.texi +++ b/mu4e/mu4e.texi @@ -793,7 +793,7 @@ By comparing current results with the baseline, you can quickly see what new messages have arrived since the last time you looked. The baseline@footnote{For debugging, it can be useful to see the time for the -baseline - for that, there is the @code{mu4e-baseline-time} command} . is reset +baseline - for that, there is the @code{mu4e-baseline-time} command.} is reset automatically when switching to the main view, or invoking @code{buffer-revert} (@kbd{g}) while in the main-view. Visiting the ``favorite'' bookmark does the same(explained below).