From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>, Richard Stallman <rms@gnu.org>
Cc: 1381@emacsbugs.donarmstrong.com, bug-gnu-emacs@gnu.org,
emacs-pretest-bug@gnu.org
Subject: bug#1381: 23.0.60; capitalization of car and cdr in the doc
Date: Wed, 19 Nov 2008 22:05:29 +0200 [thread overview]
Message-ID: <ud4grlbw6.fsf@gnu.org> (raw)
In-Reply-To: <004b01c94a7f$98491c40$c2b22382@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <emacs-pretest-bug@gnu.org>, <bug-gnu-emacs@gnu.org>
> Date: Wed, 19 Nov 2008 11:46:59 -0800
>
> > > I'd suggest not making CAR and CDR uppercase.
> >
> > They are not in uppercase, they are in "small caps" typeface (@sc in
> > Texinfo markup). You are reading the Info manual, where @sc is
> > rendered as uppercase, but in the printed manual it looks differently.
>
> I see. But is that normal for Emacs terminology? See what I wrote about cons,
> buffer, window, frame, symbol, etc.
>
> If this is intentional, feel free to close the bug. It seems odd to me, though -
> to me, these are normal Emacs terms.
These were in the manual since a long time ago, so I'll let Richard
answer this.
next prev parent reply other threads:[~2008-11-19 20:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r5jw5ly6.fsf@stupidchicken.com>
2008-11-19 18:22 ` bug#1381: 23.0.60; capitalization of car and cdr in the doc Drew Adams
2008-11-19 19:34 ` Eli Zaretskii
2008-11-19 19:46 ` Drew Adams
2008-11-19 20:05 ` Eli Zaretskii [this message]
2008-11-20 14:26 ` Richard M. Stallman
2008-11-20 16:22 ` Drew Adams
2008-11-21 15:17 ` Richard M. Stallman
2008-11-21 16:17 ` Drew Adams
2008-11-20 20:23 ` Eli Zaretskii
2008-11-20 20:28 ` Drew Adams
2008-11-20 20:43 ` Eli Zaretskii
2008-11-20 20:57 ` Drew Adams
2008-11-21 7:44 ` Yavor Doganov
2008-11-21 15:28 ` Drew Adams
[not found] ` <handler.1381.C.127740381719306.notifdonectrl.7@debbugs.gnu.org>
2010-06-24 18:39 ` bug#1381: acknowledged by developer (close 1382) 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=ud4grlbw6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=1381@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=drew.adams@oracle.com \
--cc=emacs-pretest-bug@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 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).