William,<br><br>Thanks, this has now been fixed, and the code that works is:<br><br><span class="q">(setq org-agenda-custom-commands <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &#39;(<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (&quot;d&quot; todo #(&quot;DELEGATED&quot;) nil)
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (&quot;c&quot; todo #(&quot;DONE|DEFERRED|CANCELLED&quot;) nil)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (&quot;w&quot; todo #(&quot;WAITING&quot;) nil)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (&quot;W&quot; agenda &quot;&quot; ((org-agenda-ndays 21)))<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (&quot;A&quot; agenda &quot;&quot; ((org-agenda-skip-function
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (lambda nil (org-agenda-skip-entry-if (quote notregexp) &quot;\\=.*\\[#A\\]&quot;)))<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (org-agenda-ndays 1)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (org-agenda-overriding-header &quot;Today&#39;s Priority #A tasks: &quot;)))
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (&quot;u&quot; alltodo &quot;&quot; ((org-agenda-skip-function<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (lambda nil (org-agenda-skip-entry-if (quote scheduled) (quote deadline)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (quote regexp) &quot;&lt;[^&gt;\n]+&gt;&quot;)))
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (org-agenda-overriding-header &quot;Unscheduled TODO entries: &quot;)))))<br><br><br>I got some help sent directly to me, didn&#39;t realise it wasn&#39;t on the list and then go t side tracked into other bits that didn&#39;t work.
<br><br>But the backtrace info is useful to have.<br><br>Thanks,<br><br>Graham<br></span><br><div><span class="gmail_quote">On 14/12/2007, <b class="gmail_sendername">William Henney</b> &lt;<a href="mailto:whenney@gmail.com">
whenney@gmail.com</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Graham<br><br>On Dec 13, 2007 1:11 PM, Graham Smith &lt;
<a href="mailto:myotisone@gmail.com">myotisone@gmail.com</a>&gt; wrote:<br>&gt; I have been using the set up provided by John Wiegley on a Mac and have<br>&gt; tried to to use it with Emacs32 wbut with some problems as the
<br>&gt; custom-set-variables command seemed to badly interact with the Emacs32w<br>&gt; custom-set-variables.<br>&gt;<br><br>I have no specific help to offer, but you should be able to narrow<br>down the problem further by turning on debugging of your init file.
<br>Starting from a unix command line, this would be &quot;emacs --debug-init<br>&amp;&quot;, but I have no idea whether this would work on windows. If you<br>can&#39;t work out how to do this on windows, you could use a more
<br>roundabout method as follows:<br><br>1. temporarily remove/comment the problematic code from your .emacs<br>and put it in a separate file, say &quot;bad-code.el&quot;<br>2. restart emacs<br>3. turn on debugging with<br>
&nbsp;&nbsp; M-x set-variable RET debug-on-error RET t RET<br>4. evaluate the problematic code by doing<br>&nbsp;&nbsp; M-x load-file RET path/to/bad-code.el RET<br><br>In principle, either of these methods should give you a lisp backtrace<br>
indicating exactly what the offending command is. Even if you don&#39;t<br>understand the backtrace, it might help someone else to diagnose your<br>problem.<br><br>Cheers<br><br>Will<br><br><br>--<br><br>&nbsp;&nbsp;Dr William Henney, Centro de Radioastronomía y Astrofísica,
<br>&nbsp;&nbsp;Universidad Nacional Autónoma de México, Campus Morelia<br></blockquote></div><br>