From: "William Henney" <whenney@gmail.com>
To: Graham Smith <myotisone@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: help with modifying a bit of code in .emacs
Date: Thu, 13 Dec 2007 19:27:07 -0600 [thread overview]
Message-ID: <41c818190712131727s16bb71e9y7d1038e881c23c8a@mail.gmail.com> (raw)
In-Reply-To: <2c75873c0712131111m5b435f6cp912c2bce3b16f4d6@mail.gmail.com>
Hi Graham
On Dec 13, 2007 1:11 PM, Graham Smith <myotisone@gmail.com> wrote:
> I have been using the set up provided by John Wiegley on a Mac and have
> tried to to use it with Emacs32 wbut with some problems as the
> custom-set-variables command seemed to badly interact with the Emacs32w
> custom-set-variables.
>
I have no specific help to offer, but you should be able to narrow
down the problem further by turning on debugging of your init file.
Starting from a unix command line, this would be "emacs --debug-init
&", but I have no idea whether this would work on windows. If you
can't work out how to do this on windows, you could use a more
roundabout method as follows:
1. temporarily remove/comment the problematic code from your .emacs
and put it in a separate file, say "bad-code.el"
2. restart emacs
3. turn on debugging with
M-x set-variable RET debug-on-error RET t RET
4. evaluate the problematic code by doing
M-x load-file RET path/to/bad-code.el RET
In principle, either of these methods should give you a lisp backtrace
indicating exactly what the offending command is. Even if you don't
understand the backtrace, it might help someone else to diagnose your
problem.
Cheers
Will
--
Dr William Henney, Centro de Radioastronomía y Astrofísica,
Universidad Nacional Autónoma de México, Campus Morelia
next prev parent reply other threads:[~2007-12-14 1:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 19:11 help with modifying a bit of code in .emacs Graham Smith
2007-12-14 1:27 ` William Henney [this message]
2007-12-14 8:56 ` Graham Smith
2007-12-14 2:08 ` Chris Leyon
2007-12-14 9:00 ` Graham Smith
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41c818190712131727s16bb71e9y7d1038e881c23c8a@mail.gmail.com \
--to=whenney@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=myotisone@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).