From: Drew Adams <drew.adams@oracle.com>
To: uzibalqa <uzibalqa@proton.me>
Cc: 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 15:10:45 +0000 [thread overview]
Message-ID: <SJ0PR10MB54882719C259F972298AD89EF33BA@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <RKS9ul0pWItO0WyPZO_GKoh3aVag-zL5JSEKq-wRgZsS_NnD1X6mXLTw0w-_KyLQ94VxA6UlHT1OFiR-J05sVp-iPSgZ_WRwnQDvKr4Vdms=@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.
>
> So why bother users in the manual why that is never actually used.
> (menu-item item-name real-binding item-property-list)
I hope you meant this, which is not the same thing:
(menu-item item-name real-binding
. item-property-list)
item-property-list is not an _element_ of the
overall list. It's "spliced" into that list,
as its _tail_.
What "bother" are you referring to?
item-property-list is a list. That's all.
Lisp users like/need? to understand dotted
list notation, and its abbreviated read and
print notation, i.e., the fact that
(a b c) = (a . (b . (c . nil)))
If you intend to use Elisp, then you should
intend to read about and understand its read
and print syntax. And if you use Elisp to
create menus then you should intend to read
and understand a syntax description such as
(menu-item item-name real-binding
. item-property-list)
> > 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.
>
> That's your assertion. Bothering us with jargon that never gets used is
> just being silly to those who do not have time for nonsense intended only
> for general language interest rather than practicality.
What "jargon that never gets used" are you referring to?
Apparently what you call "bother" is what Emacs
offers as doc to try to _help_ its users.
Who is bothering whom, with your "Help Me!!!??
I'm drowning!!!?!!" pleas for help? Do you ever
wonder why people - even very patient people -
give up on you after a while for not trying to
_help yourself_ a bit?
> The dot should be removed from the documentation
> and have
^^^^^^^^ ?
What dot, where? And have what? Is it possible
for you to see that you just toss half-articulated
demands and pleas over the wall and then expect
help and mind-reading?
Maybe try ChatGPT instead?
> > And you can find the same thing outside of
> > Emacs, in any number of Lisp introductions.
> >
> > Help yourself.
next prev parent reply other threads:[~2023-07-17 15:10 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 ` [External] : " Drew Adams
2023-07-17 1:07 ` Emanuel Berg
2023-07-17 15:05 ` Drew Adams
2023-07-17 1:17 ` uzibalqa
2023-07-17 15:10 ` Drew Adams [this message]
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=SJ0PR10MB54882719C259F972298AD89EF33BA@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).