emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: numbchild@gmail.com
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-persist.el: The commits after "410afd6f374e9" caused org-agenda buffer does not display scheduled and deadline tasks
Date: Sun, 09 Jan 2022 09:20:33 +0800	[thread overview]
Message-ID: <87pmp1902m.fsf@localhost> (raw)
In-Reply-To: <PAXPR08MB6640803C6A83CA45A2A961B6A34E9@PAXPR08MB6640.eurprd08.prod.outlook.com>

"Christopher M. Miles" <numbchild@gmail.com> writes:

> I git bisected org-mode source code, and found the commits after "410afd6f374e9" caused org-agenda
> does not display scheduled and deadline tasks. Also affects org-contacts completion get contacts
> email property.
>
> I'm using the latest commit "dc4b2772e".
>
> I use bug-hunter extension to test my Emacs config, confirmed problem is NOT on my Emacs config.

Does it mean that you can reproduce using emacs -Q? If so, could you
provide a recipe to replicate the bug you are seeing?

> the commits after "410afd6f374e9"

Is "410afd6f374e9" a bad commit? That commit had nothing to do with
agenda or org-persist. The following fbff082f7 is just a version
update...

Best,
Ihor



  reply	other threads:[~2022-01-09  1:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-08 16:51 [BUG] org-persist.el: The commits after "410afd6f374e9" caused org-agenda buffer does not display scheduled and deadline tasks Christopher M. Miles
2022-01-09  1:20 ` Ihor Radchenko [this message]
2022-01-09  3:09   ` Christopher M. Miles
2022-01-09  3:57     ` Ihor Radchenko
2022-01-09  8:03       ` Christopher M. Miles
2022-01-09  9:04         ` Ihor Radchenko
2022-01-09  9:07         ` Ihor Radchenko
2022-01-09 15:56           ` Christopher M. Miles
2022-01-10 14:34             ` Ihor Radchenko
2022-01-11 14:04               ` [SOLVED] " Christopher M. Miles

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=87pmp1902m.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=numbchild@gmail.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).