emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eduardo Suarez-Santana <esuarez@itccanarias.org>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: <emacs-orgmode@gnu.org>
Subject: Re: Escaping org mode date properties
Date: Sat, 1 Jan 2022 20:01:03 +0000	[thread overview]
Message-ID: <20220101200103.GB29829@itccanarias.org> (raw)
In-Reply-To: <875yr31ogp.fsf@localhost>

On Sat, Jan 01, 2022 at 11:10:30PM +0800, Ihor Radchenko wrote:
> Eduardo Suarez <esuarez@itccanarias.org> writes:
> > The next code snippet makes the entry to appear in the agenda:
> >
> > * sample date code
> > #+begin_src org
> > SCHEDULED: <2015-02-16 Mon .+2d>
> > #+end_src
> I am unable to reproduce. What are your Org and Emacs versions?

I'm using Spacemacs (develop branch).

- Emacs 27.2
- Org 9.5.1

I get a weird behaviour about it. These events appear when I start emacs. If I
edit somehow these entries they disappear from the agenda view (until I start
emacs again).

> > On the other hand, I wonder whether it is possible to make a subtree to be
> > ignored by the agenda views.
> Depending what you want, you may use org-agenda-todo-list-sublevels or
> add agenda filter excluding specific tags that you can then use to mark
> undesired subtrees.

Could be a workaround. Thanks a lot.

Anyway it looks like a bug to me.

  reply	other threads:[~2022-01-01 20:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-01 12:24 Escaping org mode date properties Eduardo Suarez
2022-01-01 15:10 ` Ihor Radchenko
2022-01-01 20:01   ` Eduardo Suarez-Santana [this message]
2022-01-02  2:51     ` [PATCH] " Ihor Radchenko
2022-01-02 21:04       ` Eduardo Suarez-Santana
2022-01-03  3:39         ` Ihor Radchenko
2022-01-03 10:39           ` Eduardo Suarez-Santana
2022-01-12 13:14             ` Ihor Radchenko

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:

  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=20220101200103.GB29829@itccanarias.org \
    --to=esuarez@itccanarias.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@gmail.com \


* 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


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).