From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Graham Smith" Subject: Re: help with modifying a bit of code in .emacs Date: Fri, 14 Dec 2007 08:56:16 +0000 Message-ID: <2c75873c0712140056v5150f907yc92af2e74250f0a8@mail.gmail.com> References: <2c75873c0712131111m5b435f6cp912c2bce3b16f4d6@mail.gmail.com> <41c818190712131727s16bb71e9y7d1038e881c23c8a@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0740379262==" Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1J36LH-0008UV-7L for emacs-orgmode@gnu.org; Fri, 14 Dec 2007 03:56:23 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1J36LE-0008TI-Iz for emacs-orgmode@gnu.org; Fri, 14 Dec 2007 03:56:22 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J36LD-0008T3-H7 for emacs-orgmode@gnu.org; Fri, 14 Dec 2007 03:56:19 -0500 Received: from an-out-0708.google.com ([209.85.132.247]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1J36LA-0007MV-TV for emacs-orgmode@gnu.org; Fri, 14 Dec 2007 03:56:17 -0500 Received: by an-out-0708.google.com with SMTP id c25so232907ana.84 for ; Fri, 14 Dec 2007 00:56:16 -0800 (PST) In-Reply-To: <41c818190712131727s16bb71e9y7d1038e881c23c8a@mail.gmail.com> 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: emacs-orgmode@gnu.org --===============0740379262== Content-Type: multipart/alternative; boundary="----=_Part_1078_26173439.1197622576164" ------=_Part_1078_26173439.1197622576164 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline William, Thanks, this has now been fixed, and the code that works is: (setq org-agenda-custom-commands '( ("d" todo #("DELEGATED") nil) ("c" todo #("DONE|DEFERRED|CANCELLED") nil) ("w" todo #("WAITING") nil) ("W" agenda "" ((org-agenda-ndays 21))) ("A" agenda "" ((org-agenda-skip-function (lambda nil (org-agenda-skip-entry-if (quote notregexp) "\\=3D.*\\[#A\\]"))) (org-agenda-ndays 1) (org-agenda-overriding-header "Today's Priority #A tasks: "))) ("u" alltodo "" ((org-agenda-skip-function (lambda nil (org-agenda-skip-entry-if (quote scheduled) (quote deadline) (quote regexp) "<[^>\n]+>"))) (org-agenda-overriding-header "Unscheduled TODO entries: "))))) I got some help sent directly to me, didn't realise it wasn't on the list and then go t side tracked into other bits that didn't work. But the backtrace info is useful to have. Thanks, Graham On 14/12/2007, William Henney wrote: > > 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 > > > -- > > Dr William Henney, Centro de Radioastronom=EDa y Astrof=EDsica, > Universidad Nacional Aut=F3noma de M=E9xico, Campus Morelia > ------=_Part_1078_26173439.1197622576164 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline William,

Thanks, this has now been fixed, and the code that works is= :

(setq org-agenda-custom-commands
  = ;    '(
        (&= quot;d" todo #("DELEGATED") nil)
        ("c" todo #("= DONE|DEFERRED|CANCELLED") nil)
      =   ("w" todo #("WAITING") nil)
   = ;     ("W" agenda "" ((org-agenda-n= days 21)))
        ("A" age= nda "" ((org-agenda-skip-function
            = ;            &n= bsp;  (lambda nil (org-agenda-skip-entry-if (quote notregexp) "\\= =3D.*\\[#A\\]")))
        &= nbsp;           &nbs= p;   (org-agenda-ndays 1)
      =             &nb= sp;     (org-agenda-overriding-header "Today's= Priority #A tasks: ")))
        ("u" alltodo "= ;" ((org-agenda-skip-function
      &= nbsp;           &nbs= p;       (lambda nil (org-agenda-skip-entry-i= f (quote scheduled) (quote deadline)
      = ;            &n= bsp;            = ;            &n= bsp;            = ;        (quote regexp) "<[^>= \n]+>")))
            = ;             (= org-agenda-overriding-header "Unscheduled TODO entries: ")))))

I got some help sent directly to me, didn't realise it wasn= 9;t on the list and then go t side tracked into other bits that didn't = work.

But the backtrace info is useful to have.

Thanks,

Gra= ham

On 14/12/2007, William Henney < whenney@gmail.com> wrote:
Hi Graham

On Dec 13, 2007 1:11 PM, Graham Smit= h < myotisone@gmail.com> wrote:> I have been using the set up provided by John Wiegley on a Mac and h= ave
> tried to to use it with Emacs32 wbut with some problems as the
> custom-set-variables command seemed to badly interact with the Ema= cs32w
> custom-set-variables.
>

I have no specific help = to offer, but you should be able to narrow
down the problem further by t= urning on debugging of your init file.
Starting from a unix command line, this would be "emacs --debug-in= it
&", but I have no idea whether this would work on windows. I= f 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 &qu= ot;bad-code.el"
2. restart emacs
3. turn on debugging with
   M-x set-variable RET debug-on-error RET t RET
4. evaluate t= he 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
pr= oblem.

Cheers

Will


--

  Dr Willia= m Henney, Centro de Radioastronom=EDa y Astrof=EDsica,
  Universidad Nacional Aut=F3noma de M=E9xico, Campus Morelia=

------=_Part_1078_26173439.1197622576164-- --===============0740379262== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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 --===============0740379262==--