all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Barry Margolin <barmar@alum.mit.edu>
To: help-gnu-emacs@gnu.org
Subject: Re: About traditional Lisp primitives
Date: Wed, 06 Mar 2013 05:39:18 -0500	[thread overview]
Message-ID: <barmar-F1D9DE.05391806032013@news.eternal-september.org> (raw)
In-Reply-To: mailman.21530.1362559820.855.help-gnu-emacs@gnu.org

In article <mailman.21530.1362559820.855.help-gnu-emacs@gnu.org>,
 Xue Fuqiao <xfq.free@gmail.com> wrote:

> In (info "(elisp) Coding Conventions"):
> 
>       This recommendation applies even to names for traditional Lisp
>       primitives that are not primitives in Emacs Lisp--such as
>       `copy-list'.
> 
> I don't know what "traditional Lisp primitives" means here.  What are 
> the differences between traditional Lisp primitives and primitives in 
> Emacs Lisp?  Are they implemented in C?

What they mean is a function in a traditional Lisp dialect (e.g. Common 
Lisp or Maclisp) that doesn't exist in Emacs Lisp.  If you want to use 
such a function in your own package, you need to write it yourself -- 
and the recommendation is that you personalize it with a prefix, so you 
don't conflict with another package that has a similar need.

-- 
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***


       reply	other threads:[~2013-03-06 10:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.21530.1362559820.855.help-gnu-emacs@gnu.org>
2013-03-06 10:39 ` Barry Margolin [this message]
2013-03-07 10:54   ` gvfs-open in eshell/shell-command Phillip Lord
2013-03-12 13:48     ` Michael Albinus
     [not found]     ` <mailman.21924.1363096112.855.help-gnu-emacs@gnu.org>
2013-03-14 17:42       ` politza
2013-03-18 12:19         ` Phillip Lord
2013-03-06  8:50 About traditional Lisp primitives Xue Fuqiao

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=barmar-F1D9DE.05391806032013@news.eternal-september.org \
    --to=barmar@alum.mit.edu \
    --cc=help-gnu-emacs@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.