From 4ce296d6b2823cfee0eeb8f5ac05083f5cd46d36 Mon Sep 17 00:00:00 2001 From: Jonas Bernoulli Date: Mon, 17 Feb 2020 11:46:31 +0100 Subject: [PATCH] manual: Deal with annoying misfeature of texinfo Texinfo is of the opinion that every hyperlink has to be prefixed by either "see" or "in". If neither of these words appears there, then it inserts "see" and it cannot be told not to do that. This turns a correct sentence like: > Mu4e lets you define custom actions for messages in the . into: > Mu4e lets you define custom actions for messages in the see . The best compromise is > Mu4e lets you define custom actions for messages in . which isn't correct but at least less messed up. Alternatively one could rephrase every sentence that contains a link to circumvent Texinfo's speech impairment. Or one could replace each link with a footnote and place the actual link in the footnote. --- mu4e/mu4e.texi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/mu4e/mu4e.texi b/mu4e/mu4e.texi index 99020602..2aed71b3 100644 --- a/mu4e/mu4e.texi +++ b/mu4e/mu4e.texi @@ -2864,8 +2864,8 @@ edited. When you compose a totally new message, the @var{msg} parameter is @node Actions @chapter Actions -@t{mu4e} lets you define custom actions for messages in the @ref{Headers view} -and for both messages and attachments in the @ref{Message view}. Custom +@t{mu4e} lets you define custom actions for messages in @ref{Headers view} +and for both messages and attachments in @ref{Message view}. Custom actions allow you to easily extend @t{mu4e} for specific needs --- for example, marking messages as spam in a spam filter or applying an attachment with a source code patch.