emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] (wrong-type-argument integer-or-marker-p nil) [9.6.15 (release_9.6.15 @ /home/phi/Source/emacs/lisp/org/)]
Date: Tue, 05 Mar 2024 11:18:32 +0000	[thread overview]
Message-ID: <871q8p6i5z.fsf@posteo.net> (raw)
In-Reply-To: <87zfvdq6vl.fsf@localhost> (Ihor Radchenko's message of "Tue, 05 Mar 2024 11:02:06 +0000")

Ihor Radchenko <yantar92@posteo.net> writes:

> Philip Kaludercic <philipk@posteo.net> writes:
>
>>> Thanks for reporting!
>>> Does the error persist if you upgrade Org mode to the latest 9.6.20
>>> version? If yes, what about the development version?
>>
>> Sorry, I cannot really reproduce the bug in any reliable way.
>
> Even if you cannot reproduce reliably, it is not a problem. Org mode has
> a way to enable recording diagnostics info (via
> org-element--cache-self-verify). But that only makes sense if we know
> for sure that the bug is present on the latest development version of
> Org mode.
>
> So, I just need to know if you keep seeing problems after upgrading to
> the latest main.
>
> If you have no time or interest diagnosing the bug and the warnings keep
> appearing, you may disable cache in your config by customizing
> org-element-use-cache.

The issue is rather, I don't see the warning at all anymore ("cannot
reproduce reliably" in the sense of might randomly occur at some point
again).

-- 
	Philip Kaludercic on peregrine


  reply	other threads:[~2024-03-05 11:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-01 14:09 [BUG] (wrong-type-argument integer-or-marker-p nil) [9.6.15 (release_9.6.15 @ /home/phi/Source/emacs/lisp/org/)] Philip Kaludercic
2024-03-02 12:13 ` Ihor Radchenko
2024-03-04 14:47   ` Philip Kaludercic
2024-03-05 11:02     ` Ihor Radchenko
2024-03-05 11:18       ` Philip Kaludercic [this message]
2024-03-05 11:25         ` 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=871q8p6i5z.fsf@posteo.net \
    --to=philipk@posteo.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).