From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: Picons bugs in 5.2.19
Date: 18 Jun 1996 19:03:23 +0200 [thread overview]
Message-ID: <x691dlavtw.fsf@eyesore.no> (raw)
In-Reply-To: Wes Hardaker's message of 18 Jun 1996 09:45:45 -0700
Wes Hardaker <hardaker@ece.ucdavis.edu> writes:
> Mon Jun 10 21:40:13 1996 Lars Magne Ingebrigtsen <lars@eyesore.no>
> * gnus-picon.el (gnus-group-display-picons): `set-to-buffer'?
>
> This breaks if you have the default of
>
> (defvar gnus-picons-display-where 'picons
>
> since set-to-buffer (set-buffer? I don't remember which you changed
> it to) doesn't create the "*Picons*" buffer if it does not exist,
> which it needs to do upon reading the first group.
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'!?!?!
instead. :-)
(I wanted to change `switch-to-buffer' to `set-buffer', and I got a
bit confused.)
> As shipped, 5.2.19 broke for me till I either created the *Picons*
> buffer or changed the set-buffer? back to switch-to-buffer. :-( :-(
> :-( :-(
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? :-] )
Does anybody have a list of ASCII smileys? I'm sure there are smileys
that we're missing...
--
"Yes. The journey through the human heart
would have to wait until some other time."
next prev parent reply other threads:[~1996-06-18 17:03 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 [this message]
1996-06-18 17:43 ` Wes Hardaker
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=x691dlavtw.fsf@eyesore.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).