From: Wes Hardaker <hardaker@ece.ucdavis.edu>
Cc: ding@ifi.uio.no
Subject: Re: Picons bugs in 5.2.19
Date: 18 Jun 1996 10:43:07 -0700 [thread overview]
Message-ID: <sdk9x5ypn8.fsf@teal.ece.ucdavis.edu> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 18 Jun 1996 19:03:23 +0200
Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
> But there is no `set-to-buffer' function. :-) Perhaps the ChangeLog
> entry should have read:
>
> Mon Jun 10 21:40:13 1996 Lars Magne Ingebrigtsen <lars@eyesore.no>
> * gnus-picon.el (gnus-group-display-picons): `set-to-buffer'!?!?!
I'm still confused (but I hardly could care less about) where you even
found the set-to-buffer to exist... Its one of the reasons I didn't
understand the changelog entry... set-to-buffer DNE, and was never
used (AFAIK).
> It should be `(set-buffer (get-buffer-create ...))', I guess.
> `switch-to-buffer' broke something for somebody, which is why I did
> the first "correction". :-/
:-(
|> (Dontcha lurve them smilies? :-] )
I'm sure we now need an 'insert smiley sub-menu somewhere...' ;->
I also wanted to turn the smilies/pictures into buttons which would
toggle the state of a given smiley (text vs picture). Should be easy.
> Does anybody have a list of ASCII smileys? I'm sure there are smileys
> that we're missing...
I think there is a HUGE list somewhere. Much longer than you want.
Probably even a web page (or 100) about them.
Last I checked, we're not even using all the images we have yet.
--
_____
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! \ \_____/
next prev parent reply other threads:[~1996-06-18 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-18 16:45 Wes Hardaker
1996-06-18 17:03 ` Lars Magne Ingebrigtsen
1996-06-18 17:43 ` Wes Hardaker [this message]
1996-06-18 18:38 ` luis fernandes
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=sdk9x5ypn8.fsf@teal.ece.ucdavis.edu \
--to=hardaker@ece.ucdavis.edu \
--cc=ding@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).