From: "zhangjg" <jinguozhang@qq.com>
To: 26635@debbugs.gnu.org
Subject: bug#26635: 25.1; elisp docs bug
Date: Mon, 24 Apr 2017 11:35:55 +0800 [thread overview]
Message-ID: <tencent_743563DE3C4CC6881AAE2183@qq.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 385 bytes --]
The elisp docs in the session "12.1 What Is a Function?" distinction the funtion and the function-like object.
But in some pages, some function-like object is give as a function.
For example:
In session "3.4 Comparison of Numbers", "=" is a set to a "function" but, in fact it a "special forms".
In the same resason, I think, "<", "<=", ">", ">=" also should be "special forms".
[-- Attachment #2: Type: text/html, Size: 415 bytes --]
next reply other threads:[~2017-04-24 3:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 3:35 zhangjg [this message]
2017-04-24 9:59 ` bug#26635: 25.1; elisp docs bug Andreas Schwab
2017-04-24 10:31 ` bug#26635: 回复： " zhangjg
2017-04-24 10:50 ` Andreas Schwab
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=tencent_743563DE3C4CC6881AAE2183@qq.com \
--to=jinguozhang@qq.com \
--cc=26635@debbugs.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).