all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: bug-gnu-emacs@gnu.org, gnu-emacs-hacker@jovi.net
Subject: Re: color-gray-p
Date: Sun, 22 Aug 2004 13:10:14 -0500 (CDT)	[thread overview]
Message-ID: <200408221810.i7MIAEu07678@raven.dms.auburn.edu> (raw)
In-Reply-To: <200408221702.i7MH2qML061174@grant.org> (Devon@jovi.net)

Devon Sean McCullough wrote:

   PS:  What about CHECK_* and other mysteries?
   Has anyone written this down or must I go to
   a certain tavern and buy RMS a beer to learn
   such arcana?

As far as I know, the only documentation about the Emacs C code is
contained in Info node `(elisp)GNU Emacs Internals' or Appendix E, GNU
Emacs Internals, in the hardcopy Elisp manual.

This is _not at all_ a comprehensive documentation.  As far as I know,
to learn the Emacs C code, you essentially have to struggle through the
source code.

In as far as the second argument to the CHECK_* functions is
concerned, it seems to have been removed in current CVS.  It
definitely has been removed for CHECK_FRAME.

Sincerely,

Luc.

  parent reply	other threads:[~2004-08-22 18:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-22 16:36 color-gray-p Luc Teirlinck
2004-08-22 17:02 ` color-gray-p Devon
2004-08-22 17:34   ` color-gray-p Luc Teirlinck
2004-08-22 17:41   ` color-gray-p Luc Teirlinck
2004-08-22 18:14     ` color-gray-p Devon
2004-08-22 18:21     ` color-gray-p Devon
2004-08-22 18:37       ` color-gray-p Luc Teirlinck
2004-08-22 18:58         ` color-gray-p Devon
2004-08-22 19:07           ` color-gray-p Luc Teirlinck
2004-08-22 21:33           ` color-gray-p Luc Teirlinck
2004-08-22 18:10   ` Luc Teirlinck [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-22  5:36 color-gray-p Devon Sean McCullough

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=200408221810.i7MIAEu07678@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=gnu-emacs-hacker@jovi.net \
    /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.