[-- Attachment #1: Type: text/plain, Size: 707 bytes --] I just pulled for the first time in a while and found I get question marks in my agenda view instead of the former use of the file name (see attached). I did a bunch of git pulling/make cleaning/making, and traced it to this commit from Nicholas: - 80bccca4e249cbb5812963863ccffbdcf4b25edd Commit c1a744659d2b44c067ecb195b3e5d51e837bddd is working properly. I verified with a minimal config containing only: (add-to-list 'load-path "~/.elisp/org.git/lisp/") My test file contained: * TODO something * TODO something else Process: - emacs -Q - M-x load-file [RET] /path/to/min-config - M-x org-agenda-file-to-front - M-x org-agenda [RET] t I get the attached view. Thanks for any suggestions, John [-- Attachment #2: 2015-04-01_121525.png --] [-- Type: image/png, Size: 46361 bytes --]
Hello,
John Hendy <jw.hendy@gmail.com> writes:
> I just pulled for the first time in a while and found I get question
> marks in my agenda view instead of the former use of the file name
> (see attached). I did a bunch of git pulling/make cleaning/making, and
> traced it to this commit from Nicholas:
> - 80bccca4e249cbb5812963863ccffbdcf4b25edd
>
> Commit c1a744659d2b44c067ecb195b3e5d51e837bddd is working properly.
>
> I verified with a minimal config containing only:
>
> (add-to-list 'load-path "~/.elisp/org.git/lisp/")
>
> My test file contained:
>
> * TODO something
>
> * TODO something else
>
> Process:
> - emacs -Q
> - M-x load-file [RET] /path/to/min-config
> - M-x org-agenda-file-to-front
> - M-x org-agenda [RET] t
Fixed in 22bf1b8ae3c2842945b9b9d9ab2ca203eae17946. Thank you.
Regards,
--
Nicolas Goaziou
Confirmed to be working great again. Thanks for the speedy response (as always)!
John
On Wed, Apr 1, 2015 at 3:44 PM, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> Hello,
>
> John Hendy <jw.hendy@gmail.com> writes:
>
>> I just pulled for the first time in a while and found I get question
>> marks in my agenda view instead of the former use of the file name
>> (see attached). I did a bunch of git pulling/make cleaning/making, and
>> traced it to this commit from Nicholas:
>> - 80bccca4e249cbb5812963863ccffbdcf4b25edd
>>
>> Commit c1a744659d2b44c067ecb195b3e5d51e837bddd is working properly.
>>
>> I verified with a minimal config containing only:
>>
>> (add-to-list 'load-path "~/.elisp/org.git/lisp/")
>>
>> My test file contained:
>>
>> * TODO something
>>
>> * TODO something else
>>
>> Process:
>> - emacs -Q
>> - M-x load-file [RET] /path/to/min-config
>> - M-x org-agenda-file-to-front
>> - M-x org-agenda [RET] t
>
> Fixed in 22bf1b8ae3c2842945b9b9d9ab2ca203eae17946. Thank you.
>
> Regards,
>
> --
> Nicolas Goaziou
May be related:
My standard agenda view pulls in the last #+CATEGORY: line of a file only.
In my case *all* my TODOs are labelled "Urlaub" ("holidays") now.
Reads nicely but sadly not quite true :-)
"Urlaub" happens to be the last CATEGORY defined in my todo.org.
Still happens after this fix.
emacs and org-mode freshly compiled from git.
Regards
Detlef
Am Thu, 2 Apr 2015 21:40:18 -0500
schrieb John Hendy <jw.hendy@gmail.com>:
> Confirmed to be working great again. Thanks for the speedy response
> (as always)!
>
> John
>
> On Wed, Apr 1, 2015 at 3:44 PM, Nicolas Goaziou
> <mail@nicolasgoaziou.fr> wrote:
> > Hello,
> >
> > John Hendy <jw.hendy@gmail.com> writes:
> >
> >> I just pulled for the first time in a while and found I get
> >> question marks in my agenda view instead of the former use of the
> >> file name (see attached). I did a bunch of git pulling/make
> >> cleaning/making, and traced it to this commit from Nicholas:
> >> - 80bccca4e249cbb5812963863ccffbdcf4b25edd
> >>
> >> Commit c1a744659d2b44c067ecb195b3e5d51e837bddd is working properly.
> >>
> >> I verified with a minimal config containing only:
> >>
> >> (add-to-list 'load-path "~/.elisp/org.git/lisp/")
> >>
> >> My test file contained:
> >>
> >> * TODO something
> >>
> >> * TODO something else
> >>
> >> Process:
> >> - emacs -Q
> >> - M-x load-file [RET] /path/to/min-config
> >> - M-x org-agenda-file-to-front
> >> - M-x org-agenda [RET] t
> >
> > Fixed in 22bf1b8ae3c2842945b9b9d9ab2ca203eae17946. Thank you.
> >
> > Regards,
> >
> > --
> > Nicolas Goaziou
>
>
Hello,
Detlef Steuer <detlef.steuer@gmx.de> writes:
> May be related:
>
> My standard agenda view pulls in the last #+CATEGORY: line of a file only.
>
> In my case *all* my TODOs are labelled "Urlaub" ("holidays") now.
> Reads nicely but sadly not quite true :-)
This is to be expected. You can set :CATEGORY: node property in subtrees
if needed.
Regards,
--
Nicolas Goaziou
Am Fri, 03 Apr 2015 17:59:16 +0200
schrieb Nicolas Goaziou <mail@nicolasgoaziou.fr>:
> This is to be expected. You can set :CATEGORY: node property in
> subtrees if needed.
So this beheaviour changed at some point in the past?
To be sure:
I have a file (modulo scheduling information)
* Line1
#+CATEGORY: one
** TODO very important
* Line2
#+CATEGORY: two
** TODO more stuff
It is expected to see both TODOs in an agenda as:
two: very important
two: more stuff
?
Detlef
Detlef Steuer <detlef.steuer@gmx.de> writes: > Am Fri, 03 Apr 2015 17:59:16 +0200 > schrieb Nicolas Goaziou <mail@nicolasgoaziou.fr>: > >> This is to be expected. You can set :CATEGORY: node property in >> subtrees if needed. > > So this beheaviour changed at some point in the past? This behaviour was long deprecated. Starting from Org 5.14 (released in 2008), the manual stated @cindex #+CATEGORY The category is a broad label assigned to each agenda item. By default, the category is simply derived from the file name, but you can also specify it with a special line in the buffer, like this@footnote{For backward compatibility, the following also works: if there are several such lines in a file, each specifies the category for the text below it. The first category also applies to any text before the first CATEGORY line. However, using this method is @emph{strongly} deprecated as it is incompatible with the outline structure of the document. The correct method for setting multiple categories in a buffer is using a property.}: I only removed the backward compatibility recently. I dropped a note in ORG-NEWS. > To be sure: > > I have a file (modulo scheduling information) > > * Line1 > #+CATEGORY: one > ** TODO very important > > * Line2 > #+CATEGORY: two > ** TODO more stuff > > It is expected to see both TODOs in an agenda as: > > two: very important > two: more stuff Yes, it is. This should be * Line1 :PROPERTIES: :CATEGORY: one :END: ** TODO very important * Line2 :PROPERTIES: :CATEGORY: two :END: ** TODO more stuff Regards,
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> This should be
>
> * Line1
> :PROPERTIES:
> :CATEGORY: one
> :END:
Oh ! I just use the old syntax and did not notice this changed
/recently/.
Thank you for the clarification.
-- Xavier.