From: "Robert Thorpe" <rthorpe@realworldtech.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Debugging .emacs file
Date: 21 Feb 2007 06:31:59 -0800 [thread overview]
Message-ID: <1172068319.446131.299760@v45g2000cwv.googlegroups.com> (raw)
In-Reply-To: <mailman.4846.1172063621.2155.help-gnu-emacs@gnu.org>
On Feb 21, 11:28 am, SteveFKI <stephen.br...@eu.fkilogistex.com>
wrote:
<snip>
> (setq c-basic-offset . 3)
The dot above is a typo.
The general way to debug .emacs is to use "progressive halving".
What you do is comment out half of the file, then start emacs. If it
doesn't work you know the problem is in the enabled half, if it works
you know the problem is in the commented out half, then you reenable
half of that half. You then continue in that way.
You should use --debug-init too.
next parent reply other threads:[~2007-02-21 14:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.4846.1172063621.2155.help-gnu-emacs@gnu.org>
2007-02-21 14:31 ` Robert Thorpe [this message]
2007-02-21 11:28 Debugging .emacs file SteveFKI
2007-02-22 4:51 ` Kevin Rodgers
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=1172068319.446131.299760@v45g2000cwv.googlegroups.com \
--to=rthorpe@realworldtech.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).