all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: drew.adams@oracle.com, emacs-devel@gnu.org
Subject: Re: read-file-name-predicate
Date: Wed, 07 Mar 2007 22:16:28 -0500	[thread overview]
Message-ID: <E1HP97E-00088b-R4@fencepost.gnu.org> (raw)
In-Reply-To: <ud53lngly.fsf@gnu.org> (message from Eli Zaretskii on Wed, 07 Mar 2007 18:49:45 +0200)

    I don't know if in this specific case the variable is a left-over from
    something we don't need anymore; I hope Kim will answer that.  But
    your general point -- that Lisp variables should all be documented to
    the degree that every Emacs user should understand -- is not valid (as
    a generality).

That is correct.  Some C features need Lisp variables (and Lisp
primitive functions) that are internal and we do not need to document
them.  In some cases we do not WANT Lisp programmers to use these
internal functions and variables.

  parent reply	other threads:[~2007-03-08  3:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-07  6:00 read-file-name-predicate Drew Adams
2007-03-07 14:39 ` read-file-name-predicate Stefan Monnier
2007-03-07 15:11   ` read-file-name-predicate Juanma Barranquero
2007-03-07 16:31     ` read-file-name-predicate Drew Adams
2007-03-07 16:49       ` read-file-name-predicate Eli Zaretskii
2007-03-07 17:14         ` read-file-name-predicate Drew Adams
2007-03-08  4:19           ` read-file-name-predicate Eli Zaretskii
2007-03-08  3:16         ` Richard Stallman [this message]
2007-03-08 11:16         ` read-file-name-predicate Kim F. Storm
2007-03-08  3:16       ` read-file-name-predicate Richard Stallman
2007-03-07 17:26 ` read-file-name-predicate Richard Stallman
2007-03-07 17:35   ` read-file-name-predicate Drew Adams
2007-03-08 17:40     ` read-file-name-predicate Richard Stallman

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=E1HP97E-00088b-R4@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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.