From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: problems in sending out emails
Date: Tue, 20 Jan 2015 18:21:14 +0100 [thread overview]
Message-ID: <upzc3875fjw5.fsf@dod.no> (raw)
In-Reply-To: <87egqpy4sl.fsf@skimble.plus.com>
Do C-j behind
(setq debug-on-error t)
in *scratch* and then when the error reoccurs, add then post the stack
trace.
It might be a good idea to do this twice: first find where the failure
happens, then load that file as a .el file (to get more symbols), and
then provoke the failure again.
The second stack trace will usually be more meaningful.
next prev parent reply other threads:[~2015-01-20 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 13:12 Sharon Kimble
2015-01-20 17:21 ` Steinar Bang [this message]
2015-01-20 18:03 ` e.fraga
2015-01-22 18:45 ` Sharon Kimble
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=upzc3875fjw5.fsf@dod.no \
--to=sb@dod.no \
--cc=ding@gnus.org \
/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).