From: Carsten Dominik <carsten.dominik@gmail.com>
To: Richard Riley <rileyrg@googlemail.com>
Cc: Juan Pechiar <juan@pechiar.com>, emacs-orgmode@gnu.org
Subject: Re: bug? scheduled keyword inside org items.
Date: Tue, 12 Oct 2010 07:24:18 +0200 [thread overview]
Message-ID: <5F28D179-8DFC-49E3-8490-CF118A05FE8A@gmail.com> (raw)
In-Reply-To: <xevd58306l.fsf@news.eternal-september.org>
On Oct 11, 2010, at 11:10 PM, Richard Riley wrote:
> Juan Pechiar <juan@pechiar.com> writes:
>
>> I'd imagine enclosing the email text in a #+BEGIN_EXAMPLE block would
>> make sense (semantically) and also avoid interpretation of SCHEDULED
>> keyword.
>
> That does make sense. I need to look into my template then for
> journaling email.
>
>>
>> But even using #+BEGIN_COMMENT block, timestamps and SCHEDULED are
>> found by the agenda.
>
> That doesn't sound good. Should it?
No, it should not. But it is costly to parse for all these
special places, and in order to keep the agenda reasonably fast,
this is one of the compromises.
I guess such a case is not very frequent, and I usually work around
them by inserting a space between the opening angular bracket and the
time stamp:
#+begin_example
,* test
SCHEDULED: < 2010-10-10 Sun>
#+end_example
That successfully breaks the timestamp parser, but still
conveys reasonably well what is meant.
- Carsten
>
>>
>> A workaround for your problem can be setting those timestamps as
>> inactive.
>>
>> Regards,
>> .j.
>>
>> On Mon, Oct 11, 2010 at 06:18:06PM +0200, Richard Riley wrote:
>>> I had stored a post here in my todo life as follows
>>>
>>> ,----
>>> |
>>> | * my org item
>>> |
>>> | Subject: Re: Recurring scheduled items appearing in schedule
>>> | From: Bernt Hansen <bernt@norang.ca>
>>> | To: Dustin Hoffman <dustinhhoffman@gmail.com>
>>> | Date: Sat, 09 Oct 2010 20:16:52 -0400
>>> |
>>> | Dustin Hoffman <dustinhhoffman@gmail.com> writes:
>>> |
>>> | > I have scheduled reminders for things that occur weekly over a
>>> period
>>> | > of months. The problem is, that each of these scheduled items
>>> appears
>>> | > under the current day in the agenda view and the multiplier
>>> (eg 6x,
>>> | > 5x) keeps going up.
>>> | >
>>> | > What I want is each of these scheduled items to appear only on
>>> the
>>> | > days that they occur in the agenda view.
>>> | >
>>> | > Here is an example of an org file with a schedule in it.
>>> | >
>>> | > * Class Times
>>> | > ** Class
>>> | > SCHEDULED: <2010-09-28 Tue 12:30-13:48 +1w>
>>> | > ** Class
>>> | > SCHEDULED: <2010-09-23 Thu 12:30-13:48 +1w>
>>> | >
>>> | >
>>> `----
>>>
>>> The SCHEDULED items inside the quoted text are appearing in my
>>> agenda.
>>>
>>> Bug, as expected or can I stop that?
>
> --
> ☘ http://www.shamrockirishbar.com, http://splash-of-open-sauce.blogspot.co
> m/ http://www.richardriley.net
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
prev parent reply other threads:[~2010-10-12 5:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 16:18 bug? scheduled keyword inside org items Richard Riley
2010-10-11 20:15 ` Juan Pechiar
2010-10-11 21:10 ` Richard Riley
2010-10-12 5:24 ` Carsten Dominik [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=5F28D179-8DFC-49E3-8490-CF118A05FE8A@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=juan@pechiar.com \
--cc=rileyrg@googlemail.com \
/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).