From: Devon@jovi.net
Cc: bug-gnu-emacs@gnu.org, gnu-emacs-hacker@jovi.net
Subject: Re: color-gray-p
Date: Sun, 22 Aug 2004 13:02:52 -0400 (EDT) [thread overview]
Message-ID: <200408221702.i7MH2qML061174@grant.org> (raw)
In-Reply-To: <200408221636.i7MGah907488@raven.dms.auburn.edu> (message from Luc Teirlinck on Sun, 22 Aug 2004 11:36:44 -0500 (CDT))
Thanks. Where do I get Emacs CVS? I know how to FTP but I understand
you have to undergo secret initiation rites at Unix Summer Camp before
CVS will deign to fetch you any software.
Peace
--Devon
/~\
\ / Health Care
X not warfare
/ \
The Voting Machine Industry
has a surprise in store:
Kevin Mitnick in 2004!
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?
Date: Sun, 22 Aug 2004 11:36:44 -0500 (CDT)
From: Luc Teirlinck <teirllm@dms.auburn.edu>
To: Devon Sean McCullough <gnu-emacs-hacker@jovi.net>
CC: bug-gnu-emacs@gnu.org
Subject: color-gray-p
Devon Sean McCullough wrote:
(color-gray-p "gray") signals (wrong-type-argument framep nil)
Functions `color-gray-p' and `color-supported-p'
do not work as documented.
These bugs occurred in 21.3, but they are fixed in Emacs CVS and,
hence, will be fixed in 21.4 (not yet released).
Sincerely,
Luc.
next prev parent reply other threads:[~2004-08-22 17:02 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 ` Devon [this message]
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 ` color-gray-p Luc Teirlinck
-- 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
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=200408221702.i7MH2qML061174@grant.org \
--to=devon@jovi.net \
--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 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).