Re: [O] property matching in org-agenda-custom-commands

2019-04-05 Thread Matt Price
Ah, I was being pretty stupid. Thanks to both Thomas and Nick. Is it possible to specify "current buffer only" in the definition of a shortcut, but still produce an agenda, rather than a sparse tree? I find the agenda in some ways easier to navigate than the sparse tree. Also (side note) I'm hav

Re: [O] property matching in org-agenda-custom-commands

2019-04-05 Thread Thomas Plass
Matt, Matt Price wrote at 13:31 on April 5, 2019: : : ("F" "Failing Students in Current Buffer Only" tags-tree "+GRADE=\"0\"") : : However, this seems to choke, and the agenda is not generated. Works as advertised (docstring'ed?), I think. The 'tags-tree creates a sparse tree, not an agenda.

Re: [O] property matching in org-agenda-custom-commands

2019-04-05 Thread Nick Dokos
Matt Price writes: > Embarassed that I still don't really know how to use the agenda commands > after all this time :-( Ditto - I need to read the doc for org-agenda-custom-commands every time I try to use it. > > I have a bunch of trees that look in part like this: > * Asisgnment 1 > ** Stude

[O] property matching in org-agenda-custom-commands

2019-04-05 Thread Matt Price
Embarassed that I still don't really know how to use the agenda commands after all this time :-( I have a bunch of trees that look in part like this: * Asisgnment 1 ** Student A :PROPERTIES: :GRADE: 0 :END: I would like to store a search in org-agenda-custom-commands. I generated it initially wit

Re: [O] Python source block and :dir header arg

2019-04-05 Thread John Kitchin
I updated to the latest org, and I am not sure if you are seeing a bug. You might need to fix the space between : and session in your example, and name the session something. Also, you need to make sure the directory exists. This example works as expected for me: #+begin_src python :results output