emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Daniel Hubmann <hubisan@gmail.com>
To: emacs-orgmode@gnu.org
Subject: [BUG] Not all time/date strings are recognized as time in org-make-tags-matcher [9.6 (9.6-gd500b4 @ /home/hubisan/.emacs.default/straight/build/org/)]
Date: Tue, 6 Dec 2022 15:14:51 +0100	[thread overview]
Message-ID: <CAOX7s=0kZR-NBMnO7imy=C62uy0N-wh3_09iyMjuXfv8MWKsDg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 998 bytes --]

After updating to Org 9.6 this match in the agenda
'SCHEDULED<"<+2d>"+SCHEDULED<>"' shows all scheduled items event if they
are far more in the future than 2 days.

Tracked this down to a commit (e022a0cea11a0e784ba20ac478a033da7fb1bb7f)
that changed the regular expression to recognize timestamps:

-    (timep (string-match-p "^\"[[<].*[]>]\"$" pv))
> +    (timep (string-match-p "^\"[[<][0-9]+.*[]>]\"$" pv))
>

If I understand it correctly, this new regular expression only matches
strings that start with < and a number. So strings like <today>,
<tomorrow>, <+2d> and so on are not working anymore.

If I change the expression to the one before and evaluate the function, the
match works again.

A big thank you to all the developers behind org-mode!

Best wishes.
Daniel Hubmann

Emacs  : GNU Emacs 29.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version
3.24.20, cairo version 1.16.0)
 of 2022-07-18
Package: Org mode version 9.6 (9.6-gd500b4 @
/home/hubisan/.emacs.default/straight/build/org/)

[-- Attachment #2: Type: text/html, Size: 1436 bytes --]

             reply	other threads:[~2022-12-07  6:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06 14:14 Daniel Hubmann [this message]
2022-12-07 12:46 ` [BUG] Not all time/date strings are recognized as time in org-make-tags-matcher [9.6 (9.6-gd500b4 @ /home/hubisan/.emacs.default/straight/build/org/)] 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:
  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='CAOX7s=0kZR-NBMnO7imy=C62uy0N-wh3_09iyMjuXfv8MWKsDg@mail.gmail.com' \
    --to=hubisan@gmail.com \
    --cc=emacs-orgmode@gnu.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).