From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Documentation of ‘define-alternatives’
Date: Tue, 15 Aug 2023 15:53:22 +0300 [thread overview]
Message-ID: <83il9ga2m5.fsf@gnu.org> (raw)
In-Reply-To: <PH0PR11MB74707A306038318A81F5639BD714A@PH0PR11MB7470.namprd11.prod.outlook.com> (message from Shynur Xie on Tue, 15 Aug 2023 10:16:36 +0000)
> From: Shynur Xie <one.last.kiss@outlook.com>
> CC: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
> Date: Tue, 15 Aug 2023 10:16:36 +0000
> msip_labels:
>
> > Macro: define-alternatives command &rest customizations
> >
> > ... ...
> >
> > If CUSTOMIZATIONS is non-‘nil’, it should consist of ... and values
> > to add to the declaration of ‘COMMAND-alternatives’.
>
> Does it mean that user can initialize ‘COMMAND-alternatives’ by
> putting the expected values in the ‘(define-alternative COMMAND ...)’
> form?
No. The text says:
If CUSTOMIZATIONS is non-‘nil’, it should consist of alternating
‘defcustom’ keywords (typically ‘:group’ and ‘:version’) and values
to add to the declaration of ‘COMMAND-alternatives’.
So CUSTOMIZATIONS is for adding keyword/value pairs we usually use in
a defcustom (since this macro creates a defcustom).
next prev parent reply other threads:[~2023-08-15 12:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 10:16 Documentation of ‘define-alternatives’ Shynur Xie
2023-08-15 12:53 ` Eli Zaretskii [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-14 12:34 Shynur Xie
2023-08-14 18:00 ` Eli Zaretskii
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83il9ga2m5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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).