From: Kyle Meyer <kyle@kyleam.com>
To: Gustavo Barros <gusbrs.2016@gmail.com>
Cc: Bastien Guerry <bzg@bzg.fr>, emacs-orgmode@gnu.org, hhkg@protonmail.com
Subject: Re: Bug: Repeating tasks no longer appearing on future dates in the agenda [9.3.6 (9.3.6-17-g389288-elpaplus @ /home/gustavo/.emacs.d/elpa/org-plus-contrib-20200224/)]
Date: Fri, 10 Apr 2020 00:00:13 +0000 [thread overview]
Message-ID: <878sj42os2.fsf@kyleam.com> (raw)
In-Reply-To: <87lfn5j5dz.fsf@gmail.com>
Gustavo Barros <gusbrs.2016@gmail.com> writes:
> I'd like to respectfully bump this bug report.
> It's an annoying regression of a widely used Org feature, is precisely
> located (to the commit) and has been reproduced by Kyle (btw, thanks,
> Kyle).
> Of course, if someone is already looking into it, and just didn't have
> the time yet, please disregard the bump.
I've sat down to work on it a few times and wasn't able to get anywhere
with the time I had available. It's on my list to revisit. However, as
we have no proposed fix, in my view it'd make sense to revert the
problematic commit, 39c656870. While that recent commit may resolve a
longstanding bug in the handling of one-time delays, it causes a
regression in functionality that I suspect is much more widely used and
relied on.
I'll plan to revert the commit tomorrow. Please chime in if you
disagree with me doing so.
next prev parent reply other threads:[~2020-04-10 0:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-29 2:15 Bug: Repeating tasks no longer appearing on future dates in the agenda [9.3.6 (9.3.6-17-g389288-elpaplus @ /home/gustavo/.emacs.d/elpa/org-plus-contrib-20200224/)] Gustavo Barros
2020-02-29 2:37 ` Kyle Meyer
2020-04-09 10:54 ` Gustavo Barros
2020-04-10 0:00 ` Kyle Meyer [this message]
2020-04-12 5:44 ` Kyle Meyer
2020-04-13 0:21 ` Gustavo Barros
2020-05-21 7:06 ` Bastien via General discussions about Org-mode.
2020-09-10 5:34 ` Bastien
2020-09-10 11:17 ` Gustavo Barros
2020-09-10 12:17 ` Bastien
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=878sj42os2.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=bzg@bzg.fr \
--cc=emacs-orgmode@gnu.org \
--cc=gusbrs.2016@gmail.com \
--cc=hhkg@protonmail.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).