From: Rob Browning <rlb@defaultvalue.org>
To: guile-devel@gnu.org
Subject: [PATCH v2 6/6] define-meta-command: mention effects of a missing category
Date: Wed, 3 Jul 2024 12:02:15 -0500 [thread overview]
Message-ID: <20240703170335.1003252-7-rlb@defaultvalue.org> (raw)
In-Reply-To: <20240703170335.1003252-1-rlb@defaultvalue.org>
module/system/repl/command.scm: add comment.
---
module/system/repl/command.scm | 2 ++
1 file changed, 2 insertions(+)
diff --git a/module/system/repl/command.scm b/module/system/repl/command.scm
index ca7450610..8b0422dbd 100644
--- a/module/system/repl/command.scm
+++ b/module/system/repl/command.scm
@@ -235,6 +235,8 @@
(define-meta-command ((name category) repl () . datums)
docstring b0 b1 ...))
+ ;; These cases (with category #f) will only produce functional
+ ;; commands if the name is already in the *command-table*.
((_ (name repl (expression0 ...) . datums) docstring b0 b1 ...)
(define-meta-command ((name #f) repl (expression0 ...) . datums)
docstring b0 b1 ...))
--
2.43.0
next prev parent reply other threads:[~2024-07-03 17:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 17:02 [PATCH v2 0/6] A handful of post 3.0.10 fixups Rob Browning
2024-07-03 17:02 ` [PATCH v2 1/6] Ensure GUILE-VERSION changes propagate to .version and Makefiles Rob Browning
2024-07-03 17:02 ` [PATCH v2 2/6] Ensure tests have guile-procedures.txt Rob Browning
2024-07-03 17:02 ` [PATCH v2 3/6] test-hashing: support 32-bit Rob Browning
2024-07-13 0:32 ` Rob Browning
2024-07-03 17:02 ` [PATCH v2 4/6] scm_i_utf8_string_hash: don't overrun when len is zero Rob Browning
2024-07-03 17:02 ` [PATCH v2 5/6] scm_i_utf8_string_hash: optimize ASCII Rob Browning
2024-07-03 17:02 ` Rob Browning [this message]
2024-07-13 0:32 ` [PATCH v2 6/6] define-meta-command: mention effects of a missing category Rob Browning
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240703170335.1003252-7-rlb@defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).