Gnus development mailing list
 help / color / mirror / Atom feed
From: John Paul Wallington <jpw@shootybangbang.com>
Cc: Thomas Hungenberg <th@demonium.de>, ding@gnus.org
Subject: Re: Cannot open load file: tool-bar
Date: Mon, 04 Nov 2002 14:30:30 +0000	[thread overview]
Message-ID: <87adkpz9tl.fsf@bundalo.shootybangbang.com> (raw)
In-Reply-To: <ilud6pmeen9.fsf@latte.josefsson.org> (Simon Josefsson's message of "Sun, 03 Nov 2002 18:39:38 +0100")

Simon Josefsson <jas@extundo.com> wrote:

> Thomas Hungenberg <th@demonium.de> writes:
[...]
>> But even with this small configuration, Gnus still stops with the same
>> signal:
>>
>> -----[begin of quoted message]------------------------------------------
>> Signaling: (file-error "Cannot open load file" "tool-bar")
>>   signal(file-error ("Cannot open load file" "tool-bar"))
>
> Gnus triggers lots of non-fatal signals (240 according to grep -e
> unwind-protect -e condition-case *.el|wc -l).  If you really want to
> have debug-on-signal enabled, you will have to press `c' to continue.

Simon is right.  Do you really want `debug-on-signal' enabled?
Wouldn't `debug-on-error' do?

If you do (require 'poe) or snarf XEmacs 21.5 from CVS then you should
get a third NOERROR argument to `require'.  If you use it, you
shouldn't cause a signal here (untested with poe).  Or you could just
comment out the (condition-case nil (require 'tool-bar) (error nil))
in `gnus-group-make-tool-bar' in lisp/gnus-group.el and recompile to
avoid it.

BTW, what was your initial configuration problem ?

-- 
John Paul Wallington



  reply	other threads:[~2002-11-04 14:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-03 16:15 Thomas Hungenberg
2002-11-03 17:39 ` Simon Josefsson
2002-11-04 14:30   ` John Paul Wallington [this message]
2002-11-04 17:03     ` Thomas Hungenberg
2002-11-04 18:43       ` John Paul Wallington
2002-11-04 20:21         ` Problems with bbdb and supercite (was: Re: Cannot open load file: tool-bar) Thomas Hungenberg
2002-11-04 22:10           ` Problems with bbdb and supercite Jack Twilley
2002-11-05  7:32           ` Kai Großjohann
2002-11-03 18:47 ` Cannot open load file: tool-bar Kai Großjohann
2002-11-04  9:59   ` Thomas Hungenberg
2002-11-04 13:44     ` Kai Großjohann
2002-11-04 16:52       ` Thomas Hungenberg
2002-11-04 21:04         ` Kai Großjohann
2002-11-04 22:11           ` Thomas Hungenberg
2002-11-05  7:35             ` Kai Großjohann
2002-11-05 11:23               ` Thomas Hungenberg
2002-11-05 17:26                 ` Kai Großjohann
2002-11-05 18:03                   ` Jesper Harder
2002-11-05 19:14                     ` Kai Großjohann
2002-11-05 22:50                       ` Jesper Harder
2002-11-05 20:49                   ` John Paul Wallington
2002-11-06  7:27                     ` Simon Josefsson
2002-11-06 12:39                       ` John Paul Wallington

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=87adkpz9tl.fsf@bundalo.shootybangbang.com \
    --to=jpw@shootybangbang.com \
    --cc=ding@gnus.org \
    --cc=th@demonium.de \
    /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).