From: "Drew Adams" <drew.adams@oracle.com>
To: "'Wolfgang Jenkner'" <wjenkner@inode.at>,
"'Eli Zaretskii'" <eliz@gnu.org>
Cc: 13292@debbugs.gnu.org
Subject: bug#13292: 24.3.50; wrong sytax description in (elisp) Case Tables
Date: Sat, 29 Dec 2012 08:17:50 -0800 [thread overview]
Message-ID: <6AF653A28D414296BCE16FDA3EE50DE7@us.oracle.com> (raw)
In-Reply-To: <85623kc0yu.fsf@iznogoud.viz>
> I meant a time closer to when the elisp manual was written, viz.
> http://ftp.gnu.org/old-gnu/emacs/elisp-manual-20-2.5.tar.gz
> has (in the node we are talking about: A Sample Function Description)
>
> @defun foo integer1 &optional integer2 &rest integers
> but the formatted manual included in that tarball has
> - Function: foo INTEGER1 &optional INTEGER2 &rest INTEGERS
>
> That's the reason why Drew's report rang a bell: I remembered
> that years ago I had become aware of this change from upper-case
> to lower-case at some point.
Yes, in Emacs 20 parameters were uppercase - more readable, BTW.
I don't have an Emacs 21 Elisp (Info) manual. My guess would be that this
regression (intentional, no doubt) was introduced in Emacs 22.
The current bug is that the usage is not consistent - that's the point.
Parameters should either be always uppercase or always lowercase. They are
instead sometimes all uppercase, sometimes all lowercase.
prev parent reply other threads:[~2012-12-29 16:17 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
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 [this message]
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=6AF653A28D414296BCE16FDA3EE50DE7@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=13292@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=wjenkner@inode.at \
/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).