From: Kevin Rodgers <kevin.d.rodgers@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Debugging .emacs file
Date: Wed, 21 Feb 2007 21:51:23 -0700 [thread overview]
Message-ID: <erj7gd$qa1$2@sea.gmane.org> (raw)
In-Reply-To: <9079277.post@talk.nabble.com>
SteveFKI wrote:
> I am new to EMACS, and have created my own .emacs file (because I want to
> learn how to do it from scratch). When I open a C file I get the message
> "File mode specification error (wrong-type-argument : listp 3).
>
> I would like to be able to debug my .emacs file, and see what is going on,
> but if I start EMACS with emacs -debug-init test.c I don't get any debug
> info. (This is obviosuly not the right thing to do).
You don't get a *Backtrace* buffer because the error does not occur
while your .emacs file is loaded, it occurs later (due to something in
your .emacs file).
Try starting Emacs like this:
emacs --eval '(setq debug-on-error t)' test.c
--
Kevin Rodgers
Denver, Colorado, USA
next prev parent reply other threads:[~2007-02-22 4:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 11:28 Debugging .emacs file SteveFKI
2007-02-22 4:51 ` Kevin Rodgers [this message]
[not found] <mailman.4846.1172063621.2155.help-gnu-emacs@gnu.org>
2007-02-21 14:31 ` Robert Thorpe
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='erj7gd$qa1$2@sea.gmane.org' \
--to=kevin.d.rodgers@gmail.com \
--cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).