Hi Graham On Dec 13, 2007 1:11 PM, Graham Smith <[EMAIL PROTECTED]> 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 _______________________________________________ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
