FILE special property?

FILE special property?

[Boyan Penkov]

Hello,

I’m looking to set up a search string using the FILE special property, but cannot get the syntax right.  This is as part of setting up org-stuck-projects.

If the file is in ~/todos/myTodos.org, and I want all the entries with heading 1, will 

(setq org-stuck-projects
      ‘(“+FILE="~/todos/myTodos.org"+LEVEL=1" ("NEXT" "TODO") nil "”))

work, or am I missing quotes there?

Thanks!

--
Boyan Penkov
www.boyanpenkov.com

Re: FILE special property?

[Alexander Baier]

On 2014-05-16 22:12 Boyan Penkov wrote:
> (setq org-stuck-projects
>       ‘(“+FILE="~/todos/myTodos.org"+LEVEL=1" ("NEXT" "TODO") nil "”))

I have never used this feature, but this first element look odd to
me. I would try this: “+FILE=\"~/todos/myTodos.org\"+LEVEL=1".

HTH,
-- 
Alexander Baier

Re: FILE special property?

[Boyan Penkov]

[-- Attachment #1: Type: text/plain, Size: 985 bytes --]

Thanks for your help, Alex.

The backslashes do get the string to evaluate correctly (now the value of org-stuck-projects is indeed set to what you’d think it would be set to, where the first element is a string), but this does not yield the right output — C-c # still yields no output, and I do know there are projects I define as unfinished in the relevant file.

When I crop out the +FILE=… part of the string, I get the output I’m expecting, so I’m pretty sure my problem is with the syntax of the FILE selector.

Thanks!
--
Boyan Penkov
www.boyanpenkov.com

On May 16, 2014, at 5:10 PM, Alexander Baier <alexander.baier@mailbox.org> wrote:

> On 2014-05-16 22:12 Boyan Penkov wrote:
>> (setq org-stuck-projects
>>      ‘(“+FILE="~/todos/myTodos.org"+LEVEL=1" ("NEXT" "TODO") nil "”))
> 
> I have never used this feature, but this first element look odd to
> me. I would try this: “+FILE=\"~/todos/myTodos.org\"+LEVEL=1".
> 
> HTH,
> -- 
> Alexander Baier


[-- Attachment #2: Type: text/html, Size: 2059 bytes --]

Re: FILE special property?

[Nick Dokos]

Boyan Penkov <boyan.penkov@gmail.com> writes:

> Thanks for your help, Alex.
>
> The backslashes do get the string to evaluate correctly (now the value of org-stuck-projects is indeed set to what you’d think it would be set to, where the first element is a
> string), but this does not yield the right output — C-c # still yields no output, and I do know there are projects I define as unfinished in the relevant file.
>
> When I crop out the +FILE=… part of the string, I get the output I’m expecting, so I’m pretty sure my problem is with the syntax of the FILE selector.
>

~ is bash syntax. Try replacing it with the full path of your home
directory.

> Thanks!
> --
> Boyan Penkov
> www.boyanpenkov.com
>
> On May 16, 2014, at 5:10 PM, Alexander Baier <alexander.baier@mailbox.org> wrote:
>
>     On 2014-05-16 22:12 Boyan Penkov wrote:
>    
>         (setq org-stuck-projects
>              ‘(“+FILE="~/todos/myTodos.org"+LEVEL=1" ("NEXT" "TODO") nil "”))
>
>     I have never used this feature, but this first element look odd to
>     me. I would try this: “+FILE=\"~/todos/myTodos.org\"+LEVEL=1".
>    
>     HTH,
>     --
>     Alexander Baier
>

-- 
Nick