From: Ihor Radchenko <yantar92@gmail.com>
To: Sharon Kimble <boudiccas@skimble09.plus.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-element-cache [9.5.4 (release_9.5.4-766-gf3f60e @ /home/boudiccas/git/org-mode/lisp/)]
Date: Mon, 05 Sep 2022 14:50:44 +0800 [thread overview]
Message-ID: <87wnaiwbzv.fsf@localhost> (raw)
In-Reply-To: <87wnaj13yh.fsf@skimble09.plus.com>
Sharon Kimble <boudiccas@skimble09.plus.com> writes:
>> You can then try:
>> 1. Run clean Emacs version by running "make repro" from Org repository
>> and try to reproduce the issue.
>
> This created a new instance of emacs, which showed this in its '*compile-log*' -
Let me clarify what I was referring to.
"make repro" is supposed to create a new Emacs instance that is not
affected by your personal settings. Please try to open the problematic
file from there and then do what you usually do before you get the
warning appear. Let me know if it does or does not appear in this
scenario.
> ===
> lisp/org-macs.el: Warning: ‘buffer-string’ is an obsolete generalized
> variable.
> lisp/org-macs.el: Warning: ‘buffer-string’ is an obsolete generalized
> variable.
> lisp/org.el: Warning: ‘buffer-substring’ is an obsolete generalized variable.
> ===
> and also -
>
> ===
> For information about GNU Emacs and the GNU system, type C-h C-a.
> Org mode version 9.5.5 (release_9.5.5-756-g1f1d8f.dirty @ /home/boudiccas/git/org-mode/lisp/)
> Mark set
> Beginning of buffer [4 times]
> ===
This is not relevant and nothing to worry about.
>> 2. If you cannot reproduce, you can try to bisect your config using
>> https://github.com/Malabarba/elisp-bug-hunter
>> Also, see
>> https://open.tube/videos/watch/4d819114-43bf-42df-af94-f94fc53dd0d9
>
> I used 'bug-hunter-file' on my main config and also my init file and it found no problems with either.
I referred to interactive usage of bug-hunter-file.
What I am asking you to do here is trying to perform action triggering
the error you reported. bug-hunter-init-file should help you to identify
which part of your config is the culprit. Then, you can report that part
to me. It will help to fix the problem.
--
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92
prev parent reply other threads:[~2022-09-05 6:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-04 10:21 [BUG] org-element-cache [9.5.4 (release_9.5.4-766-gf3f60e @ /home/boudiccas/git/org-mode/lisp/)] Sharon Kimble
2022-09-04 10:46 ` Ihor Radchenko
2022-09-04 13:28 ` Sharon Kimble
2022-09-04 13:48 ` Ihor Radchenko
2022-09-04 15:38 ` Sharon Kimble
2022-09-04 15:58 ` Ihor Radchenko
2022-09-04 16:47 ` Sharon Kimble
2022-09-05 6:50 ` Ihor Radchenko [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=87wnaiwbzv.fsf@localhost \
--to=yantar92@gmail.com \
--cc=boudiccas@skimble09.plus.com \
--cc=emacs-orgmode@gnu.org \
/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).