From c3bb04150f5b8981fc93ceced843ae5b8e47ab87 Mon Sep 17 00:00:00 2001 From: "Dirk-Jan C. Binnema" Date: Mon, 16 Mar 2020 23:02:59 +0200 Subject: [PATCH] mu4e: mu4e.texi: use an @anchor, not a @node Latter breaks on some (older?) texinfo releases. Fixes #1617 --- mu4e/mu4e.texi | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/mu4e/mu4e.texi b/mu4e/mu4e.texi index db4fad9b..c7bbe462 100644 --- a/mu4e/mu4e.texi +++ b/mu4e/mu4e.texi @@ -3864,7 +3864,7 @@ answers. @section General @subsection Results from @command{mu} and @t{mu4e} differ - why? -@node mu-mu4e-differ +@anchor{mu-mu4e-differ} In general, the same queries for @command{mu} and @t{mu4e} should yield the same results. If they differ, this is usually because one of the following reasons: @@ -3886,8 +3886,7 @@ necessary. @subsection The unread/all counts in the main-screen differ from the 'real' numbers - what's going on? For speed reasons, the counts do not exclude messages that no longer -exist in the file-system, nor does it exclude duplicate messages. See -@ref{mu-mu4e-differ}. +exist in the file-system, nor does it exclude duplicate messages; @xref{mu-mu4e-differ}. @subsection How can I quickly delete/move/trash a lot of messages? You can select ('mark' in Emacs-speak) the messages like you would