From: Pádraig Brady <P@draigBrady.com>
Date: Wed, 12 Aug 2020 17:40:04 +0000 (+0100)
Subject: doc: clarify timeout --foreground description
X-Git-Tag: v9.0~205
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=5b8161ee4dc95308c9ef89a5268aa87a7f32d4bf;p=thirdparty%2Fcoreutils.git

doc: clarify timeout --foreground description

* doc/coreutils.texi (timeout invocation): Avoid any implication
that `timeout --foreground` could be used to retroactively
timeout commands not already invoked by timeout(1).
Fixes bug https://bugs.gnu.org/42831
---

diff --git a/doc/coreutils.texi b/doc/coreutils.texi
index 52d4cfcbec..a55514d594 100644
--- a/doc/coreutils.texi
+++ b/doc/coreutils.texi
@@ -18077,8 +18077,8 @@ managed @var{command} supports running for an indeterminate amount of time.
 @opindex --foreground
 Don't create a separate background program group, so that
 the managed @var{command} can use the foreground TTY normally.
-This is needed to support timing out commands not started
-directly from an interactive shell, in two situations.
+This is needed to support two situations when timing out commands,
+when not invoking @command{timeout} from an interactive shell.
 @enumerate
 @item
 @var{command} is interactive and needs to read from the terminal for example