Gnus development mailing list
 help / color / mirror / Atom feed
From: Wes Hardaker <hardaker@ece.ucdavis.edu>
Subject: My latest in pretty pictures:  picons support
Date: Tue, 09 Jan 1996 16:33:14 -0800	[thread overview]
Message-ID: <199601100033.AA177293996@chroma.ece.ucdavis.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1163 bytes --]

Well, I've played with things quiet a bit since the last time I sent
this out.  It now can display the icons practically anywhere in any
buffer.  I have it set so that it displays them in its own (and this
is the default).  See the top of the lisp code for documentation on
its usage.  Note that there are now TWO hooks, not one like
previously.  One is for displaying the group icons, and the other is
for displaying the user/domain icons.  The code should replace gnus-picon.el 
in the .26 distribution.

Also enclosed is a patch to gnus.el, for v0.26.  It changes the names
of some of the variables to be 'picons' instead of 'picon'.  This
patch and this code will probably be in .27 or .28, assuming Lars puts
it there :-)
                                                                _____ 
Wes Hardaker                                                   / ___ \
Department of Electrical and Computer Engineering             / /   \//\
University of California at Davis        __________________  \--/    /--\
Davis CA  95616                         /     Recycle!     \  \//\___/ /
(hardaker@ece.ucdavis.edu)             / It's not too late! \   \_____/



[-- Attachment #2: gnus.diff --]
[-- Type: application/x-patch, Size: 2466 bytes --]

[-- Attachment #3: gnus-picons.el --]
[-- Type: application/x-elisp, Size: 9793 bytes --]

                 reply	other threads:[~1996-01-10  0:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=199601100033.AA177293996@chroma.ece.ucdavis.edu \
    --to=hardaker@ece.ucdavis.edu \
    /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).