unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Tassilo Horn <tsdh@gnu.org>,
	Heime via Users list for the GNU Emacs text editor
	<help-gnu-emacs@gnu.org>
Cc: Heime <heimeborgia@protonmail.com>
Subject: RE: [External] : Re: Keywords as function arguments for control flow
Date: Fri, 29 Nov 2024 21:06:06 +0000	[thread overview]
Message-ID: <DS7PR10MB5232AE4A77313A75324F77A2F32A2@DS7PR10MB5232.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87y1125zre.fsf@gnu.org>

> Your example uses symbols not keywords.

And one can Ask Emacs.  This is what the Elisp manual
has to say about keywords:

  A symbol whose name starts with a colon (':') is
  called a keyword symbol. These symbols automatically
  act as constants, and are normally used only by
  comparing an unknown symbol with a few specific
  alternatives. See "Variables that Never Change".

https://www.gnu.org/software/emacs/manual/html_node/elisp/Symbol-Type.html

That "Variables that Never Change" link takes you here:

https://www.gnu.org/software/emacs/manual/html_node/elisp/Constant-Variables.html

where it says this:

  Function: keywordp object ¶
  function returns t if object is a symbol whose
  name starts with ':', interned in the standard
  obarray, and returns nil otherwise.



  reply	other threads:[~2024-11-29 21:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-28 15:21 Keywords as function arguments for control flow Heime via Users list for the GNU Emacs text editor
2024-11-29  6:18 ` Tassilo Horn
2024-11-29 21:06   ` Drew Adams [this message]
2024-11-29 21:26     ` [External] : " Heime via Users list for the GNU Emacs text editor
2024-11-30 11:47 ` Jean Louis
2024-11-30 11:55   ` Heime via Users list for the GNU Emacs text editor
2024-11-30 14:37     ` Jean Louis

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=DS7PR10MB5232AE4A77313A75324F77A2F32A2@DS7PR10MB5232.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=heimeborgia@protonmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=tsdh@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).