unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: <rms@gnu.org>
Cc: 1381@emacsbugs.donarmstrong.com,
	bug-submit-list@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: Fri, 21 Nov 2008 08:17:55 -0800	[thread overview]
Message-ID: <003601c94bf4$b6921460$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <E1L3XlI-0002QC-MN@fencepost.gnu.org>

>     OK, that's one thing. But my question was whether these 
>     shouldn't simply be treated as normal Emacs terms - just
>     like cons, buffer, symbol, and frame, after
>     they have been introduced (defined).
> 
> The reason for using @sc on car and cdr is that they are acronyms.
> Those other terms are not acronyms.

I see. That makes sense, I guess, though I'm not sure it's important. (If we
always stuck to that convention, then we might always write "EMACS" or "EMacS",
not "Emacs". ;-))

FWIW, this is what Wikipedia says about the orthography of acronyms:

 The most common capitalization scheme seen with acronyms
 and initialisms is all-uppercase (all-caps), except for
 those few that have linguistically taken on an identity
 as regular words, with the acronymous etymology of the
 words fading into the background of common knowledge, such
 as has occurred with the words scuba, laser, and radar.

That's the argument I'd make here: "car" and "cdr" have linguistically taken on
an identity as regular words. The machine registers that were at the orgins of
these terms are incidental to the current meanings, and knowledge of that
historical relation is anecdotal.

I see "cdr" (for Lispians) the same way I see "radar". We should encourage
thinking of these as common terms, rather than as acronyms about machine
registers. Rather than facilitating understanding, I think it gets in the way of
understanding (and readability) to write "RADAR" and "CDR".









  reply	other threads:[~2008-11-21 16:17 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
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 [this message]
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='003601c94bf4$b6921460$0200a8c0@us.oracle.com' \
    --to=drew.adams@oracle.com \
    --cc=1381@emacsbugs.donarmstrong.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=bug-submit-list@donarmstrong.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).