From mboxrd@z Thu Jan 1 00:00:00 1970 From: "William Henney" Subject: Re: help with modifying a bit of code in .emacs Date: Thu, 13 Dec 2007 19:27:07 -0600 Message-ID: <41c818190712131727s16bb71e9y7d1038e881c23c8a@mail.gmail.com> References: <2c75873c0712131111m5b435f6cp912c2bce3b16f4d6@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1J2zKZ-0007cz-KA for emacs-orgmode@gnu.org; Thu, 13 Dec 2007 20:27:11 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1J2zKY-0007ck-98 for emacs-orgmode@gnu.org; Thu, 13 Dec 2007 20:27:10 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J2zKY-0007ch-4c for emacs-orgmode@gnu.org; Thu, 13 Dec 2007 20:27:10 -0500 Received: from wa-out-1112.google.com ([209.85.146.180]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1J2zKX-0008OM-Rr for emacs-orgmode@gnu.org; Thu, 13 Dec 2007 20:27:10 -0500 Received: by wa-out-1112.google.com with SMTP id k34so1436546wah.10 for ; Thu, 13 Dec 2007 17:27:08 -0800 (PST) In-Reply-To: <2c75873c0712131111m5b435f6cp912c2bce3b16f4d6@mail.gmail.com> Content-Disposition: inline List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Graham Smith Cc: emacs-orgmode@gnu.org Hi Graham On Dec 13, 2007 1:11 PM, Graham Smith 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 --=20 Dr William Henney, Centro de Radioastronom=EDa y Astrof=EDsica, Universidad Nacional Aut=F3noma de M=E9xico, Campus Morelia