Gregor Zattler writes:
> this happened when I juggled with some
> org-mode formatted text from an email in
> two versions, comparing them. I cannot
> say at what specific command the warning
> was shown.
>
> I'm not able to reproduce.
I was really hoping that we eradicated this in the latest ma
Hi Ihor,
* Ihor Radchenko [2023-11-19; 19:21 GMT]:
> Gregor Zattler writes:
>> Warning (org-element-cache): org-element--cache:
>> Warning(notmuch-startpage.org): Org parser error in
>> notmuch-startpage.org::8690. Resetting.
>> The error was: (wrong-number-of-argum
g (org-element-cache): org-element--cache:
> Warning(notmuch-startpage.org): Org parser error in
> notmuch-startpage.org::8690. Resetting.
> The error was: (wrong-number-of-arguments ((t) (element) "Return type of
> ELEMENT.
>
> The function returns the type of the ele
Gregor Zattler writes:
> Dear org mode maintainers, developers, Ihor, I caught the
> following warning/backtrace while calling
> 'my/org-goto-agenda-heading´ which in turn is just
> "(org-refile '(4))".
>
> HTH/Ciao; Gregor
>
> ■ Warning (org-el
Dear org mode maintainers, developers, Ihor, I caught the
following warning/backtrace while calling
'my/org-goto-agenda-heading´ which in turn is just
"(org-refile '(4))".
HTH/Ciao; Gregor
■ Warning (org-element-cache): org-element--cache:
Warning(Checkliste-Updates.txt):
Hi Ihor,
* Ihor Radchenko [2023-08-23; 10:53 GMT]:
> Gregor Zattler 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-repor
Gregor Zattler writes:
> Dear Ihow, I caught another org-element-cache warning.
> I started Emacs (after having problems with a botched
> configuration, which in turn uses babel...) and called
> the agenda like so:
>
> (defun gz/org-agenda-list ()
> "Show Org
Dear Ihow, I caught another org-element-cache warning.
I started Emacs (after having problems with a botched
configuration, which in turn uses babel...) and called
the agenda like so:
(defun gz/org-agenda-list ()
"Show Org Agenda starting yesterday."
(interactive)
(org-age
Gregor Zattler writes:
> Dear org-mode developers, Ihor, I cought an
> org-element-cache warning with a rather up-to-date
> emacs and org-mode ...
Thanks for reporting!
> The element is: "(headline (:standard-properties [159509 160713 159557 160712
> 1..."
> The
Dear org-mode developers, Ihor, I cought an
org-element-cache warning with a rather up-to-date
emacs and org-mode while calling via a key binding this
simple function:
(defun my/org-goto-agenda-heading ()
(interactive)
(org-refile '(4)))
GNU Emacs 30.0.50 (build 1, x86_64-pc-linu
Gregor Zattler writes:
>> This is strange. Did the buffer in question happened to be an indirect
>> buffer?
>
> I do not use indirect buffers intentionally. If an agenda
> is an indirect buffer than it may be -- I do not remember
> the exact situation, it was happening at the very first
> minut
Hi Ihor,
* Ihor Radchenko [2023-02-07; 10:59 GMT]:
> Gregor Zattler writes:
>> * Ihor Radchenko [2023-02-06; 10:28 GMT]:
>>> Gregor Zattler writes:
>>> Unfortunately, the provided log is incomplete. I cannot deduce anything
>>> useful from it.
>>
>> that's strange, I realized it was shorter tha
Gregor Zattler writes:
> Hi Ihor,
> * Ihor Radchenko [2023-02-06; 10:28 GMT]:
>> Gregor Zattler writes:
>> Unfortunately, the provided log is incomplete. I cannot deduce anything
>> useful from it.
>
> that's strange, I realized it was shorter than others, but
> it's all emacs had in it's *Warn
Hi Ihor,
* Ihor Radchenko [2023-02-06; 10:28 GMT]:
> Gregor Zattler writes:
> Unfortunately, the provided log is incomplete. I cannot deduce anything
> useful from it.
that's strange, I realized it was shorter than others, but
it's all emacs had in it's *Warnings* buffer then.
> Please provide
Gregor Zattler writes:
> Dear Ihor, org-mode developers, I caught another cache
> warning, see below.
Thanks for reporting!
Unfortunately, the provided log is incomplete. I cannot deduce anything
useful from it.
Please provide the full log if you encounter the warning again.
Canceled.
--
Ih
): org-element--cache: Warning(XXX.org):
(gz/org-agenda-list) Cached element is incorrect in XXX.org. (Cache tic up to
date: "yes") Resetting.
If this warning appears regularly, please report the warning text to Org mode
mailing list (M-x org-submit-bug-report).
The element is: "
Dear org-mode developers, I caught this org-element--cache:
Warning(*Capture*) with `max-lisp-eval-depth` set to 32000.
With a value of 16000 I got
org-capture: Capture abort: Lisp nesting exceeds ‘max-lisp-eval-depth’: 16001
With a value of 16 I got a segfault and the backtrace
was so huge it
Robert Weiner writes:
> So if we want to determine the Org type of an element outside of an Org
> buffer (when using org-type minor modes for example), how would we change
> this 'let' code:
>
> (let* ((context
> ;; Only consider supported types, even if they are not
> ;; the c
t in "~/src/org-mode/contrilb/lisp" in a
> > *Pp Eval Output* buffer holding my complete load-path
> > resulted in this org-element--cache warning:
> >
> > ■ Warning (org-element-cache): org-element--cache: Org parser error in
> *Pp Eval Output*::5288. Resett
Gregor Zattler writes:
> Dear org-mode and hyperbole developers, hitting hyperbole's
> action-key with point in "~/src/org-mode/contrilb/lisp" in a
> *Pp Eval Output* buffer holding my complete load-path
> resulted in this org-element--cache warning:
>
> ■
Dear org-mode and hyperbole developers, hitting hyperbole's
action-key with point in "~/src/org-mode/contrilb/lisp" in a
*Pp Eval Output* buffer holding my complete load-path
resulted in this org-element--cache warning:
■ Warning (org-element-cache): org-element--cache: Org
Gregor Zattler writes:
> I then updated org-mode, applied your patch: No warning
> either. I then purged ~/.cache/org/persist and restarted
> emacs: No warnings.
>
> So while there are no downsides regarding my small test with
> your patch, I cannot verify that it addresses the problem,
> becaus
Hi Ihor,
* Ihor Radchenko [2022-07-08; 12:25]:
> Thanks for reporting! The backtrace is very helpful.
>
> Can you please try the attached patch and let me know if it helps?
thanks for the patch. I first tried to provoke again the
warnings but did not succeed, although I use the same emacs
and or
Gregor Zattler writes:
> Dear org-mode developers, Ihor, I got these warnings
> immediately after I purged ~/.cache/org-persist, started
> emacs/org-mode and tried to find some node via org-rifle.
> Backtrace:
> org-element-cache diagnostics( *helm-org-rifle-fontify*): nil is about to
> modify
ll me if there is
anything I can do to help investigate.
-- Ciao; Gregor
--
-... --- .-. . -.. ..--.. ...-.-
Warning (org-element-cache): org-element--cache: Warning(
*helm-org-rifle-fontify*): Unregistered buffer modifications detected.
Resetting.
If this warning appears regularly, please r
Colin Baxter 😺 writes:
> I have done this but now do not see any warning. Further, I now don't
> seem to be able to re-produce the issue at all. It could that the
> original warning was spurious and reflected some stale state. I did have
> multiple emacsen open at the time.
Note that I fixed som
> Ihor Radchenko writes:
> Colin Baxter 😺 writes:
>> I do not have an org-persist cache present. So I wonder where is
>> the cache that I am supposedly corrupting.
> That warning is shown when org-element--parse-to throws an error
> (the parser fails). Apparently, there
Colin Baxter 😺 writes:
> I do not have an org-persist cache present. So I wonder where is the
> cache that I am supposedly corrupting.
That warning is shown when org-element--parse-to throws an error (the
parser fails). Apparently, there is some problem with Org parser.
> Warning (org-element-c
Hello,
I have
#+begin_src emacs-lisp
(setq org-element-use-cache nil)
(setq org-element-cache-persistent nil)
#+end_src
Yet when editing by hand a time string in a today habit I get the
warning:
--8<---cut here---start->8---
Warning (org-element-cache): or
29 matches
Mail list logo
