emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Gregor Zattler <telegraph@gmx.net>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-element--cache: Warning(izt.org): Got element without parent (cache active?: t)
Date: Wed, 23 Aug 2023 13:48:45 +0200	[thread overview]
Message-ID: <87350auggy.fsf@no.lan> (raw)
In-Reply-To: <871qfu6ncp.fsf@localhost>

Hi Ihor,
* Ihor Radchenko <yantar92@posteo.net> [2023-08-23; 10:53 GMT]:
> Gregor Zattler <telegraph@gmx.net> writes:
>>  ■  Warning (org-element-cache): org-element--cache: Warning(izt.org): Got element without parent (cache active?: t). Please report it to Org mode mailing list (M-x org-submit-bug-report).
>> (node-property (:standard-properties [326858 326875 nil nil 0 326858 nil t nil nil nil node-property element nil #<buffer izt.org> nil nil nil] :key "VISIBILITY" :value "all"))
>> Backtrace:
>>   org-element-cache diagnostics(izt.org): Added new element with nil key: "(keyword
>> ...
> May you try to reproduce the problem starting from emacs -Q, reducing
> your Org file to some small file that can be shared?

that happened when org-mode generated my agenda, there
are four rather big org-mode files involved.  Is it
sufficent to try to reproduce with izt.org only, which
is mentioned in the warning?

I tried just now, but there was no warning and since
the warning I changed the file.  Especially I did
org-link and resolved all problems...

Next time I will save the file immediately for
inspection.

Ciao; Gregor 


      reply	other threads:[~2023-08-23 11:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-23  9:48 org-element--cache: Warning(izt.org): Got element without parent (cache active?: t) Gregor Zattler
2023-08-23 10:53 ` Ihor Radchenko
2023-08-23 11:48   ` Gregor Zattler [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=87350auggy.fsf@no.lan \
    --to=telegraph@gmx.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.net \
    /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).