Gnus development mailing list
 help / color / mirror / Atom feed
From: John Griffith <griffith@sfs.nphil.uni-tuebingen.de>
Cc: ding@ifi.uio.no
Subject: Re: Picon related bugs--anyone else see these?
Date: 13 Aug 1996 11:08:54 +0200	[thread overview]
Message-ID: <tjhgq7hcrd.fsf@sfs.nphil.uni-tuebingen.de> (raw)
In-Reply-To: Sudish Joseph's message of 12 Aug 1996 21:08:50 -0400


I just started using picons.  I see this bug as well (XEmacs 19.14).
I have essentially the same settings as Sudish.

I also notice the picon display is slow.  When selecting an article,
the buffers get messed up for about half a second before stabilizing.
It could be because of searching for picon files across NFS, or it
could just be slow drawing on XEmacs' part.


  parent reply	other threads:[~1996-08-13  9:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-08-11  4:31 Sudish Joseph
1996-08-12  6:24 ` Wes Hardaker
1996-08-13  1:08   ` Sudish Joseph
1996-08-13  8:17     ` Lars Magne Ingebrigtsen
1996-08-13  9:08     ` John Griffith [this message]
1996-08-13 12:38       ` Wesley.Hardaker
1996-08-14  6:24         ` Wesley.Hardaker
1996-08-13 12:35     ` Wesley.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=tjhgq7hcrd.fsf@sfs.nphil.uni-tuebingen.de \
    --to=griffith@sfs.nphil.uni-tuebingen.de \
    --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).