Gnus development mailing list
 help / color / mirror / Atom feed
From: Lloyd Zusman <ljz@asfast.com>
Subject: Startup error (benign?) in recent Oort versions.
Date: 19 Aug 2001 21:06:13 -0400	[thread overview]
Message-ID: <m27kvzczga.fsf@asfast.com> (raw)

In recent Oort versions (at least in v0.04), I get the following stack
trace when I start up gnus with debugging turned on (debug-on-quit,
debug-on-signal, and debug-on-error).  I'm not sure if this is a bona
fide problem or it's benign, but I thought I'd report it here, just in
case.  Even if it's benign, it prevents me from easily tracing other
errors.

Here's my XEmacs version:

  21.4 (patch 3) "Academic Rigor" XEmacs Lucid

Any ideas?

[ Lines manually wrapped ]

 Signaling: (void-function gnus-visual-p)
   (gnus-visual-p (quote mouse-face) (quote highlight))
   (if (gnus-visual-p (quote mouse-face) (quote highlight)) 
     (if (boundp ...) (or gnus-mouse-face ...) (quote highlight)) 
     (quote default))
   (condition-case nil (if (gnus-visual-p ... ...) (if ... ... ...) 
     (quote default)) (error (quote highlight)))
   eval((condition-case nil (if (gnus-visual-p ... ...) (if ... ... ...) 
     (quote default)) (error (quote highlight))))
   custom-initialize-reset(gnus-mouse-face (condition-case nil 
     (if (gnus-visual-p ... ...) (if ... ... ...) (quote default)) 
     (error (quote highlight))))
   custom-declare-variable(gnus-mouse-face (condition-case nil 
     (if (gnus-visual-p ... ...) (if ... ... ...) (quote default)) 
     (error (quote highlight))) 
     "*Face used for group or summary buffer mouse highlighting.\n
     The line beneath the mouse pointer will be highlighted with this\nface." 
     :group gnus-visual :type face)
   load-internal("gnus" nil nil nil nil nil)
   load("gnus" nil nil nil)
   gnus()


-- 
 Lloyd Zusman
 ljz@asfast.com


             reply	other threads:[~2001-08-20  1:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-20  1:06 Lloyd Zusman [this message]
2001-08-21 22:08 ` Lars Magne Ingebrigtsen

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=m27kvzczga.fsf@asfast.com \
    --to=ljz@asfast.com \
    /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).