Re: [O] Agenda bug
Nicolas Goaziou writes: > Could you provide an ECM? I tried to set `org-agenda-files' to a file > containing the three lines above, and launched an agenda view, without > error. So, what are the steps required to exhibit a failure? Apologies. It's an org version problem on my end. There is no error with org 9.1. Somehow that machine was never upgraded or got restored to an old version. It was still on 8.2. -- Robert Horn rjh...@alum.mit.edu
Re: [O] Agenda bug
Hello, Robert Horn writes: > I discovered that the lines ( the body of a headline): > *** real headline >* example >:SCHEDULED: > > cause agenda processing to fail. Could you provide an ECM? I tried to set `org-agenda-files' to a file containing the three lines above, and launched an agenda view, without error. So, what are the steps required to exhibit a failure? Regards, -- Nicolas Goaziou
Re: [O] Agenda bug
Eric S Fraga writes: > On Tuesday, 6 Mar 2018 at 11:23, Robert Horn wrote: >> I discovered that the lines ( the body of a headline): >> *** real headline >>* example >>:SCHEDULED: >> >> cause agenda processing to fail. It tries to parse as a >> timestamp. The parser used by agenda appears not to enforce the >> requirement that headlines begin with asterisks on the left margin. > > I think the issue is that SCHEDULED and DEADLINE entries must appear > immediately after the headline. You have a line (* example) in between > the SCHEDULED line and the headline. You have characterized the bug. That ":SCHEDULED:" should not have been considered a SCHEDULED entry. It should have been ignored, based on the description for org format in the manual. I was putting together an example for someone and was composing a full example of an org file. I just stumbled across this when trying various forms of verbatim, code, and other blocks. I was not expecting the agenda display and processing to completely fail. I created my example by eliminating one of the colons and explaining that in a real org file you would need the colon. But that leaves the bug that this particular error causes agenda creation to fail. I was expecting the parser to treat the SCHEDULED line as just more body text, and ignore it. -- Robert Horn rjhorn...@gmail.com
Re: [O] Agenda bug
On Tuesday, 6 Mar 2018 at 11:23, Robert Horn wrote: > I discovered that the lines ( the body of a headline): > *** real headline >* example >:SCHEDULED: > > cause agenda processing to fail. It tries to parse as a > timestamp. The parser used by agenda appears not to enforce the > requirement that headlines begin with asterisks on the left margin. I think the issue is that SCHEDULED and DEADLINE entries must appear immediately after the headline. You have a line (* example) in between the SCHEDULED line and the headline. -- Eric S Fraga via Emacs 27.0.50, Org release_9.1.6-191-g90607d signature.asc Description: PGP signature
[O] Agenda bug
I discovered that the lines ( the body of a headline): *** real headline * example :SCHEDULED: cause agenda processing to fail. It tries to parse as a timestamp. The parser used by agenda appears not to enforce the requirement that headlines begin with asterisks on the left margin. Removing either the leading colon or the asterisk on example fixes the problem. Regular display parsing does not get confused. The highlighting and font changes do not consider the " * example" to be a headline. -- Robert Horn rjh...@alum.mit.edu
Re: [O] Agenda bug: time conflict between headline and scheduled date
Samuel Wales writes: > But the problem of grabbing a time from the headline is solvable: > > (setq org-agenda-search-headline-for-time nil) Indeed, thanks a lot for the pointers! -- Bastien, who wonders why all metaphysical problems cannot be solved by setting an Org variable.
Re: [O] Agenda bug: time conflict between headline and scheduled date
Hi Huy, I depend on inactive timestamps in headlines, because they are useful when the entries are folded. I sort by time, which eliminates the need for date trees. But the problem of grabbing a time from the headline is solvable: (setq org-agenda-search-headline-for-time nil) Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. ANYBODY can get it. There is no hope without action.
Re: [O] Agenda bug: time conflict between headline and scheduled date
Hi Huy, Huy writes: > there's a bug when I have a task like this: > > * Test [2012-12-26 Wed 22:24] > SCHEDULED: <2012-12-25 Wed> > > Note that the inactive date has a time in the headline, but the schedule > date doesn't. > > When I run the agenda, I get this: > > Tuesday25 December 2012 > GTD:22:24.. Scheduled: Test [2012-12-26 Wed 22:24] > > The time should not be extracted from the non-scheduled timestamp, > right? Yes. Mixing time-stamps for a single entry is known to cause problems, and this is one of them. Better to put the inactive time-stamp outside of the headline. Best, -- Bastien
Re: [O] Agenda bug: q & x keys are swapped?
Hi Huy, Huy writes: > It seems that org-agenda-quit (q) and org-agenda-exit (x) are swapped. > 'q' wants to close my the buffers loaded for the agenda. > > Strange. I cannot reproduce this. Does anyone can? Thanks, -- Bastien
Re: [O] Agenda bug: 'now' is on the wrong day
Huy, please check your setting for org-extend-today-until: The hour when your day really ends. Must be an integer. This has influence for the following applications: - When switching the agenda to "today". It it is still earlier than the time given here, the day recognized as TODAY is actually yesterday. .j. On Thu, Dec 27, 2012 at 01:20:38AM -0800, Huy wrote: > It's 1:17am over here. > And when I pop up the agenda and then hit 'l', it says: >1:17.. now - - - - - - - - - - - - - - - - - - - - - - - - > - > > but it's on the wrong day: yesterday.
[O] Agenda bug: 'now' is on the wrong day
It's 1:17am over here. And when I pop up the agenda and then hit 'l', it says: 1:17.. now - - - - - - - - - - - - - - - - - - - - - - - - - but it's on the wrong day: yesterday. I'm running 7.9.2 on emacs 24.2.1 on OS X Thanks, Huy
[O] Agenda bug: q & x keys are swapped?
It seems that org-agenda-quit (q) and org-agenda-exit (x) are swapped. 'q' wants to close my the buffers loaded for the agenda. Strange. I'm running 7.9.2 on emacs 24.2.1 on OS X Thanks, Huy
[O] Agenda bug: time conflict between headline and scheduled date
task Reply-To: Hi, there's a bug when I have a task like this: * Test [2012-12-26 Wed 22:24] SCHEDULED: <2012-12-25 Wed> Note that the inactive date has a time in the headline, but the schedule date doesn't. When I run the agenda, I get this: Tuesday25 December 2012 GTD:22:24.. Scheduled: Test [2012-12-26 Wed 22:24] The time should not be extracted from the non-scheduled timestamp, right? I'm running 7.9.2 on emacs 24.2.1 on OS X Thanks, Huy
Re: [O] agenda bug
Hi,
Nicholas Putnam writes:
> I get a strange error message when trying to view the agenda for the
> current day/week with C-c a a :
>
> org-agenda-highlight-todo: Args out of range: #(" diary: " 0 14
> (org-category "diary" tags nil org-highest-priority 65
> org-lowest-priority 67 time-of-day nil ...)), 26, 30
>
> I can make it go away by deleting the following from the end of one of
> my agenda files, or changing the date + or - one day.
>
> ** <2011-04-19 Tue>
>
> Why would this break the agenda view?
It would be nice to have some more informations.
Is this exactly the line you have in your agenda?
Version orgmode, emacs etc.?
Does the same happen when the item is not at the end of that agenda
file, but say somewhere in the middle?
See: http://orgmode.org/manual/Feedback.html or
(info "(org)Feedback") <--- `C-x C-e' here
Re: [O] agenda bug
Nicholas Putnam wrote:
> I get a strange error message when trying to view the agenda for the
> current day/week with C-c a a :
>
> org-agenda-highlight-todo: Args out of range: #(" diary: " 0 14
> (org-category "diary" tags nil org-highest-priority 65
> org-lowest-priority 67 time-of-day nil ...)), 26, 30
>
> I can make it go away by deleting the following from the end of one of
> my agenda files, or changing the date + or - one day.
>
> ** <2011-04-19 Tue>
>
> Why would this break the agenda view?
>
Who knows? A backtrace would help however: M-x toggle-debug-on-error and
trigger the error again.
Nick
PS. I sound like a broken record :-)
[O] agenda bug
I get a strange error message when trying to view the agenda for the current
day/week with C-c a a :
org-agenda-highlight-todo: Args out of range: #(" diary: " 0 14
(org-category "diary" tags nil org-highest-priority 65 org-lowest-priority
67 time-of-day nil ...)), 26, 30
I can make it go away by deleting the following from the end of one of my
agenda files, or changing the date + or - one day.
** <2011-04-19 Tue>
Why would this break the agenda view?
Nik
