From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 13292-done@debbugs.gnu.org
Subject: bug#13292: 24.3.50; wrong sytax description in (elisp) Case Tables
Date: Fri, 28 Dec 2012 20:30:34 +0200 [thread overview]
Message-ID: <83623mm3lh.fsf@gnu.org> (raw)
In-Reply-To: <E96C5DF8025F4EFB9B2F082621D0E9EE@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <13292@debbugs.gnu.org>
> Date: Fri, 28 Dec 2012 08:57:28 -0800
>
> > > The parameters should be uppercase everywhere.
> >
> > They never were. This is how Info works.
> > Closing.
>
> In that case, there are bugs in the other direction, in other nodes of the
> manual - nodes that use uppercase for parameters.
>
> For example:
>
> `A Sample Function Description' - `count-loop'
> `Syntax Table Functions' - `with-syntax-table'
> `Using Lexical Binding' - `special-variable-p'
> `Syntax Table Internals' - `string-to-syntax'
> `Declare Form' - `declare'
>
> Note that `A Sample Function Description' is the very place where we explain the
> syntax convention and give an example of it. Not a good place to set a bad
> example.
It's not bad. This is done on purpose, see the Texinfo sources, which
use @var in this case.
> Reopening. There is clearly some cleanup to be done.
Reclosing. Please stop this ridicule.
next prev parent reply other threads:[~2012-12-28 18:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-28 15:26 bug#13292: 24.3.50; wrong sytax description in (elisp) Case Tables Drew Adams
2012-12-28 15:30 ` Drew Adams
2012-12-28 16:39 ` Eli Zaretskii
2012-12-28 16:57 ` Drew Adams
2012-12-28 18:30 ` Eli Zaretskii [this message]
2012-12-28 18:46 ` Drew Adams
2012-12-29 0:21 ` Wolfgang Jenkner
2012-12-29 8:30 ` Eli Zaretskii
2012-12-29 15:48 ` Wolfgang Jenkner
2012-12-29 16:17 ` 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=83623mm3lh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=13292-done@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).