Re: [O] org-stuck-projects confuses a "Next" heading with the NEXT keyword

2017-01-24 Thread Nicolas Goaziou
Hello,

Matt Lundin  writes:

> I find that this commit (7c3e0b0fdfdc0cf1a4724cffe17b6bb160278247)
> causes Org mode no longer to identify stuck projects correctly.
>
> Steps to reproduce:
>
> I am using emacs version 25.1.1 and the most recent commit in the Org
> mode repo.
>
> /usr/bin/emacs -Q -l ~/minimal.el
>
> minimal.el contains...
>
> (add-to-list 'load-path "~/org-mode/lisp/")
> (add-to-list 'load-path "~/org-mode/contrib/lisp/")
>
> (require 'org)
>
> (setq org-agenda-files '("~/config/test.org"))
>
>
> ...and test.org contains...
>
> #+TODO: TODO NEXT | DONE
>
> * Headline
> ** This project should not be stuck
> *** TODO A next action
> *** NEXT Another one

Fixed. Thank you.

Regards,

-- 
Nicolas Goaziou



Re: [O] org-stuck-projects confuses a "Next" heading with the NEXT keyword

2017-01-24 Thread Matt Lundin
Hi Nicholas,

Nicolas Goaziou  writes:

> Hello,
>
> Guy Mayraz  writes:
>
>> I want every project to have a NEXT or WAIT keyword, and have defined
>> org-stuck-projects as follows:
>>
>> (setq org-stuck-projects '("+LEVEL=2/-INACTIVE-DONE" ("NEXT" "WAIT") nil
>> ""))
>>
>> It mostly works, but it does not identify as stuck a project that has a
>> "Next items" subheading and no NEXT keyword.
>
> Fixed. Thank you.

I find that this commit (7c3e0b0fdfdc0cf1a4724cffe17b6bb160278247)
causes Org mode no longer to identify stuck projects correctly.

Steps to reproduce:

I am using emacs version 25.1.1 and the most recent commit in the Org
mode repo.

/usr/bin/emacs -Q -l ~/minimal.el

minimal.el contains...

--8<---cut here---start->8---
(add-to-list 'load-path "~/org-mode/lisp/")
(add-to-list 'load-path "~/org-mode/contrib/lisp/")

(require 'org)

(setq org-agenda-files '("~/config/test.org"))
--8<---cut here---end--->8---

...and test.org contains...

--8<---cut here---start->8---
#+TODO: TODO NEXT | DONE

* Headline
** This project should not be stuck
*** TODO A next action
*** NEXT Another one
--8<---cut here---end--->8---

I am using the default value of org-stuck-projects:

--8<---cut here---start->8---
org-stuck-projects is a variable defined in ‘org-agenda.el’.
Its value is ("+LEVEL=2/-DONE" ("TODO" "NEXT" "NEXTACTION") nil "")
--8<---cut here---end--->8---

M-x org-agenda-list-stuck-projects produces the following:

--8<---cut here---start->8---
List of stuck projects: 
  test:   This project should not be stuck
--8<---cut here---end--->8---

Thanks,
Matt




Re: [O] org-stuck-projects confuses a "Next" heading with the NEXT keyword

2017-01-22 Thread Nicolas Goaziou
Hello,

Guy Mayraz  writes:

> I want every project to have a NEXT or WAIT keyword, and have defined
> org-stuck-projects as follows:
>
> (setq org-stuck-projects '("+LEVEL=2/-INACTIVE-DONE" ("NEXT" "WAIT") nil
> ""))
>
> It mostly works, but it does not identify as stuck a project that has a
> "Next items" subheading and no NEXT keyword.

Fixed. Thank you.

Regards,

-- 
Nicolas Goaziou



[O] org-stuck-projects confuses a "Next" heading with the NEXT keyword

2017-01-18 Thread Guy Mayraz
I want every project to have a NEXT or WAIT keyword, and have defined
org-stuck-projects as follows:

(setq org-stuck-projects '("+LEVEL=2/-INACTIVE-DONE" ("NEXT" "WAIT") nil
""))

It mostly works, but it does not identify as stuck a project that has a
"Next items" subheading and no NEXT keyword.

In case this is relevant, I have org-occur-case-fold-search set to 'smart,
and this setting works as expected for org-occur, but not for
org-stuck-projects.

Thanks!!

Guy