From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: tools-reference/echo/
Date: Fri, 23 Aug 2024 15:22:13 +0000 (UTC) [thread overview]
Message-ID: <1724426191.0edced44cbbbb3bac79448fbf8b1620ecc2b39df.ulm@gentoo> (raw)
commit: 0edced44cbbbb3bac79448fbf8b1620ecc2b39df
Author: Sebastian Engel <sighunter <AT> gmx <DOT> de>
AuthorDate: Mon Aug 12 21:29:44 2024 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Fri Aug 23 15:16:31 2024 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=0edced44
tools-reference/echo: Format the word variable as inline code
The devmanual commonly uses <c> to format variables in text passages as code
to make them more distinguishable from the rest of the text and that's why
it should be done here too.
Signed-off-by: Sebastian Engel <sighunter <AT> gmx.de>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
tools-reference/echo/text.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools-reference/echo/text.xml b/tools-reference/echo/text.xml
index 9bce77c..dba3452 100644
--- a/tools-reference/echo/text.xml
+++ b/tools-reference/echo/text.xml
@@ -47,7 +47,7 @@ As of >=bash-2.05b, the so-called "here strings" have been
introduced. Using "here strings", you can pass contents of an
environment variable to the standard input of an application, using
<c><<<word</c> redirection: what actually happens is
-that <c>bash</c> expands word and passes the result to the standard
+that <c>bash</c> expands <c>word</c> and passes the result to the standard
input.
</p>
next reply other threads:[~2024-08-23 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 15:22 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-23 15:22 [gentoo-commits] proj/devmanual:master commit in: tools-reference/echo/ Ulrich Müller
2024-08-31 16:43 Ulrich Müller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1724426191.0edced44cbbbb3bac79448fbf8b1620ecc2b39df.ulm@gentoo \
--to=ulm@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox