From: Dan Mills <dm@cs.duke.edu>
Subject: Re: problem with picons
Date: 18 Nov 1999 12:54:21 -0500 [thread overview]
Message-ID: <87vh6zofci.fsf@majikthise.adsl.duke.edu> (raw)
In-Reply-To: Kim-Minh Kaplan's message of "18 Nov 1999 11:30:01 +0100"
Kim-Minh Kaplan <kmkaplan@vocatex.fr> writes:
> Might also be the Gnus version as you are now running:
>
> > X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald"
>
> Can you check with the where and when (use the CVS tree) the problem
> happens ? Also a lisp backtrace would be helpful in understanding the
> problem.
I was using Gnus 5.5 by mistake.. I now switched back to pgnus (0.65 I
think), and Picons still work fine.
I don't know how to make a lisp backtrace, though. How would I do
that?
-Dan
--
Dan Mills, Duke Class of 2000 -o)
email: dm(at)cs(dot)duke(dot)edu /\\
-----------------------------------\ _\_v
Damn Sill.. Sand Mill? All Minds! |_____
next prev parent reply other threads:[~1999-11-18 17:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-15 11:04 Dan Mills
1999-11-16 11:00 ` Kim-Minh Kaplan
1999-11-16 6:22 ` Dan Mills
1999-11-16 14:48 ` Kim-Minh Kaplan
1999-11-16 22:22 ` David Porter
1999-11-17 13:59 ` Dan Mills
1999-11-17 16:14 ` Dan Mills
1999-11-18 10:30 ` Kim-Minh Kaplan
1999-11-18 17:54 ` Dan Mills [this message]
1999-11-19 21:35 ` Matt McClure
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=87vh6zofci.fsf@majikthise.adsl.duke.edu \
--to=dm@cs.duke.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).