From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: ...and more picons
Date: 18 Jun 1996 15:50:45 +0000 [thread overview]
Message-ID: <w8sbuihdsbu.fsf@hler.ifi.uio.no> (raw)
In-Reply-To: Hallvard B Furuseth's message of Tue, 18 Jun 1996 17:39:57 +0200 (MET DST)
Hallvard B Furuseth <h.b.furuseth@usit.uio.no> writes:
> > there's now a `gnus-picons-get-maximum-picons' variable that
> > defaults to t
>
> Can this take time? With a slow machine, my first priority can be is to
> get rid of anything time-consuming. (Including scoring and even
> threading, sometimes.) Other times, I want anything which makes things
> look or work better.
Picons is off by default -- you have to add some functions to
`gnus-article-display-hook' to see them.
> The number of variables to keep track of, is growing again... I'd like
> to be able to configure all this, without having to keep track of all
> the variables. How about a `gnus-nice-stuff' variable into which you
> put a list of the nice features we want? Or gnus-nice-visual-stuff,
> gnus-nice-treading-stuff and so on. Hm. We tried that before without
> much success. Maybe an M-x gnus-configure is better. Asks about
> general things, like "do you want gnus to be nice, or fast?"
Those meta-variables again. :-)
The manual for the new Custom thing is very nice. To bad the new
custom.el hasn't been written yet. Lots of neat things that can be
done within that framework...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@ifi.uio.no * Lars Ingebrigtsen
next prev parent reply other threads:[~1996-06-18 15:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-18 15:17 Lars Magne Ingebrigtsen
1996-06-18 15:39 ` Hallvard B Furuseth
1996-06-18 15:50 ` Lars Magne Ingebrigtsen [this message]
1996-06-18 16:38 ` Wes Hardaker
1996-06-18 16:58 ` Lars Magne Ingebrigtsen
1996-06-18 17:34 ` Wes Hardaker
1996-06-18 18:05 ` Wes Hardaker
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=w8sbuihdsbu.fsf@hler.ifi.uio.no \
--to=larsi@ifi.uio.no \
/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).