emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Christopher M. Miles" <numbchild@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [BUG] org-agenda generation missing some entries
Date: Sat, 23 Oct 2021 14:54:00 +0800	[thread overview]
Message-ID: <PAXPR08MB66401E695174FB00C261EF6EA3819@PAXPR08MB6640.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <874k99ahvd.fsf@localhost>


[-- Attachment #1.1: Type: text/plain, Size: 1177 bytes --]



Ihor Radchenko <yantar92@gmail.com> writes:

> "Christopher M. Miles" <numbchild@gmail.com> writes:
>> Now I tried your latest push. The errors gone. But org-agenda entries still missing. I checked
>> *Messages* buffer, no error messages, including other error special buffers. no information.
>
> Agenda now uses a new algorithm to search entries. There may be a bug
> there. Can you provide a minimal org file with a heading that should be
> listed in agenda, but did not show up?
>
> Best,
> Ihor

I'm git bisect on the latest git-pulled org-mode. Still located bad commit on this bad commit. Seems
commit also introduced other problem.

#+begin_example
0ef88e2d9 * | bad @ org-agenda.el/org-agenda-get-scheduled: Use cache
#+end_example

I compared good *Org Agenda* buffer and bad *Org Agenda* buffer, bellowing are some of missing
org-agenda entries:

#+begin_src org
,* PROJECT 🅰 task A
  SCHEDULED: <2019-04-16 Tue>
  :LOGBOOK:
  - State "PROJECT"    from              [2019-04-16 Tue 13:37]
  :END:
#+end_src

I checked most of them, almost all missing org-agenda entries are "SCHEDULED" tasks with logbook or
clocking log.



[-- Attachment #1.2: Type: text/html, Size: 2703 bytes --]

[-- Attachment #2: Type: text/plain, Size: 282 bytes --]


<#secure method=pgpmime mode=sign>
-- 
[ 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

  reply	other threads:[~2021-10-23  6:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-21  8:20 [BUG] org-agenda generation missing some entries Christopher M. Miles
2021-10-21  8:42 ` Ihor Radchenko
2021-10-22  2:08   ` Christopher M. Miles
2021-10-22  2:55     ` Ihor Radchenko
2021-10-23  6:54       ` Christopher M. Miles [this message]
2021-10-23  7:17         ` Ihor Radchenko
2021-10-23  8:10           ` Christopher M. Miles
2021-10-23 11:33             ` Ihor Radchenko
2021-10-24  4:55               ` Christopher M. Miles
2021-10-24  5:25                 ` Ihor Radchenko
2021-10-24  7:05                   ` Christopher M. Miles
2021-10-24  8:43                     ` Ihor Radchenko
2021-10-24  9:36                       ` [SOLVED] " Christopher M. Miles
2021-10-23  7:56       ` Christopher M. Miles
2021-10-21 11:22 ` 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=PAXPR08MB66401E695174FB00C261EF6EA3819@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).