From: "Štěpán Němec" <stepnem@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 6591@debbugs.gnu.org, Richard Stallman <rms@gnu.org>
Subject: bug#6591: 24.0.50; incorrect doc for `catch'
Date: Sun, 11 Jul 2010 10:14:47 +0200 [thread overview]
Message-ID: <877hl2a0zs.fsf@gmail.com> (raw)
In-Reply-To: <83sk3qv922.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 11 Jul 2010 09:15:01 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: "Drew Adams" <drew.adams@oracle.com>
>> Cc: <6591@debbugs.gnu.org>
>> Date: Sat, 10 Jul 2010 21:21:04 -0700
>>
>> If you now say that you are open to looking
>> for another syntax to use, then I would return to my initial suggestion
> (but I
>> won't argue that it is the only good approach): use `...' to mean
> repetitions of
>> whatever it follows, in this case a sexp, and thus write (catch TAG
> FORM...).
>> Introducing a grouping syntax operator (e.g. braces: {}), so the scope of
> the
>> ellipsis can be controlled - e.g. (A B {C D}... E...) meaning that C D
> repeats
>> and E repeats.
>
> Using FORM... is okay, but will need more extensive changes, so I'd
> rather not do it. I'd like to simply remove the dots after BODY, and
> explain in the text that BODY can consist of one or more forms.
>
> Does anyone see any reason why keeping the dots in BODY... will have
> some didactical importance? Richard? Stefan? Yidong?
Well, just look at `when' -- ISTM it has the very same "problem" as
discussed here. And it's probably not the only one/two.
Štěpán
next prev parent reply other threads:[~2010-07-11 8:14 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 15:52 bug#6591: 24.0.50; incorrect doc for `catch' Drew Adams
2010-07-09 17:48 ` Eli Zaretskii
2010-07-09 19:36 ` Drew Adams
2010-07-10 7:48 ` Eli Zaretskii
2010-07-10 14:14 ` Drew Adams
2010-07-10 14:38 ` Eli Zaretskii
2010-07-10 15:44 ` Drew Adams
2010-07-10 15:55 ` Eli Zaretskii
2010-07-11 4:21 ` Drew Adams
2010-07-11 6:15 ` Eli Zaretskii
2010-07-11 8:14 ` Štěpán Němec [this message]
2010-07-11 9:22 ` Eli Zaretskii
2010-07-11 10:59 ` Štěpán Němec
2010-07-11 13:23 ` Eli Zaretskii
2010-07-11 13:44 ` Štěpán Němec
2010-07-11 14:00 ` Eli Zaretskii
2010-07-11 15:26 ` Andreas Schwab
2010-07-11 15:33 ` Drew Adams
2010-07-11 17:22 ` Eli Zaretskii
[not found] ` <mailman.11.1278862210.6344.bug-gnu-emacs@gnu.org>
2010-07-11 22:36 ` Tim X
[not found] ` <mailman.2.1278856813.6344.bug-gnu-emacs@gnu.org>
2010-07-11 22:34 ` Tim X
2010-12-08 15:52 ` Drew Adams
2010-12-20 12:25 ` Chong Yidong
2010-07-11 15:33 ` Drew Adams
2010-07-11 17:25 ` Eli Zaretskii
2010-07-11 16:33 ` Chong Yidong
2010-07-11 16:52 ` Drew Adams
2010-07-11 17:13 ` Chong Yidong
2010-07-11 17:58 ` Drew Adams
2010-07-11 18:14 ` Andreas Schwab
2010-07-11 19:10 ` Drew Adams
2010-07-11 19:40 ` Andreas Schwab
2010-07-11 20:07 ` Drew Adams
2010-07-11 21:22 ` Andreas Schwab
2010-07-11 21:42 ` Chong Yidong
2010-07-11 21:44 ` Drew Adams
2010-07-12 8:43 ` Andreas Schwab
2010-07-12 14:56 ` Drew Adams
2010-07-12 15:26 ` Andreas Schwab
2010-07-12 16:01 ` Drew Adams
2010-07-12 16:11 ` Andreas Schwab
2010-07-12 16:31 ` Drew Adams
2010-07-12 16:36 ` Andreas Schwab
2010-07-12 16:50 ` Drew Adams
2010-07-12 18:14 ` Andreas Schwab
2010-07-12 18:35 ` Drew Adams
2010-07-12 18:41 ` Andreas Schwab
2010-07-12 18:49 ` Drew Adams
2010-07-12 17:02 ` Eli Zaretskii
2010-07-12 18:30 ` Drew Adams
2010-07-10 5:44 ` MON KEY
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=877hl2a0zs.fsf@gmail.com \
--to=stepnem@gmail.com \
--cc=6591@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rms@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.