From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: emacs-devel@gnu.org
Subject: Re: [d.love@dl.ac.uk: Re: privateColormap X resource]
Date: Tue, 29 Oct 2002 09:26:29 -0500 [thread overview]
Message-ID: <200210291426.g9TEQTF15534@rum.cs.yale.edu> (raw)
In-Reply-To: E186FR8-00075z-00@fencepost.gnu.org
> Can someone please try testing whether the privateColormap X resource
> works in Emacs? Here is a suggestion for how to test that;
> I would not know how to fill in the details and really do it,
> but maybe some of you know.
This suggestion won't work because Emacs (rightly so from my point of
view) does not automatically switch to a private colormap when it
runs out of colors. Instead it uses the closest color available,
such that the result is not quite right but is not psychedelic either.
But a long time ago Gerd said (while tracking down a
color-reference-count-overflow bug in XFree triggered by Emacs):
> In the course of cleaning up the color code a bit, I'm now setting the
> XtNcolormap resource of the shell widget. I think the menu bar should
> inherit that colormap. An easy way to check this if it does is to run
> Emacs with a private colormap. Just add the resource
>
> Emacs.privateColormap: true
There's also Emacs.visualClass.
Stefan
> ------- Start of forwarded message -------
> Envelope-to: rms@gnu.org
> Delivery-date: Sun, 27 Oct 2002 07:42:31 -0500
> To: rms@gnu.org
> Subject: Re: privateColormap X resource
> From: Dave Love <d.love@dl.ac.uk>
> Date: 27 Oct 2002 12:42:21 +0000
> In-Reply-To: <E184FfQ-0007ZT-00@fencepost.gnu.org>
> X-Spam-Status: No, hits=-9.3 required=5.0
> tests=IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,
> USER_AGENT
> version=2.41
> X-Spam-Level:
>
> You wrote:
>
> > I would run it in an 8-bit session, eat up the colourmap with Netrape
> > or something, and then see if Emacs gets it own (with resulting
> > psychedelics when you switch window focus). There may be a better
> > way.
> >
> > Can you write a precise recipe for doing this?
>
> I don't think I can do much better. I think it would be clear to
> people using 8-bit displays.
> ------- End of forwarded message -------
>
>
> _______________________________________________
> Emacs-devel mailing list
> Emacs-devel@gnu.org
> http://mail.gnu.org/mailman/listinfo/emacs-devel
>
next prev parent reply other threads:[~2002-10-29 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-28 19:20 [d.love@dl.ac.uk: Re: privateColormap X resource] Richard Stallman
2002-10-28 21:28 ` Jan D.
2002-10-29 11:29 ` Richard Stallman
2002-10-29 14:26 ` Stefan Monnier [this message]
2002-10-30 17:17 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2002-10-29 3:01 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
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=200210291426.g9TEQTF15534@rum.cs.yale.edu \
--to=monnier+gnu/emacs@rum.cs.yale.edu \
--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 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).