From: Bill Freeman <ke1g.nh@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Subject: bug#15558: [gnu.org #859332] Error in elisp on line documentation
Date: Tue, 8 Oct 2013 13:32:47 -0400 [thread overview]
Message-ID: <CAB+Aj0ufTQ_iBpepXWecpVoYw9mMNpzc_t8LPU7QwvZWPciEFQ@mail.gmail.com> (raw)
In-Reply-To: <ujpprfu47f.fsf@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]
Yes, thanks, I see that now. (And I thought I was reading carefully.)
But might I suggest that the line:
If every condition evaluates to nil, so that every clause fails,
condreturns
nil.
be placed after the line:
Then, if condition is non-nil when tested, the value of
conditionbecomes the value of the
cond form.
Bill
On Tue, Oct 8, 2013 at 12:17 PM, Glenn Morris <rgm@gnu.org> wrote:
>
> "Robert Musial via RT" wrote:
>
> >> Yet it is perfectly legal for a clause to have no body-forms, only a
> >> condition.
> [...]
> >> The current text actually leaves the value undefined for this case. It
> is
> >> a useful case, and should be correctly documented.
>
> It is documented (if a little clunkily):
>
> A clause may also look like this:
>
> (condition)
>
> Then, if condition is non-nil when tested, the value of condition
> becomes the value of the cond form.
>
>
> PS: Please report Emacs documentation issues via M-x report-emacs-bug
> (or mail to bug-gnu-emacs@gnu.org) rather than emailing GNU webmasters.
>
[-- Attachment #2: Type: text/html, Size: 1688 bytes --]
next prev parent reply other threads:[~2013-10-08 17:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <RT-Ticket-859332@rt.gnu.org>
[not found] ` <CAB+Aj0vReBpxZx7C31hXZHB3_K=rzSbKOR5BtUiZ2bv9PuSw=Q@mail.gmail.com>
2013-10-07 23:32 ` bug#15558: [gnu.org #859332] Error in elisp on line documentation Robert Musial via RT
2013-10-08 16:17 ` Glenn Morris
2013-10-08 17:32 ` Bill Freeman [this message]
2013-10-09 17:19 ` Glenn Morris
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAB+Aj0ufTQ_iBpepXWecpVoYw9mMNpzc_t8LPU7QwvZWPciEFQ@mail.gmail.com \
--to=ke1g.nh@gmail.com \
--cc=rgm@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.