From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: broken gnus-group-jump-to-group?
Date: 31 Aug 1999 17:29:58 +0200 [thread overview]
Message-ID: <vafzoz8ynm1.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Clinton Roy's message of "31 Aug 1999 12:39:26 +1000"
Clinton Roy <s344025@student.uq.edu.au> writes:
> so now what can i do to start tracking the problem down?
Can you type M-x toggle-debug-on-error RET, then repeat the problem?
You should get a backtrace. If it contains gibberish, have a look at
the line below the gibberish. This gives you a function name. Load
the *.el file where this function is defined. Repeat. If there's
still gibberish, repeat. Post the resulting backtrace (with no
gibberish).
(Gibberish is usually on a line which starts with "byte-code".)
kai
--
I like BOTH kinds of music.
next prev parent reply other threads:[~1999-08-31 15:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-29 14:06 Clinton Roy
1999-08-29 20:02 ` Kai Großjohann
[not found] ` <87k8qc4qsh.fsf@stleo011.stleo.uq.edu.au>
1999-08-31 15:29 ` Kai Großjohann [this message]
1999-09-10 0:50 ` Clinton Roy
1999-09-10 9:19 ` Toby Speight
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=vafzoz8ynm1.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.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).