From: "Christopher M. Miles" <numbchild@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: [SOLVED] Re: [BUG] org-persist.el: The commits after "410afd6f374e9" caused org-agenda buffer does not display scheduled and deadline tasks
Date: Tue, 11 Jan 2022 22:04:28 +0800 [thread overview]
Message-ID: <PAXPR08MB6640B24AAB9A5307CE1CB969A3519@PAXPR08MB6640.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <87a6g3acc1.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 761 bytes --]
Ihor Radchenko <yantar92@gmail.com> writes:
> "Christopher M. Miles" <numbchild@gmail.com> writes:
>
>>> we are entering the territory of Emacs
>>> build-dependent bugs...
>>
>>> My best suggestion then is going to
>>> org-element.el and changing "(version< emacs-version "29")" to "t".
>>
>> I used this method, found the problem is gone.
>
> Thanks! So much for the idea of byte-compiling the function.
> Should be fixed upstream now.
>
> Best,
> Ihor
Confirmed problem solved.
--
[ stardiviner ]
I try to make every word tell the meaning that I want to express.
Blog: https://stardiviner.github.io/
IRC(freenode): stardiviner, Matrix: stardiviner
GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-01-11 14:58 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
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 ` Christopher M. Miles [this message]
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=PAXPR08MB6640B24AAB9A5307CE1CB969A3519@PAXPR08MB6640.eurprd08.prod.outlook.com \
--to=numbchild@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@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).