emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: erimius@web.de
To: emacs-orgmode@gnu.org
Subject: Bug: org-deadline drops warning periods from TIME [9.4.6 (9.4.6-10-gee652a-elpaplus @ /home/fap/.emacs.d/elpa/org-plus-contrib-20210712/)]
Date: Wed, 21 Jul 2021 17:09:27 +0200	[thread overview]
Message-ID: <83b84e24-bf18-8b2c-0e8e-84abbd2915c8@web.de> (raw)

* Reproduction

Call ~org-deadline~ with a warning period like so:


(org-deadline nil "<2021-07-20 Tue -1d>")
   ;; => DEADLINE: <2021-07-20 Tue>

* Expected

Deadline gets added with the warning period provided.

* Actual

Deadline gets added without the provided warning period.

* Discussion

I've opened a Emacs Stackexchange question regarding this:
https://emacs.stackexchange.com/questions/66765/how-to-insert-an-org-deadline-from-lisp-with-a-warning-period/

And got told the following by Nick D:

#+begin_quote
I think this is a bug: the function ~org--deadline-or-schedule~ saves a
repeater (e.g ~+2d~ ) and adds it back at the end, but the regexp does
not match a warning period (e.g. ~-2d~) so it drops it. You should
probably report it with ~M-x org-submit-bug-report~.
#+end_quote

* Version info

Emacs  : GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version
3.24.20, cairo version 1.16.0)
 of 2020-09-19
Package: Org mode version 9.4.6 (9.4.6-10-gee652a-elpaplus @
/home/fap/.emacs.d/elpa/org-plus-contrib-20210712/)



             reply	other threads:[~2021-07-21 17:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-21 15:09 erimius [this message]
2021-08-31 15:55 ` Bug: org-deadline drops warning periods from TIME [9.4.6 (9.4.6-10-gee652a-elpaplus @ /home/fap/.emacs.d/elpa/org-plus-contrib-20210712/)] Timothy
2021-12-20 14:29 ` [PATCH] " Ihor Radchenko
2022-05-15  6:51   ` 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=83b84e24-bf18-8b2c-0e8e-84abbd2915c8@web.de \
    --to=erimius@web.de \
    --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).