From: Per Abrahamsen <abraham@dina.kvl.dk>
Cc: ding@gnus.org, emacs-custom@sunsite.auc.dk
Subject: Re: Functional complaint, customize library
Date: 07 Apr 1998 17:30:04 +0200 [thread overview]
Message-ID: <rjhg45fy4j.fsf@zuse.+dina.kvl.dk> (raw)
In-Reply-To: <vxk7m51aevi.fsf@pocari-sweat.jprc.com>
The themes idea has come up several times. It does require some
careful conciderations if you want to do it right, but not a huge
project either. Especially compared to the benefits. Nobody has
volunteered for doing the work, though.
I find the other idea totally unfascinating.
Discussion about themes (and that other thing) should probably go to
<URL:mailto:emacs-custom@sunsite.auc.dk>, replies redirected there.
Karl Kleinpaste <karl@jprc.com> writes:
> In a CMU-local chat system this morning, there's been an argu^H^H^Hdiscussion
> about the customization of fonts and colors in Gnus. It seems that a
> lot of folks are uptight at the fact that there's a bunch of things to
> change, instead of some monolithic way to pick a whole color scheme at
> once, or at least to change everything to a single color. A primary
> plaintiff in this says that he would really like not to have to go
> through a set of a dozen different color/font selections, but instead
> could say "change all foreground colors to MidnightBlue and don't
> bother me about it any more." The related "scheme" idea comes from
> the Windows-centric crowd, where there are ways of picking a whole
> selection of quasi-matched colors for one's basic environment.
>
> I've never so much as glanced at the internals of customize. Any
> opinions out there on how hard it would be to create such things as
> "scheme"-based color choices (with a few such sample schemes to start
> with) and an aggressive change-all-of-'em-in-this-group-to-this-color
> function?
>
> --karl
next prev parent reply other threads:[~1998-04-07 15:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-07 14:24 Karl Kleinpaste
1998-04-07 15:30 ` Per Abrahamsen [this message]
[not found] ` <x7lnth4ewy.fsf@peorth.gweep.net>
1998-04-07 22:08 ` Hrvoje Niksic
[not found] ` <x7d8et1buq.fsf@peorth.gweep.net>
1998-04-08 10:05 ` Per Abrahamsen
1998-04-08 10:05 ` Per Abrahamsen
1998-04-07 16:28 ` Scott Blachowicz
[not found] ` <x7ogyd4ez4.fsf@peorth.gweep.net>
1998-04-07 21:31 ` Karl Kleinpaste
[not found] ` <x7iuol1eml.fsf@peorth.gweep.net>
1998-04-07 23:40 ` Karl Kleinpaste
[not found] ` <x7vhslvy0k.fsf@peorth.gweep.net>
1998-04-08 2:46 ` Hrvoje Niksic
1998-04-08 18:57 ` Jake Colman
1998-04-08 21:03 ` Alan Shutko
1998-04-09 11:26 ` Hrvoje Niksic
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=rjhg45fy4j.fsf@zuse.+dina.kvl.dk \
--to=abraham@dina.kvl.dk \
--cc=ding@gnus.org \
--cc=emacs-custom@sunsite.auc.dk \
/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.
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 NNTP newsgroup(s).