From: Boruch Baum <boruch_baum@gmx.com>
To: 43749@debbugs.gnu.org
Subject: bug#43749: 26.1: simple.el: command-execute docstring [PATCH]
Date: Thu, 1 Oct 2020 13:48:47 -0400 [thread overview]
Message-ID: <20201001174847.kpys3ndz2kwmljs5@E15-2016.optimum.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 256 bytes --]
The docstring was using a non-standard form of reference for function
'this-command-keys', so function describe-command was unable to
auto-magically construct a link to it.
--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0
[-- Attachment #2: simple.patch --]
[-- Type: text/x-diff, Size: 1453 bytes --]
diff --git a/simple.el b/simple.el
index 9483170..a03363f 100644
--- a/simple.el
+++ b/simple.el
@@ -1814,13 +1814,14 @@ invoking, give a prefix argument to `execute-extended-command'."
;; BEWARE: Called directly from the C code.
"Execute CMD as an editor command.
CMD must be a symbol that satisfies the `commandp' predicate.
-Optional second arg RECORD-FLAG non-nil
-means unconditionally put this command in the variable `command-history'.
-Otherwise, that is done only if an arg is read using the minibuffer.
-The argument KEYS specifies the value to use instead of (this-command-keys)
-when reading the arguments; if it is nil, (this-command-keys) is used.
-The argument SPECIAL, if non-nil, means that this command is executing
-a special event, so ignore the prefix argument and don't clear it."
+Optional second arg RECORD-FLAG non-nil means unconditionally put
+this command in the variable `command-history'. Otherwise, that
+is done only if an arg is read using the minibuffer. The argument
+KEYS specifies the value to use instead of the return value of
+function `this-command-keys' when reading the arguments; if it is
+nil, `this-command-keys' is used. The argument SPECIAL, if
+non-nil, means that this command is executing a special event, so
+ignore the prefix argument and don't clear it."
(setq debug-on-next-call nil)
(let ((prefixarg (unless special
;; FIXME: This should probably be done around
next reply other threads:[~2020-10-01 17:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 17:48 Boruch Baum [this message]
2020-10-01 18:26 ` bug#43749: 26.1: simple.el: command-execute docstring [PATCH] Lars Ingebrigtsen
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=20201001174847.kpys3ndz2kwmljs5@E15-2016.optimum.net \
--to=boruch_baum@gmx.com \
--cc=43749@debbugs.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.