emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: "Christopher M. Miles" <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 11:57:25 +0800	[thread overview]
Message-ID: <87mtk58st6.fsf@localhost> (raw)
In-Reply-To: <PAXPR08MB6640A051CEA4FD89BD924D0CA34F9@PAXPR08MB6640.eurprd08.prod.outlook.com>

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

> Here is my reproduce environment:
> Reproduce test with =emacs -Q=
> #+begin_src shell :eval no
> emacs -Q -l ~/.config/emacs/minimal-org-init.el ~/org-persist-test.org
> #+end_src
> #+begin_src org :tangle "~/org-persist-test.org"
>   ,* LEARN 🅰 Clojure Web Development Stack [2/12]
>   DEADLINE: <2022-01-01 Sat>
>   - Removed deadline, was "[2018-12-09 Sun]" on [2019-04-13 Sat 11:14]
>   - State "LEARN"      from              [2018-06-01 Fri 09:18]
>   :END:
> #+end_src

Thanks! I am still unable to reproduce. However, I was not able to use
your minimal-org-init directly as I do not have ELPA folder.

Also, note that your statement
 '((emacs-lisp . t)))
may load built-in org

I did the following:
1. go to Org mode source directory
2. create bug.el with the following contents (I tried my best to pull
   important pieces from your minimal init)

(custom-set-variables '(org-modules nil))

(setq org-src-fontify-natively t)

 '((emacs-lisp . t)))

3. Run emacs -Q -L ./lisp -l ./bug.el ~/org-persist-test.org
4. M-x org-agenda
5. < a (set restriction to current buffer and run normal weekly agenda)
6. The heading is displayed

Can you follow my steps and report what happens?


  reply	other threads:[~2022-01-09  3:54 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
2022-01-09  3:09   ` Christopher M. Miles
2022-01-09  3:57     ` Ihor Radchenko [this message]
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:

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


* 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).