From: Eduardo Suarez-Santana <firstname.lastname@example.org>
To: Ihor Radchenko <email@example.com>
Subject: Re: [PATCH] Re: Escaping org mode date properties
Date: Sun, 2 Jan 2022 21:04:33 +0000 [thread overview]
Message-ID: <20220102210433.GC29829@itccanarias.org> (raw)
On Sun, Jan 02, 2022 at 10:51:54AM +0800, Ihor Radchenko wrote:
> Eduardo Suarez-Santana <firstname.lastname@example.org> writes:
> >> 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).
> Thanks for the hint! I was able to reproduce entries disappearing from
> agenda view.
> The culprit is org-in-src-block-p. It relies on fontification to
> determine if we are inside a code block. However, when you strip a code
> block with SCHEDULED inside from begin/end lines, the fontification
> properties do not get removed.
> The attached patch should fix the issue. However, I need several people
> to test it first - the patch will make things slower without cache.
The patch works for me.
However, how about next cases?
* an example block
SCHEDULED: <2015-02-16 Mon .+2d>
* an example with colon
: SCHEDULED: <2015-02-16 Mon .+2d>
I think they behave the same way as 'begin_src'.
> >> 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.
> For future. You will make things much easier if you provide a clear
> sequence of steps to reproduce the problem. Your original report is not
> reproducible if I just copy-paste your code into a new org file. I had
> to guess what you did in order to see the problem.
Sorry about that. I got weird results and was not sure about the expected
behaviour. I had already asked in IRC with no answer.
next prev parent reply other threads:[~2022-01-02 21:06 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
2022-01-02 2:51 ` [PATCH] " Ihor Radchenko
2022-01-02 21:04 ` Eduardo Suarez-Santana [this message]
2022-01-03 3:39 ` Ihor Radchenko
2022-01-03 10:39 ` Eduardo Suarez-Santana
2022-01-12 13:14 ` Ihor Radchenko
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 \
* 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).