Re: org element bug filling

2025-09-30 Thread Samuel Wales
does anybody know if this bug is fixed? On Thu, Aug 14, 2025 at 3:03 PM Samuel Wales wrote: > > Not sure what you mean here. Do you mean supply backtraces with those > versions, or do you mean that bugfix can't be fixed? > > On Mon, Aug 11, 2025 at 9:31 AM Ihor Radchenko wrote: > > > > Samuel W

Re: org element bug filling

2025-08-14 Thread Samuel Wales
Not sure what you mean here. Do you mean supply backtraces with those versions, or do you mean that bugfix can't be fixed? On Mon, Aug 11, 2025 at 9:31 AM Ihor Radchenko wrote: > > Samuel Wales writes: > > > org9.7.33 > > emacs30.1 > > Then, I can only suggest trying development version

Re: org element bug filling

2025-08-11 Thread Ihor Radchenko
Samuel Wales writes: > org9.7.33 > emacs30.1 Then, I can only suggest trying development version of Org maybe with Emacs master. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at . Support Org development at

Re: org element bug filling

2025-08-10 Thread Samuel Wales
org9.7.33 emacs30.1 On Sun, Aug 10, 2025 at 3:28 AM Ihor Radchenko wrote: > > Samuel Wales writes: > > > they seem random, but once they start in a file, they sometimes occur > > more often. > > > > e.g. open a heading, open a child, and the first heading closes. > > Might be related to

Re: org element bug filling

2025-08-10 Thread Ihor Radchenko
Samuel Wales writes: > they seem random, but once they start in a file, they sometimes occur > more often. > > e.g. open a heading, open a child, and the first heading closes. Might be related to https://debbugs.gnu.org/cgi/bugreport.cgi?bug=79115 Or not. Which Org version are you using? -- Ih

Re: org element bug filling

2025-08-09 Thread Samuel Wales
they seem random, but once they start in a file, they sometimes occur more often. e.g. open a heading, open a child, and the first heading closes. On Sat, Aug 9, 2025 at 5:53 AM Ihor Radchenko wrote: > > Samuel Wales writes: > > > i am not getting that error yet, but i am getting folding glitch

Re: org element bug filling

2025-08-09 Thread Ihor Radchenko
Samuel Wales writes: > i am not getting that error yet, but i am getting folding glitches > upon folding/unfolding of headings and upon moving of list items. > > perhaps not related? might be in the past few git snapshots. No idea, because I need more details on what "glitches" you are talking

Re: org element bug filling

2025-08-05 Thread Samuel Wales
thank you very much. i am not getting that error yet, but i am getting folding glitches upon folding/unfolding of headings and upon moving of list items. perhaps not related? might be in the past few git snapshots. On Mon, Aug 4, 2025 at 10:14 AM Ihor Radchenko wrote: > > Samuel Wales write

Re: org element bug filling

2025-08-04 Thread Ihor Radchenko
Samuel Wales writes: > -- Caught at Sun Aug 3 21:13:01 2025 > > Error: wrong-type-argument (number-or-marker-p nil) > <(2 nil) > (if (< p post-affiliated) nil (cond ((eql type 'comment) > ... > org-adaptive-fill-function() Thanks! Fixed, (hopefully) on bugfix. https://git.savannah.gnu.org

Re: org element bug filling

2025-08-03 Thread Samuel Wales
-- Caught at Sun Aug 3 21:13:01 2025 Error: wrong-type-argument (number-or-marker-p nil) <(2 nil) (if (< p post-affiliated) nil (cond ((eql type 'comment) (save-excursion (forward-line 0) (looking-at "[ \11]*") (concat (match-string 0) "# "))) ((eql type 'footnote-definition) "") ((memql type

Re: org element bug filling

2025-08-03 Thread Ihor Radchenko
Samuel Wales writes: > below please find entire contents of warnings buffer [latest says look > at redisplay trace buffer], followed by entire contents of redisplay > trace buffer. Thanks! Unfortunately, there is no additional information here. > Error: wrong-type-argument (number-or-marker-p n

Re: org element bug filling

2025-07-27 Thread Samuel Wales
below please find entire contents of warnings buffer [latest says look at redisplay trace buffer], followed by entire contents of redisplay trace buffer. -- Caught at Sat Jul 26 21:46:34 2025 Error: wrong-type-argument (number-or-marker-p nil) org-adaptive-fill-function() fill-match-adaptive

Re: org element bug filling

2025-07-20 Thread Ihor Radchenko
Samuel Wales writes: > i set teh variables and tried to repro and was not able to. Then, you can try adding those variable into init.el and then monitor *Redisplay-trace* buffer. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at . Support Or

Re: org element bug filling

2025-07-20 Thread Samuel Wales
i got the error upon scroll-up-command. [i am not sure if i was in the buffer being reported on for sure, but i always have only one window, so if so, it woudl be oerhaps strange that it would try to font lock something not visible. one thing that would help is if th4e warnings buffer could conta

Re: org element bug filling

2025-07-20 Thread Samuel Wales
i will try, but i doubt that i wil be able to retrigger immediately aft4r the first trigger. On Sun, Jul 20, 2025 at 8:04 AM Ihor Radchenko wrote: > > Samuel Wales writes: > > > ⛔ Warning (org-element): org-element--cache: Org parser error in > > fix.org::22506. Resetting. > > The error was: (w

Re: org element bug filling

2025-07-20 Thread Ihor Radchenko
Samuel Wales writes: > ⛔ Warning (org-element): org-element--cache: Org parser error in > fix.org::22506. Resetting. > The error was: (wrong-type-argument integer-or-marker-p nil) > Backtrace: > " backtrace-to-string(nil) > org-element-at-point() > org-adaptive-fill-function() > fill-mat

Re: org element bug filling

2025-07-06 Thread Samuel Wales
Another observation that might or might not be relevant: I am getting very frequent, intermittent folding errors, where I try to fold or unfold a list or use undo-tree, and entries get collapsed. Got worse when upgraded. On Sun, Jul 6, 2025 at 9:15 PM Samuel Wales wrote: > > (auto-fill-mode -1

Re: org element bug filling

2025-07-06 Thread Samuel Wales
(auto-fill-mode -1) (visual-line-fill-column-mode) (visual-wrap-prefix-mode) On Sun, Jul 6, 2025 at 9:11 PM Samuel Wales wrote: > > Please forgive any email impropriety in the headers. I am not sure if > they are correct. I am hoping this will go through. Gmail is > inaccessible, not all