unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: uzibalqa <uzibalqa@proton.me>,
	uzibalqa via Users list for the GNU Emacs text editor
	<help-gnu-emacs@gnu.org>
Subject: RE: [External] : menu-item uses no dot period before item-property-list in examples
Date: Mon, 17 Jul 2023 00:52:29 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488F7C13B085C0C35F7768CF33BA@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <TG5ja9QGoiohWHCHW1-vC7NS0mLfSB-EtpqryFFi8PkxqKKQpuS2dXahYvJON_LTCK1bxboqI6het4GebHLB1qqCLDsgbNcaips2UDD1KOg=@proton.me>

> > Have read about
> 
>  (menu-item item-name real-binding . item-property-list)
>
> but when things actually get implemented there exist no dot period
> before 'item-property-list'.
> 
>  (define-key global-map
>    [menu-bar mcp-topm daphne-subm entry-sweep]
>      '(menu-item "Entry Sweep" gilgamesh-entry-sweep
>         :help "Entry Sweep"))

Yes, there is.  And you've been told before
that (a . (b c)) is the same as (a b c).

For simplicity, Lisp _printing_ removes the
dot and parens: . (...).  This is standard
Lisp syntax convenience: we write (a b c)
instead of (a . (b . (c . nil))).  That's
all there is to it.

And you've asked this before, and you've
been pointed to the Elisp doc, which
explains all of this in detail, even with
diagrams and examples.

Please, Ask Emacs.  Many people, over many
years, have gone to the trouble of writing
good, clear help and doc.

And you can find the same thing outside of
Emacs, in any number of Lisp introductions.

Help yourself.

  reply	other threads:[~2023-07-17  0:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-16 22:34 menu-item uses no dot period before item-property-list in examples uzibalqa
2023-07-17  0:52 ` Drew Adams [this message]
2023-07-17  1:07   ` [External] : " Emanuel Berg
2023-07-17 15:05     ` Drew Adams
2023-07-17  1:17   ` uzibalqa
2023-07-17 15:10     ` Drew Adams
2023-07-17 15:43       ` uzibalqa
2023-07-17 16:36         ` Drew Adams
2023-07-17 16:56           ` uzibalqa
2023-07-17 17:25             ` uzibalqa
2023-07-17 19:07               ` uzibalqa
2023-07-17 19:26               ` Drew Adams

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=SJ0PR10MB5488F7C13B085C0C35F7768CF33BA@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=uzibalqa@proton.me \
    /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).