emacs-31 2c5b4911b39: ; * doc/lispref/commands.texi (Interactive Codes): More examples of '*'.

branch: emacs-31
commit 2c5b4911b398488b4e6a00d27aa1df93075fd674
Author: Eli Zaretskii <[email protected]>
Commit: Eli Zaretskii <[email protected]>

    ; * doc/lispref/commands.texi (Interactive Codes): More examples of '*'.
---
 doc/lispref/commands.texi | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/doc/lispref/commands.texi b/doc/lispref/commands.texi
index 8614ee53f87..0e993f45b48 100644
--- a/doc/lispref/commands.texi
+++ b/doc/lispref/commands.texi
@@ -393,9 +393,11 @@ many Emacs primitives will signal an error if a command attempts to
 modify text of a read-only buffer, even if the command's interactive
 spec does not include @samp{*}.  So this character is for when you want
 to forcibly signal an error even if the command's implementation doesn't
-invoke any primitives which modify the buffer.  For example, a command
-that binds @code{inhibit-read-only} non-@code{nil} (because it affects
-more than just read-only buffers), or a command which, depending on the
+invoke any primitives which modify the buffer, or if you want to avoid
+processing or side effects of a command that will fail later due to
+buffer modifications.  For example, a command that binds
+@code{inhibit-read-only} non-@code{nil} (because it affects more than
+just read-only buffers), or a command which, depending on the
 conditions, might end up not modifying the buffer, but you want it to
 signal this error anyway.