* Sparse tree for undated TODOs, or hierachical agenda?
@ 2015-04-18 3:35 Nikolaus Rath
2015-04-21 1:16 ` Nikolaus Rath
2015-04-21 14:10 ` Jorge A. Alfaro-Murillo
0 siblings, 2 replies; 12+ messages in thread
From: Nikolaus Rath @ 2015-04-18 3:35 UTC (permalink / raw)
To: emacs-orgmode
Hello,
I'm starting to like orgmode more and more. Thanks for working on this!
However, for me the global todo list in the Agenda very hard to digest
(even when excluding sublevels), so I'd rather have a view that
conserves the document structure.
Is there a way to create a sparse tree that shows only undated TODOs
(i.e., excludes anything that scheduled or has a deadline)?
Or, alternatively, is there a way to generate an Agenda view that
preserves the outline of the document (i.e., TODO items are grouped by
their headings)?
Thanks,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: Sparse tree for undated TODOs, or hierachical agenda?
2015-04-18 3:35 Sparse tree for undated TODOs, or hierachical agenda? Nikolaus Rath
@ 2015-04-21 1:16 ` Nikolaus Rath
2015-04-21 14:10 ` Jorge A. Alfaro-Murillo
1 sibling, 0 replies; 12+ messages in thread
From: Nikolaus Rath @ 2015-04-21 1:16 UTC (permalink / raw)
To: emacs-orgmode
Hi,
On Apr 17 2015, Nikolaus Rath <Nikolaus@rath.org> wrote:
> However, for me the global todo list in the Agenda very hard to digest
> (even when excluding sublevels), so I'd rather have a view that
> conserves the document structure.
>
> Is there a way to create a sparse tree that shows only undated TODOs
> (i.e., excludes anything that scheduled or has a deadline)?
>
> Or, alternatively, is there a way to generate an Agenda view that
> preserves the outline of the document (i.e., TODO items are grouped by
> their headings)?
Really no one has any suggestion?
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: Sparse tree for undated TODOs, or hierachical agenda?
2015-04-18 3:35 Sparse tree for undated TODOs, or hierachical agenda? Nikolaus Rath
2015-04-21 1:16 ` Nikolaus Rath
@ 2015-04-21 14:10 ` Jorge A. Alfaro-Murillo
2015-04-21 15:35 ` Nikolaus Rath
1 sibling, 1 reply; 12+ messages in thread
From: Jorge A. Alfaro-Murillo @ 2015-04-21 14:10 UTC (permalink / raw)
To: emacs-orgmode
Hi, Nikolaus.
Nikolaus Rath writes:
> Hello,
>
> I'm starting to like orgmode more and more. Thanks for working
> on this!
>
> However, for me the global todo list in the Agenda very hard to
> digest (even when excluding sublevels), so I'd rather have a
> view that conserves the document structure.
If you want to restrict to your current document before building
the agenda use '<', so if 'C-c a' calls your agenda (suggested org
key), then you can do 'C-c a < a' to get the agenda restricted to
the buffer that you are in.
> Is there a way to create a sparse tree that shows only undated
> TODOs (i.e., excludes anything that scheduled or has a
> deadline)?
I do not know what you mean by sparse tree, but this excludes
anything scheduled or with a deadline from the global todo list:
#+BEGIN_SRC emacs-lisp
(setq org-agenda-todo-ignore-scheduled 'all)
(setq org-agenda-todo-ignore-deadlines 'all)
#+END_SRC
Instead of 'all you can also use 'past or 'future to exclude only
scheduled and deadlines from the past or the future, respectively.
Best,
--
Jorge.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Sparse tree for undated TODOs, or hierachical agenda?
2015-04-21 14:10 ` Jorge A. Alfaro-Murillo
@ 2015-04-21 15:35 ` Nikolaus Rath
2015-04-21 17:11 ` Jorge A. Alfaro-Murillo
0 siblings, 1 reply; 12+ messages in thread
From: Nikolaus Rath @ 2015-04-21 15:35 UTC (permalink / raw)
To: emacs-orgmode
On Apr 21 2015, jorge.alfaro-murillo@yale.edu (Jorge A. Alfaro-Murillo) wrote:
> Hi, Nikolaus.
>
> Nikolaus Rath writes:
>
>> Hello,
>>
>> I'm starting to like orgmode more and more. Thanks for working
>> on this!
>>
>> However, for me the global todo list in the Agenda very hard to
>> digest (even when excluding sublevels), so I'd rather have a
>> view that conserves the document structure.
>
> If you want to restrict to your current document before building
> the agenda use '<', so if 'C-c a' calls your agenda (suggested org
> key), then you can do 'C-c a < a' to get the agenda restricted to
> the buffer that you are in.
Well, yes, but that still throws away all the headings. E.g.
* Task 1
** TODO Do A
** Other stuff
* Task 2
** TODO Do B
** TODO Do C
SCHEDULED: <2015-05-31 Sun>
becomes (after C-c a t):
* TODO Do A
* TODO Do B
What I would like to get is
* Task 1
** TODO Do A
* Task 2
** TODO Do B
>
>> Is there a way to create a sparse tree that shows only undated
>> TODOs (i.e., excludes anything that scheduled or has a
>> deadline)?
>
> I do not know what you mean by sparse tree,
The sparse tree is what you get with C-c \ t (org-sparse-tree). For the
above example, you get:
* Task 1
** TODO Do A
* Task 2
** TODO Do B
** TODO Do C
SCHEDULED: <2015-05-31 Sun>
so the structure is conserved like I want, but even with..
> but this excludes
> anything scheduled or with a deadline from the global todo list:
>
> #+BEGIN_SRC emacs-lisp
> (setq org-agenda-todo-ignore-scheduled 'all)
> (setq org-agenda-todo-ignore-deadlines 'all)
> #+END_SRC
.. the scheduled items are still included (because the todo-* settings
apply only to the Agenda view, not the sparse tree view).
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: Sparse tree for undated TODOs, or hierachical agenda?
2015-04-21 15:35 ` Nikolaus Rath
@ 2015-04-21 17:11 ` Jorge A. Alfaro-Murillo
2015-04-21 21:08 ` Nikolaus Rath
0 siblings, 1 reply; 12+ messages in thread
From: Jorge A. Alfaro-Murillo @ 2015-04-21 17:11 UTC (permalink / raw)
To: emacs-orgmode
Nikolaus Rath writes:
> Jorge A. Alfaro-Murillo writes:
>> If you want to restrict to your current document before
>> building the agenda use '<', so if 'C-c a' calls your agenda
>> (suggested org key), then you can do 'C-c a < a' to get the
>> agenda restricted to the buffer that you are in.
>
> Well, yes, but that still throws away all the headings. E.g.
>
> * Task 1 ** TODO Do A ** Other stuff * Task 2 ** TODO Do B **
> TODO Do C
> SCHEDULED: <2015-05-31 Sun>
>
> becomes (after C-c a t):
>
> * TODO Do A * TODO Do B
>
> What I would like to get is
>
> * Task 1 ** TODO Do A * Task 2 ** TODO Do B
>> I do not know what you mean by sparse tree,
>
> The sparse tree is what you get with C-c \ t (org-sparse-tree).
> For the above example, you get:
>
> * Task 1 ** TODO Do A * Task 2 ** TODO Do B ** TODO Do C
> SCHEDULED: <2015-05-31 Sun>
>
> so the structure is conserved like I want, but even with..
>
>> but this excludes anything scheduled or with a deadline from
>> the global todo list:
>>
>> #+BEGIN_SRC emacs-lisp
>> (setq org-agenda-todo-ignore-scheduled 'all) (setq
>> org-agenda-todo-ignore-deadlines 'all)
>> #+END_SRC
>
> .. the scheduled items are still included (because the todo-*
> settings apply only to the Agenda view, not the sparse tree
> view).
It seems to me that these are two different issues. If you want
the TODO list in the org-agenda to show your headlines you can
configure the view to show breadcrumbs (and order by category):
#+BEGIN_SRC emacs-lisp
(setq org-agenda-prefix-format
'((agenda . " %i %-12:c%?-12t% s")
(timeline . " % s")
(todo . " %i %-12:c%-24:b")
(tags . " %i %-12:c")
(search . " %i %-12:c")))
(setq org-agenda-sorting-strategy
((agenda habit-down time-up priority-down category-keep)
(todo category-keep)
(tags priority-down category-keep)
(search category-keep)))
#+END_SRC
Now, if you want to narrow the agenda (C-c a) or org-sparse-tree
(C-c /) to show TODO items not SCHEDULED or DEADLINE'd use the key
'm' and the following match:
-SCHEDULED={.+}-DEADLINE={.+}+TODO="TODO"
Best,
--
Jorge.
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: Sparse tree for undated TODOs, or hierachical agenda?
2015-04-21 17:11 ` Jorge A. Alfaro-Murillo
@ 2015-04-21 21:08 ` Nikolaus Rath
2015-04-21 23:03 ` How to match TODO items not SCHEDULED or DEADLINE'd (was: Sparse tree for undated TODOs, or hierachical agenda?) Nikolaus Rath
` (2 more replies)
0 siblings, 3 replies; 12+ messages in thread
From: Nikolaus Rath @ 2015-04-21 21:08 UTC (permalink / raw)
To: emacs-orgmode
On Apr 21 2015, jorge.alfaro-murillo@yale.edu (Jorge A. Alfaro-Murillo) wrote:
> Nikolaus Rath writes:
>
>> Jorge A. Alfaro-Murillo writes:
>>> If you want to restrict to your current document before
>>> building the agenda use '<', so if 'C-c a' calls your agenda
>>> (suggested org key), then you can do 'C-c a < a' to get the
>>> agenda restricted to the buffer that you are in.
>>
>> Well, yes, but that still throws away all the headings. E.g.
>>
>> * Task 1 ** TODO Do A ** Other stuff * Task 2 ** TODO Do B **
>> TODO Do C
>> SCHEDULED: <2015-05-31 Sun>
>>
>> becomes (after C-c a t):
>>
>> * TODO Do A * TODO Do B
>>
>> What I would like to get is
>>
>> * Task 1 ** TODO Do A * Task 2 ** TODO Do B
>
>>> I do not know what you mean by sparse tree,
>>
>> The sparse tree is what you get with C-c \ t (org-sparse-tree).
>> For the above example, you get:
>>
>> * Task 1 ** TODO Do A * Task 2 ** TODO Do B ** TODO Do C
>> SCHEDULED: <2015-05-31 Sun>
>>
>> so the structure is conserved like I want, but even with..
>>
>>> but this excludes anything scheduled or with a deadline from
>>> the global todo list:
>>>
>>> #+BEGIN_SRC emacs-lisp
>>> (setq org-agenda-todo-ignore-scheduled 'all) (setq
>>> org-agenda-todo-ignore-deadlines 'all)
>>> #+END_SRC
>>
>> .. the scheduled items are still included (because the todo-*
>> settings apply only to the Agenda view, not the sparse tree
>> view).
>
> It seems to me that these are two different issues. If you want
> the TODO list in the org-agenda to show your headlines you can
> configure the view to show breadcrumbs (and order by category):
>
> #+BEGIN_SRC emacs-lisp
> (setq org-agenda-prefix-format
> '((agenda . " %i %-12:c%?-12t% s")
> (timeline . " % s")
> (todo . " %i %-12:c%-24:b")
> (tags . " %i %-12:c")
> (search . " %i %-12:c")))
>
> (setq org-agenda-sorting-strategy
> ((agenda habit-down time-up priority-down category-keep)
> (todo category-keep)
> (tags priority-down category-keep)
> (search category-keep)))
> #+END_SRC
For me the second assignment fails with:
Debugger entered--Lisp error: (void-variable >)
(setq org-agenda-sorting-strategy > ((agenda habit-down time-up priority-down category-keep) > (todo category-keep) > (tags priority-down category-keep) > (search category-keep)))
eval((setq org-agenda-sorting-strategy > ((agenda habit-down time-up priority-down category-keep) > (todo category-keep) > (tags priority-down category-keep) > (search category-keep))) nil)
eval-last-sexp-1(nil)
eval-last-sexp(nil)
call-interactively(eval-last-sexp nil nil)
command-execute(eval-last-sexp)
If I evaluate just the first one, I'm getting the headlines as an
additional column which is better but not yet perfect.
> Now, if you want to narrow the agenda (C-c a) or org-sparse-tree
> (C-c /) to show TODO items not SCHEDULED or DEADLINE'd use the key
> 'm' and the following match:
>
> -SCHEDULED={.+}-DEADLINE={.+}+TODO="TODO"
This, however, works perfectly, thanks a lot! Is this explained anywhere
in the documentation? Because I certainly searched for it but could not
find anything.
(I'm nevertheless interested in trying out your first solution for
changing the Agenda view as well).
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
^ permalink raw reply [flat|nested] 12+ messages in thread* How to match TODO items not SCHEDULED or DEADLINE'd (was: Sparse tree for undated TODOs, or hierachical agenda?)
2015-04-21 21:08 ` Nikolaus Rath
@ 2015-04-21 23:03 ` Nikolaus Rath
2015-04-22 14:03 ` How to match TODO items not SCHEDULED or DEADLINE'd Jorge A. Alfaro-Murillo
2015-04-21 23:08 ` Sparse tree for undated TODOs, or hierachical agenda? Nikolaus Rath
2015-04-22 13:52 ` Jorge A. Alfaro-Murillo
2 siblings, 1 reply; 12+ messages in thread
From: Nikolaus Rath @ 2015-04-21 23:03 UTC (permalink / raw)
To: emacs-orgmode
On Apr 21 2015, Nikolaus Rath <Nikolaus@rath.org> wrote:
> On Apr 21 2015, jorge.alfaro-murillo@yale.edu (Jorge A. Alfaro-Murillo) wrote:
>> Now, if you want to narrow the agenda (C-c a) or org-sparse-tree
>> (C-c /) to show TODO items not SCHEDULED or DEADLINE'd use the key
>> 'm' and the following match:
>>
>> -SCHEDULED={.+}-DEADLINE={.+}+TODO="TODO"
>
> This, however, works perfectly, thanks a lot!
Actually, it seems it does not work for some cases. If I have a file
with
* TODO Item 1
* TODO Item 2
SCHEDULED: <2015-04-24 Fri>
* Heading
** TODO Subitem 1
** TODO Subitem 1
SCHEDULED: <2015-04-24 Fri>
end do the above procedure, I'm getting
* TODO Item 1
* TODO Item 2...
* Heading
** TODO Subitem 1...
Why is "Item 2" not being hidden?
Thanks,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: How to match TODO items not SCHEDULED or DEADLINE'd
2015-04-21 23:03 ` How to match TODO items not SCHEDULED or DEADLINE'd (was: Sparse tree for undated TODOs, or hierachical agenda?) Nikolaus Rath
@ 2015-04-22 14:03 ` Jorge A. Alfaro-Murillo
2015-04-22 15:49 ` Nicolas Goaziou
0 siblings, 1 reply; 12+ messages in thread
From: Jorge A. Alfaro-Murillo @ 2015-04-22 14:03 UTC (permalink / raw)
To: emacs-orgmode
Nikolaus Rath writes:
> On Apr 21 2015, Nikolaus Rath <Nikolaus@rath.org> wrote:
>> On Apr 21 2015, jorge.alfaro-murillo@yale.edu (Jorge A.
>> Alfaro-Murillo) wrote:
>>> Now, if you want to narrow the agenda (C-c a) or
>>> org-sparse-tree (C-c /) to show TODO items not SCHEDULED or
>>> DEADLINE'd use the key 'm' and the following match:
>>>
>>> -SCHEDULED={.+}-DEADLINE={.+}+TODO="TODO"
>>
>> This, however, works perfectly, thanks a lot!
>
> Actually, it seems it does not work for some cases. If I have a
> file with
>
> * TODO Item 1 * TODO Item 2
> SCHEDULED: <2015-04-24 Fri>
> * Heading ** TODO Subitem 1 ** TODO Subitem 1
> SCHEDULED: <2015-04-24 Fri>
>
> end do the above procedure, I'm getting
>
> * TODO Item 1 * TODO Item 2... * Heading ** TODO Subitem 1...
>
> Why is "Item 2" not being hidden?
That is a good question, I don't know. It fails for me as well in
the org-sparse-tree, but not in the agenda. In the agenda it only
shows Item 1 and Subitem 1, as it should. I had never used the
sparse tree, it might by what it is supposed to do, perhaps it
shows by default all entries up to a certain level. Hopefully
someone can answer, if not perhaps a new thread with just that
issue could serve as a bug report.
--
Jorge.
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: How to match TODO items not SCHEDULED or DEADLINE'd
2015-04-22 14:03 ` How to match TODO items not SCHEDULED or DEADLINE'd Jorge A. Alfaro-Murillo
@ 2015-04-22 15:49 ` Nicolas Goaziou
2015-04-22 16:10 ` Jorge A. Alfaro-Murillo
0 siblings, 1 reply; 12+ messages in thread
From: Nicolas Goaziou @ 2015-04-22 15:49 UTC (permalink / raw)
To: Jorge A. Alfaro-Murillo; +Cc: emacs-orgmode
Hello,
jorge.alfaro-murillo@yale.edu (Jorge A. Alfaro-Murillo) writes:
> Nikolaus Rath writes:
>
>> On Apr 21 2015, Nikolaus Rath <Nikolaus@rath.org> wrote:
>>> On Apr 21 2015, jorge.alfaro-murillo@yale.edu (Jorge A.
>>> Alfaro-Murillo) wrote:
>>>> Now, if you want to narrow the agenda (C-c a) or org-sparse-tree
>>>> (C-c /) to show TODO items not SCHEDULED or DEADLINE'd use the key
>>>> 'm' and the following match:
>>>>
>>>> -SCHEDULED={.+}-DEADLINE={.+}+TODO="TODO"
>>>
>>> This, however, works perfectly, thanks a lot!
>>
>> Actually, it seems it does not work for some cases. If I have a file
>> with
>>
>> * TODO Item 1 * TODO Item 2 SCHEDULED: <2015-04-24 Fri> * Heading
>> ** TODO Subitem 1 ** TODO Subitem 1 SCHEDULED: <2015-04-24 Fri>
>>
>> end do the above procedure, I'm getting
>>
>> * TODO Item 1 * TODO Item 2... * Heading ** TODO Subitem 1...
>>
>> Why is "Item 2" not being hidden?
>
> That is a good question, I don't know. It fails for me as well in the
> org-sparse-tree, but not in the agenda. In the agenda it only shows
> Item 1 and Subitem 1, as it should. I had never used the sparse tree,
> it might by what it is supposed to do, perhaps it shows by default all
> entries up to a certain level. Hopefully someone can answer, if not
> perhaps a new thread with just that issue could serve as a bug report.
If you're using development version, see `org-show-context-detail'.
Regards,
--
Nicolas Goaziou
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: How to match TODO items not SCHEDULED or DEADLINE'd
2015-04-22 15:49 ` Nicolas Goaziou
@ 2015-04-22 16:10 ` Jorge A. Alfaro-Murillo
0 siblings, 0 replies; 12+ messages in thread
From: Jorge A. Alfaro-Murillo @ 2015-04-22 16:10 UTC (permalink / raw)
To: emacs-orgmode
Nicolas Goaziou writes:
> jorge.alfaro-murillo@yale.edu (Jorge A. Alfaro-Murillo) writes:
>
>> Nikolaus Rath writes:
>>> Actually, it seems it does not work for some cases. If I have
>>> a file with
>>>
>>> * TODO Item 1 * TODO Item 2 SCHEDULED: <2015-04-24 Fri> *
>>> Heading ** TODO Subitem 1 ** TODO Subitem 1 SCHEDULED:
>>> <2015-04-24 Fri>
>>>
>>> end do the above procedure, I'm getting
>>>
>>> * TODO Item 1 * TODO Item 2... * Heading ** TODO Subitem 1...
>>>
>>> Why is "Item 2" not being hidden?
>>
>> That is a good question, I don't know. It fails for me as well
>> in the org-sparse-tree, but not in the agenda. In the agenda it
>> only shows Item 1 and Subitem 1, as it should. I had never used
>> the sparse tree, it might by what it is supposed to do, perhaps
>> it shows by default all entries up to a certain level.
>> Hopefully someone can answer, if not perhaps a new thread with
>> just that issue could serve as a bug report.
>
> If you're using development version, see
> `org-show-context-detail'.
Thank you that answers the question, that list has (default .
ancestors) in the default. Nikolaus, for the sparse trees to look
like you want, probably you want to add:
#+BEGIN_SRC emacs-lisp
(add-to-list 'org-show-context-detail '(tags-tree . minimal))
(add-to-list 'org-show-context-detail '(occur-tree . minimal))
#+END_SRC
Best,
--
Jorge.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Sparse tree for undated TODOs, or hierachical agenda?
2015-04-21 21:08 ` Nikolaus Rath
2015-04-21 23:03 ` How to match TODO items not SCHEDULED or DEADLINE'd (was: Sparse tree for undated TODOs, or hierachical agenda?) Nikolaus Rath
@ 2015-04-21 23:08 ` Nikolaus Rath
2015-04-22 13:52 ` Jorge A. Alfaro-Murillo
2 siblings, 0 replies; 12+ messages in thread
From: Nikolaus Rath @ 2015-04-21 23:08 UTC (permalink / raw)
To: emacs-orgmode
On Apr 21 2015, Nikolaus Rath <Nikolaus@rath.org> wrote:
>> Now, if you want to narrow the agenda (C-c a) or org-sparse-tree
>> (C-c /) to show TODO items not SCHEDULED or DEADLINE'd use the key
>> 'm' and the following match:
>>
>> -SCHEDULED={.+}-DEADLINE={.+}+TODO="TODO"
>
> This, however, works perfectly, thanks a lot! Is this explained anywhere
> in the documentation? Because I certainly searched for it but could not
> find anything.
Now that I knew what to look for, I finally found it myself. Here's a
link for the benefit of future people trying to Google this:
Match syntax:
http://orgmode.org/org.html#Matching-tags-and-properties
..and the special properties that automatically exist:
http://orgmode.org/org.html#Special-properties
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
^ permalink raw reply [flat|nested] 12+ messages in thread* Re: Sparse tree for undated TODOs, or hierachical agenda?
2015-04-21 21:08 ` Nikolaus Rath
2015-04-21 23:03 ` How to match TODO items not SCHEDULED or DEADLINE'd (was: Sparse tree for undated TODOs, or hierachical agenda?) Nikolaus Rath
2015-04-21 23:08 ` Sparse tree for undated TODOs, or hierachical agenda? Nikolaus Rath
@ 2015-04-22 13:52 ` Jorge A. Alfaro-Murillo
2 siblings, 0 replies; 12+ messages in thread
From: Jorge A. Alfaro-Murillo @ 2015-04-22 13:52 UTC (permalink / raw)
To: emacs-orgmode
Nikolaus Rath writes:
>>> Jorge A. Alfaro-Murillo writes:
>>
>> #+BEGIN_SRC emacs-lisp
>> (setq org-agenda-prefix-format
>> '((agenda . " %i %-12:c%?-12t% s")
>> (timeline . " % s") (todo . " %i %-12:c%-24:b")
>> (tags . " %i %-12:c") (search . " %i %-12:c")))
>>
>> (setq org-agenda-sorting-strategy
>> ((agenda habit-down time-up priority-down
>> category-keep)
>> (todo category-keep) (tags priority-down
>> category-keep) (search category-keep)))
>> #+END_SRC
>
> For me the second assignment fails with:
Sorry, I am missing a quote for the list, the second part should
be
#+BEGIN_SRC emacs-lisp
(setq org-agenda-sorting-strategy
'((agenda habit-down time-up priority-down category-keep)
(todo category-keep)
(tags priority-down category-keep)
(search category-keep)))
#+END_SRC
Best,
--
Jorge.
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2015-04-22 16:11 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-04-18 3:35 Sparse tree for undated TODOs, or hierachical agenda? Nikolaus Rath
2015-04-21 1:16 ` Nikolaus Rath
2015-04-21 14:10 ` Jorge A. Alfaro-Murillo
2015-04-21 15:35 ` Nikolaus Rath
2015-04-21 17:11 ` Jorge A. Alfaro-Murillo
2015-04-21 21:08 ` Nikolaus Rath
2015-04-21 23:03 ` How to match TODO items not SCHEDULED or DEADLINE'd (was: Sparse tree for undated TODOs, or hierachical agenda?) Nikolaus Rath
2015-04-22 14:03 ` How to match TODO items not SCHEDULED or DEADLINE'd Jorge A. Alfaro-Murillo
2015-04-22 15:49 ` Nicolas Goaziou
2015-04-22 16:10 ` Jorge A. Alfaro-Murillo
2015-04-21 23:08 ` Sparse tree for undated TODOs, or hierachical agenda? Nikolaus Rath
2015-04-22 13:52 ` Jorge A. Alfaro-Murillo
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).