From: Glenn Washburn <development@efficientek.com>
To: grub-devel@gnu.org, Daniel Kiper <dkiper@net-space.pl>
Cc: Glenn Washburn <development@efficientek.com>
Subject: [PATCH] docs: Commandline and menu entry commands are now separated
Date: Sat, 13 May 2023 21:05:35 -0500 [thread overview]
Message-ID: <20230514020535.226393-1-development@efficientek.com> (raw)
The menu entry commands now have their own section. Change the wording in
the section that they were in to reflect this.
Signed-off-by: Glenn Washburn <development@efficientek.com>
---
docs/grub.texi | 11 +++++------
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/docs/grub.texi b/docs/grub.texi
index 1324175fbe3f..9d4adf0b8ab6 100644
--- a/docs/grub.texi
+++ b/docs/grub.texi
@@ -3167,9 +3167,8 @@ The command-line interface provides a prompt and after it an editable
text area much like a command-line in Unix or DOS. Each command is
immediately executed after it is entered@footnote{However, this
behavior will be changed in the future version, in a user-invisible
-way.}. The commands (@pxref{Command-line and menu entry commands}) are a
-subset of those available in the configuration file, used with exactly
-the same syntax.
+way.}. The commands (@pxref{Commands}) are a subset of those available
+in the configuration file, used with exactly the same syntax.
Cursor movement and editing of the text on the line can be done via a
subset of the functions available in the Bash shell:
@@ -3910,7 +3909,7 @@ shell}.
* Menu-specific commands::
* Loader commands::
* General commands::
-* Command-line and menu entry commands::
+* Command-line commands::
* Networking commands::
* Undocumented commands::
@end menu
@@ -4283,8 +4282,8 @@ printed.
@end deffn
-@node Command-line and menu entry commands
-@section The list of command-line and menu entry commands
+@node Command-line commands
+@section The list of command-line commands
These commands are usable in the command-line and in menu entries. If
you forget a command, you can run the command @command{help}
--
2.34.1
next reply other threads:[~2023-05-14 2:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-14 2:05 Glenn Washburn [this message]
2023-05-16 13:26 ` [PATCH] docs: Commandline and menu entry commands are now separated Daniel Kiper
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=20230514020535.226393-1-development@efficientek.com \
--to=development@efficientek.com \
--cc=dkiper@net-space.pl \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.