emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Francesco Pizzolante" <fpz-djc/iPCCuDYQheJpep6IedvLeJWuRmrY@public.gmane.org>
To: Nicolas Goaziou <mail-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org>
Cc: mailing-list-org-mode
	<public-emacs-orgmode-mXXj517/zsQ-wOFGN7rlS/M9smdsby/KFg@public.gmane.org>,
	Francesco Pizzolante
	<public-fpz-djc/iPCCuDYQheJpep6IedvLeJWuRmrY-wOFGN7rlS/M9smdsby/KFg@public.gmane.org>
Subject: Re: [BUG] Entries from Org code blocks appear in agenda
Date: Tue, 09 Sep 2014 11:35:57 +0200	[thread overview]
Message-ID: <87iokxrv9e.fsf@somewhere.org> (raw)
In-Reply-To: <87y4tznp8r.fsf-6L+WB3rwWSY7o+4O0k2oReFciLI1ps7f@public.gmane.org> (Nicolas Goaziou's message of "Thu, 04 Sep 2014 21:45:56 +0200")



Hi Nicolas,

>> I noticed that entries from Org code blocks are erroneously displayed in
>> the agenda.
>>
>> Here's a very simple Org example in order to reproduce it
>> (my-simple-test.org):
>>
>> * Test
>>
>> #+BEGIN_SRC org ,SCHEDULED: <2014-09-04 Thu 10:00> #+END_SRC
>
> This is a known bug that would require to use the parser in
> "org-agenda.el" for a proper fix.
>
> Meanwhile, I wrote a workaround. Would you mind testing it (note: it
> applies on maint, probably not on master without conflicts).

Thanks for the patch.

I just applied and tested it on org-plus-contrib-20140908 from Elpa but
the workaround does not work as I can still see the erroneous headings
appearing in the agenda.

Regards,
 Francesco

      parent reply	other threads:[~2014-09-09  9:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-04 12:41 [BUG] Entries from Org code blocks appear in agenda Francesco Pizzolante
2014-09-04 19:45 ` Nicolas Goaziou
     [not found]   ` <87y4tznp8r.fsf-6L+WB3rwWSY7o+4O0k2oReFciLI1ps7f@public.gmane.org>
2014-09-09  9:35     ` Francesco Pizzolante [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87iokxrv9e.fsf@somewhere.org \
    --to=fpz-djc/ipccudyqhejpep6iedvlejwurmry@public.gmane.org \
    --cc=mail-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org \
    --cc=public-emacs-orgmode-mXXj517/zsQ-wOFGN7rlS/M9smdsby/KFg@public.gmane.org \
    --cc=public-fpz-djc/iPCCuDYQheJpep6IedvLeJWuRmrY-wOFGN7rlS/M9smdsby/KFg@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).