Org-agenda-leaders

Org-agenda-leaders

[Uwe Jochum]

Hi all,

when I switched to the orgmode 8.3.2 quite a lot of entries in my weekly 
agenda disappeared. This seems to be related to the fact that I renamed 
the agenda leaders like so:

  '(org-agenda-deadline-leaders (quote ("FRIST:  " "In %3d d.: ")))

  '(org-agenda-scheduled-leaders (quote ("TERMIN: " "TERMIN.%2dx: ")))

So renaming a scheduled item with the leader "SCHEDULED" brings it back 
into the agenda list. Hm. I wanted Orgmode to speak German with me, and it 
worked perfectly up to orgmode 8.2. or so. Is someone out there who can 
confirm this new behavior of orgmode 8.3.? Is it a bug or did I miss some 
change in the configuration of orgmode?

Thanks in advance for any hint.

Best,

Uwe Jochum

Re: Org-agenda-leaders

[Matt Lundin]

Uwe Jochum <uwe.jochum@uni-konstanz.de> writes:

> Hi all,
>
> when I switched to the orgmode 8.3.2 quite a lot of entries in my
> weekly agenda disappeared. This seems to be related to the fact that I
> renamed the agenda leaders like so:
>
>  '(org-agenda-deadline-leaders (quote ("FRIST:  " "In %3d d.: ")))
>
>  '(org-agenda-scheduled-leaders (quote ("TERMIN: " "TERMIN.%2dx: ")))
>

I cannot replicate this. The leaders above (FRIST, TERMIN) appear
properly on my machine.

Org-mode version 8.3.2 (release_8.3.2-204-g30ec97)
Emacs: "25.0.50.4"

Matt

Re: Org-agenda-leaders

[Uwe Jochum]

Dear Matt,

thanks! I'll try a fresh install of Emacs and orgmode this weekend and see 
what will happen. My Emacs is 24.3.1 on a Linux Mint machine.

Besten Dank,

Uwe Jochum

Matt Lundin schrieb am 2015-10-21 um 17:03 Uhr:

> Uwe Jochum <uwe.jochum@uni-konstanz.de> writes:
>
>> Hi all,
>>
>> when I switched to the orgmode 8.3.2 quite a lot of entries in my
>> weekly agenda disappeared. This seems to be related to the fact that I
>> renamed the agenda leaders like so:
>>
>>  '(org-agenda-deadline-leaders (quote ("FRIST:  " "In %3d d.: ")))
>>
>>  '(org-agenda-scheduled-leaders (quote ("TERMIN: " "TERMIN.%2dx: ")))
>>
>
> I cannot replicate this. The leaders above (FRIST, TERMIN) appear
> properly on my machine.
>
> Org-mode version 8.3.2 (release_8.3.2-204-g30ec97)
> Emacs: "25.0.50.4"
>
> Matt
>
>

Re: Org-agenda-leaders

[Uwe Jochum]

Hi Matt and all,

here is (probably) the solution to this problem:

As I said, I have this in my .emacs:

'(org-agenda-deadline-leaders (quote ("FRIST:  " "In %3d d.: ")))

'(org-agenda-scheduled-leaders (quote ("TERMIN: " "TERMIN.%2dx: ")))

Up to orgmode 8.2.something this worked globally in orgmode, i.e. I could 
use an entry like this in my org-files:

* TODO Do Something
TERMIN: <2015-10-10 Sa>

This was parsed and produced an output in the agenda list like so:

Samstag 10 October 2015
TERMIN.1x: Do Something

But now in orgmode 8.3.2 the leaders are no longer globally working, but 
only for producing the agenda list. Therefore it is necessary to use the 
English words SCHEDULED and DEADLINE in the org-files, like so:

* TODO Do Something
SCHEDULED: <2015-10-10 Sa>

And this gives (the .emacs file beeing unchanged)

Samstag 10 Oktober 2015
TERMIN.1x: Do Something

So obviously the parser was changed or in the earlier orgmode-versions I 
used a feature that was not intended (I mean the agenda-leader-text as a 
text for the org-file-entries).

I hope this clears the point a little bit.

I switched to the English words SCHEDULED and DEADLINE in the org-files. 
So, as for me, that's o.k.

Thanks a lot,

Uwe Jochum

Re: Org-agenda-leaders

[Nick Dokos]

Uwe Jochum <uwe.jochum@uni-konstanz.de> writes:

> Hi Matt and all,
>
> here is (probably) the solution to this problem:
>
> As I said, I have this in my .emacs:
>
> '(org-agenda-deadline-leaders (quote ("FRIST:  " "In %3d d.: ")))
>
> '(org-agenda-scheduled-leaders (quote ("TERMIN: " "TERMIN.%2dx: ")))
>
> Up to orgmode 8.2.something this worked globally in orgmode, i.e. I
> could use an entry like this in my org-files:
>
> * TODO Do Something
> TERMIN: <2015-10-10 Sa>
>
> This was parsed and produced an output in the agenda list like so:
>
> Samstag 10 October 2015
> TERMIN.1x: Do Something
>
> But now in orgmode 8.3.2 the leaders are no longer globally working,
> but only for producing the agenda list. Therefore it is necessary to
> use the English words SCHEDULED and DEADLINE in the org-files, like
> so:
>
> * TODO Do Something
> SCHEDULED: <2015-10-10 Sa>
>
> And this gives (the .emacs file beeing unchanged)
>
> Samstag 10 Oktober 2015
> TERMIN.1x: Do Something
>
> So obviously the parser was changed or in the earlier orgmode-versions
> I used a feature that was not intended (I mean the agenda-leader-text
> as a text for the org-file-entries).
>
> I hope this clears the point a little bit.
>
> I switched to the English words SCHEDULED and DEADLINE in the
> org-files. So, as for me, that's o.k.
>
> Thanks a lot,
>

,----
| (defconst org-clock-string "CLOCK:"
|   "String used as prefix for timestamps clocking work hours on an item.")
| 
| (defvar org-closed-string "CLOSED:"
|   "String used as the prefix for timestamps logging closing a TODO entry.")
| 
| (defvar org-deadline-string "DEADLINE:"
|   "String to mark deadline entries.
| A deadline is this string, followed by a time stamp.  Should be a word,
| terminated by a colon.  You can insert a schedule keyword and
| a timestamp with \\[org-deadline].")
| 
| (defvar org-scheduled-string "SCHEDULED:"
|   "String to mark scheduled TODO entries.
| A schedule is this string, followed by a time stamp.  Should be a word,
| terminated by a colon.  You can insert a schedule keyword and
| a timestamp with \\[org-schedule].")
`----

Try redefining some or all of these strings.

-- 
Nick

Re: Org-agenda-leaders

[Nicolas Goaziou]

Hello,

Nick Dokos <ndokos@gmail.com> writes:

> ,----
> | (defconst org-clock-string "CLOCK:"
> |   "String used as prefix for timestamps clocking work hours on an item.")
> | 
> | (defvar org-closed-string "CLOSED:"
> |   "String used as the prefix for timestamps logging closing a TODO entry.")
> | 
> | (defvar org-deadline-string "DEADLINE:"
> |   "String to mark deadline entries.
> | A deadline is this string, followed by a time stamp.  Should be a word,
> | terminated by a colon.  You can insert a schedule keyword and
> | a timestamp with \\[org-deadline].")
> | 
> | (defvar org-scheduled-string "SCHEDULED:"
> |   "String to mark scheduled TODO entries.
> | A schedule is this string, followed by a time stamp.  Should be a word,
> | terminated by a colon.  You can insert a schedule keyword and
> | a timestamp with \\[org-schedule].")
> `----
>
> Try redefining some or all of these strings.

Please don't. They should be defconst and are kept as defvar for
historical reasons.

Regards,

-- 
Nicolas Goaziou

Re: Org-agenda-leaders

[Nick Dokos]

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Hello,
>
> Nick Dokos <ndokos@gmail.com> writes:
>
>> ,----
>> | (defconst org-clock-string "CLOCK:"
>> |   "String used as prefix for timestamps clocking work hours on an item.")
>> | 
>> | (defvar org-closed-string "CLOSED:"
>> |   "String used as the prefix for timestamps logging closing a TODO entry.")
>> | 
>> | (defvar org-deadline-string "DEADLINE:"
>> |   "String to mark deadline entries.
>> | A deadline is this string, followed by a time stamp.  Should be a word,
>> | terminated by a colon.  You can insert a schedule keyword and
>> | a timestamp with \\[org-deadline].")
>> | 
>> | (defvar org-scheduled-string "SCHEDULED:"
>> |   "String to mark scheduled TODO entries.
>> | A schedule is this string, followed by a time stamp.  Should be a word,
>> | terminated by a colon.  You can insert a schedule keyword and
>> | a timestamp with \\[org-schedule].")
>> `----
>>
>> Try redefining some or all of these strings.
>
> Please don't. They should be defconst and are kept as defvar for
> historical reasons.
>

Oops - sorry: I didn't realize that. I didn't even notice the CLOCK
defconst. As a matter of curiosity, what's the back story here?

-- 
Nick

Re: Org-agenda-leaders

[Nicolas Goaziou]

Nick Dokos <ndokos@gmail.com> writes:

> Oops - sorry: I didn't realize that. I didn't even notice the CLOCK
> defconst. As a matter of curiosity, what's the back story here?

Backward compatibility. What else? A defconst prevent anyone from using
anything else than "DEADLINE:" and "SCHEDULED:" (I cannot remember
exactly, but even though you can still modify them, it breaks something
elsewhere).

With a defvar, we tolerate users on the dark side of the syntax. But
really, no one should modify these keywords.

Regards,