Org 9.7 org-element API incompatible changes #364

muntean-alex · 2023-08-02T18:27:22Z

Good evening all,
I've had a small agenda-like org-ql setup that I used with org-mode for a while.
After not using it for a month or two, I've gotten back to using it and I've discovered that it throws an error.

"replace-regexp-in-string: Wrong type argument: stringp, [org-element-deferred org-element--headline-parse-title (nil) nil]"

(defun kr/agenda-next-month ()
  (interactive)
  (require 'org-ql)
(org-ql-search (org-agenda-files)
  '(and (or (deadline :to 30)
            (scheduled :to 30)
            (todo :to 30))
        (not (done))
        (not (tags "tag"))
        )
  :title "My next month"
  :super-groups '(
                  (:name "Today"
                         :scheduled today
                         :deadline today
                         :date today)
                  (:name "Due soon"
                         :scheduled future
                         :deadline auto)
                  (:name "Overdue"
                         :scheduled past
                         :deadline past)
                  (:name "Bills soon"
                         :tag "bills")
                  (:name "Due later"
                         :scheduled future
                         :deadline future)
                  (:name "Projects"
                         :tag "projects")
                  (:name "Misc"
                         :todo "TODO")
                  (:todo "READ"
                         :order 7)
                  (:todo "WAIT"
                         :order 6)
                  (:priority "A" :order 1)
                  (:priority "B" :order 2)
                  (:priority "C" :order 3)))
)

Anybody facing something similar?
Any hints on tracking down this issue?

Thank you kindly!

The text was updated successfully, but these errors were encountered:

yantar92 · 2023-08-02T18:30:52Z

radian-software/straight.el#1107

TL;DR: If you upgraded Org mode recently, you may need to clear your straight/build directory and re-compile.

muntean-alex · 2023-08-02T18:45:02Z

Hello!
I've nuked the straight directory and rebuilt with doom upgrade
Sadly, no cigar.
Gives me the same error.

yantar92 · 2023-08-02T18:48:05Z

Hmm. Then, may you do M-x debug-on-error and post the full backtrace?

muntean-alex · 2023-08-02T18:52:18Z

Debugger entered--Lisp error: (wrong-type-argument stringp [org-element-deferred org-element--headline-parse-title (nil) nil])
  string-match("\\[\\[\\(\\(?:[^][\\]\\|\\\\\\(?:\\\\\\\\\\)*[][]\\|\\\\+[^][]\\)+\\)..." [org-element-deferred org-element--headline-parse-title (nil) nil] 0)
  replace-regexp-in-string("\\[\\[\\(\\(?:[^][\\]\\|\\\\\\(?:\\\\\\\\\\)*[][]\\|\\\\+[^][]\\)+\\)..." #f(compiled-function (m) #<bytecode -0x8ce38b99175cad3>) [org-element-deferred org-element--headline-parse-title (nil) nil] nil t)
  org-link-display-format([org-element-deferred org-element--headline-parse-title (nil) nil])
  org-ql-view--format-element((headline (:standard-properties [667 707 679 707 0 667 (:title) nil nil 681 705 nil nil 1 nil [org-element-deferred org-element--headline-deferred nil t] nil #<buffer inbox.org>] :pre-blank 0 :raw-value [org-element-deferred org-element--headline-parse-title (nil) nil] :title [org-element-deferred org-element--headline-parse-title (nil) nil] :level [org-element-deferred org-element--headline-parse-title (nil) nil] :priority [org-element-deferred org-element--headline-parse-title (nil) nil] :tags [org-element-deferred org-element--headline-parse-title (nil) nil] :todo-keyword [org-element-deferred org-element--headline-parse-title (nil) nil] :todo-type [org-element-deferred org-element--headline-parse-title (nil) nil] :footnote-section-p [org-element-deferred org-element--headline-parse-title (nil) nil] :archivedp [org-element-deferred org-element--headline-parse-title (nil) nil] :commentedp [org-element-deferred org-element--headline-parse-title (nil) nil] :org-marker #<marker in no buffer> :org-hd-marker #<marker in no buffer>)))
  mapcar(org-ql-view--format-element ((headline ...) (headline ...) (headline ...) (headline ...) (headline ...) (headline ...) (headline ...) (headline ...) (headline ...) (headline ...) (headline ...) (headline ...) (headline ...) (headline ...) (headline ...) (headline ...) (headline ...) (headline ...) (headline ...) (headline ...) ...))
  -map(org-ql-view--format-element ((headline ...) (headline ...) (headline ...) (headline ...) (headline ...) (headline ...) (headline ...) (headline ...) (headline ...) (headline ...) (headline ...) (headline ...) (headline ...) (headline ...) (headline ...) (headline ...) (headline ...) (headline ...) (headline ...) (headline ...) ...))
  org-ql-search(("[[myfiles.org]]") (and (or (deadline :to 30) (scheduled :to 30) (todo :to 30)) (not (done)) (not (tags "tag"))) :title "My Agenda View" :super-groups ((:name "Today" :scheduled today :deadline today :date today) (:name "Due soon" :scheduled future :deadline auto) (:name "Overdue" :scheduled past :deadline past) (:name "Bills soon" :tag "bills") (:name "Due later" :scheduled future :deadline future) (:name "Projects" :tag "projects") (:name "Misc" :todo "TODO") (:todo "READ" :order 7) (:todo "WAIT" :order 6) (:priority "A" :order 1) (:priority "B" :order 2) (:priority "C" :order 3)))
  kr/agenda-next-month()
  funcall-interactively(kr/agenda-next-month)
  call-interactively(kr/agenda-next-month nil nil)
  command-execute(kr/agenda-next-month)

yantar92 · 2023-08-02T18:54:48Z

I see now. This is because org-ql-view--format-element relies on internal org-element representation, which has been changed in the cutting edge Org.

@alphapapa Please check out https://git.savannah.gnu.org/cgit/emacs/org-mode.git/tree/etc/ORG-NEWS#n40

yantar92 · 2023-08-02T18:56:05Z

@muntean-alex Meanwhile, you may need to downgrade Org mode. org-roam/org-roam#2361 has a lot of instructions how to do it.

alphapapa · 2023-08-02T20:41:14Z

I see now. This is because org-ql-view--format-element relies on internal org-element representation, which has been changed in the cutting edge Org.

@alphapapa Please check out https://git.savannah.gnu.org/cgit/emacs/org-mode.git/tree/etc/ORG-NEWS#n40

ISTM that this change, while it may be an improvement in several ways, is going to break a LOT of third-party packages, like this one. The org-element sexp representation has been unchanged for many years and versions. I feel like there should be a transitional period with the new representation under a different API to preserve compatibility with other code in the wild.

I mean, thinking of all the places in org-ql and org-super-agenda that will likely have to be changed for this, and have multiple code paths by Org version, for YEARS to come, because of this change... the various org-ql predicates and org-super-agenda group selectors... It makes me want to import the old org-element API and just use that instead.

On top of that, there is no guidance for developers to adapt their code to the new API, no helper functions or macros...? This is looking like many, many hours of work and hundreds or thousands of lines of extra code to work with multiple Org versions and APIs, and that cluttering up the packages' source code for years until the old Org versions are truly not used anymore.

Version 9.7 (not released yet)

Ok, so, please, please, PLEASE, do not release Org 9.7 with this change as-is. There has got to be some kind of compatibility layer for downstream libraries. This burden can't just be dumped on downstream developers and users.

Or if I'm wrong and this is all much simpler than it appears, then please educate me, and please improve the documentation accordingly.

yantar92 · 2023-08-03T03:39:29Z

Adam Porter ***@***.***> writes:

ISTM that this change, while it may be an improvement in several ways, is going to break a LOT of third-party packages, like this one. The org-element sexp representation has been unchanged for many years and versions. I feel like there should be a transitional period with the new representation under a different API to preserve compatibility with other code in the wild.

Only the packages that were abusing the internal representation _instead_ of using the (previously) existing API may be broken. Except a single (rare) case when packages had a need to traverse all properties in an element - this case had no proper API previously.

I mean, thinking of all the places in org-ql and org-super-agenda that will likely have to be changed for this, and have multiple code paths by Org version, for YEARS to come, because of this change... the various org-ql predicates and org-super-agenda group selectors... It makes me want to import the old org-element API and just use that instead.

The change is not as breaking. And I do not recall where in org-ql.el sexp representation is used.

On top of that, there is no guidance for developers to adapt their code to the new API, no helper functions or macros...?

Please refer to https://git.savannah.gnu.org/cgit/emacs/org-mode.git/tree/etc/ORG-NEWS#n59

…

-- Ihor Radchenko // yantar92, 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>

muntean-alex · 2023-08-03T18:46:50Z

@muntean-alex Meanwhile, you may need to downgrade Org mode. org-roam/org-roam#2361 has a lot of instructions how to do it.

For reference, this worked for me and fixed the issue.
Thank you very much!

maikol-solis · 2023-09-04T14:19:53Z

I had the same issue, and I thought that it was something to do with org-ql-block. I reported the problem here #38 (comment).

However, downgrading org to 9.6, solved completely the problem. In doom, I added this line into my packages.el:

(package! org :pin "806abc5a2bbcb5f884467a0145547221ba09eb59")

Best.

See #364.

alphapapa · 2023-09-04T19:50:15Z

Thanks to all for reporting. Please try the commit I just pushed on the wip/364 branch and let me know if that works on Org 9.7.

gdindi · 2023-09-11T17:00:42Z

Hi,
I have tried to replace org-ql-viel.el with the version in the wip/364 branch and I keep getting this error:

(void-function org-ql-view--resolve-element-properties)

I have byte-compiled and native-compiled (I am using native-comp). I am doing something wrong but I don't see it.

What is the recommended way of testing this? My org-ql is installed with package-install and I am using "20230908.722".

Thanks.

alphapapa · 2023-09-11T17:32:22Z

@gdindi You shouldn't try to mix and match files from different commits. You should follow the instructions in the readme to install with Quelpa, adding this to the recipe form: :branch "wip/364".

gdindi · 2023-09-11T19:33:23Z

Makes sense. Thanks. I unistalled org-ql with package-delete and installed with this in my init.el:

(quelpa
 '(org-ql 
           :fetcher github
           :repo "alphapapa/org-ql"
           :branch "wip/364"
           :files (:defaults (:exclude "helm-org-ql.el"))))
(require 'org-ql)

The package is installed in ~/.emacs.d/elpa/org-ql-20230904.214910. I restarted Emacs, but I still get this backtrace:

(void-function org-ql-view--resolve-element-properties)
org-ql-view--resolve-element-properties((headline (:standard-properties [699314 699314 699346 699691 699691 0 (:title) nil nil nil nil 699348 699691 2 #<buffer biblio.org> [org-element-deferred org-element--headline-deferred nil t] nil nil] :pre-blank 0 :raw-value [org-element-deferred org-element--headline-parse-title (nil) nil] :title [org-element-deferred org-element--headline-parse-title (nil) nil] :level [org-element-deferred org-element--headline-parse-title (nil) nil] :priority [org-element-deferred org-element--headline-parse-title (nil) nil] :tags [org-element-deferred org-element--headline-parse-title (nil) nil] :todo-keyword [org-element-deferred org-element--headline-parse-title (nil) nil] :todo-type [org-element-deferred org-element--headline-parse-title (nil) nil] :footnote-section-p [org-element-deferred org-element--headline-parse-title (nil) nil] :archivedp [org-element-deferred org-element--headline-parse-title (nil) nil] :commentedp [org-element-deferred org-element--headline-parse-title (nil) nil] :org-marker #<marker at 699314 in biblio.org> :org-hd-marker #<marker at 699314 in biblio.org>)))
org-ql-view--format-element((headline (:standard-properties [699314 699314 699346 699691 699691 0 (:title) nil nil nil nil 699348 699691 2 #<buffer biblio.org> [org-element-deferred org-element--headline-deferred nil t] nil nil] :pre-blank 0 :raw-value [org-element-deferred org-element--headline-parse-title (nil) nil] :title [org-element-deferred org-element--headline-parse-title (nil) nil] :level [org-element-deferred org-element--headline-parse-title (nil) nil] :priority [org-element-deferred org-element--headline-parse-title (nil) nil] :tags [org-element-deferred org-element--headline-parse-title (nil) nil] :todo-keyword [org-element-deferred org-element--headline-parse-title (nil) nil] :todo-type [org-element-deferred org-element--headline-parse-title (nil) nil] :footnote-section-p [org-element-deferred org-element--headline-parse-title (nil) nil] :archivedp [org-element-deferred org-element--headline-parse-title (nil) nil] :commentedp [org-element-deferred org-element--headline-parse-title (nil) nil] :org-marker #<marker at 699314 in biblio.org> :org-hd-marker #<marker at 699314 in biblio.org>)))

I don’t understand the void function message, since the code contains the defalias, but I don’t understand how defalias works wrt defun.

I may be introducing more noise than help in this issue. I just wanted to test seing that the OP had found another solution and that nobody seemed to have tested your fix.

If I can be of any help, do not hesitate to tell me what to do, but I don’t want to pollute the issue if the problem comes from my config.

Thanks.

See #364.

alphapapa · 2023-09-11T23:26:48Z

@gdindi Thanks for testing that. I think I made a mistake, wrapping the defalias call in eval-and-compile (a "thinko," I think). I just pushed to that branch again. Please try again and let me know if it works. (You may find it useful to use this command to easily upgrade the Quelpa-installed package.)

gdindi · 2023-09-12T06:08:30Z

Hi. I just tried and keep getting the same error.

alphapapa · 2023-09-12T14:16:03Z

Hi. I just tried and keep getting the same error.

Did you delete other versions of org-ql and restart Emacs before testing?

gdindi · 2023-09-12T15:42:25Z

On Tue 12-Sep-2023 at 16:16:15 +02, Adam Porter ***@***.***> wrote:

Hi. I just tried and keep getting the same error. Did you delete other versions of org-ql and restart Emacs before testing?

Yes. I also deleted the git clone in .emacs.d/quelpa to make sure quelpa was getting the most recent sources.

…

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

--

See #364.

alphapapa · 2023-09-12T22:30:31Z

Looking more closely at the backtrace, the element seems to have no :begin property at all. It looks like the value might be in the :standard-properties vector as an integer position rather than as a marker.

But I also see what appear to be some still-deferred properties, which I don't understand, because we should be forcing them to resolve here:

org-ql/org-ql-view.el

Lines 821 to 833 in 1bd7bb4

    
           (defalias 'org-ql-view--resolve-element-properties 
        
             ;; It would be preferable to define this as an inline function, but 
        
             ;; that would mean that users would have to recompile org-ql when 
        
             ;; upgrading to Org 9.7 or else get weird errors. 
        
             ;; TODO(someday): Define `org-ql-view--resolve-element-properties' as inline. 
        
             (if (version<= "9.7" org-version) 
        
                 (lambda (node) 
        
                   "Resolve NODE's properties using `org-element-properties-resolve'." 
        
                   ;; Silence warnings about `org-element-properties-resolve' 
        
                   ;; being unresolved on earlier Org versions. 
        
                   (with-no-warnings 
        
                     (org-element-properties-resolve node 'force-undefer))) 
        
               #'identity))

Maybe the problem is that the :begin property was always an integer, so org-is-habit-p was always being called in the wrong buffer, and the error is just being revealed by org-element-at-point being changed to signal an error when it's not called in an org-mode buffer now.

@gdindi Please try the commit I just pushed which changes it to use the heading marker instead. (And thank you for your help testing this!)

gdindi · 2023-09-13T05:25:10Z

I will pretend I understand your explanation ;)

Good news: it works at least with my custom searches that I use most frequently. I will keep on testing in case I find other issues.

Thanks!

yantar92 · 2023-09-13T08:07:00Z

Adam Porter ***@***.***> writes:

Anyway, I wonder if the value of `(org-element-property :begin element)` is not what is expected even after calling `(org-element-properties-resolve node 'force-undefer)`. @yantar92 Do you happen to know off the top of your head if that is the case?

org-element does not store markers (storing markers slows down editing). So, it is expected that :begin property is a number, not a marker.

…

-- Ihor Radchenko // yantar92, 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>

yantar92 · 2023-09-13T08:10:46Z

Adam Porter ***@***.***> writes:

But I also see what appear to be some still-deferred properties, which I don't understand, because we should be forcing them to resolve here: https://github.com/alphapapa/org-ql/blob/1bd7bb4af6382b00d199d9cd843fadd7e764fa82/org-ql-view.el#L821-L833

`org-element-properties-resolve' should resolve everything if it is actually called.

Maybe the problem is that the `:begin` property was always an integer, so `org-is-habit-p` was always being called in the wrong buffer, and the error is just being revealed by `org-element-at-point` being changed to signal an error when it's not called in an `org-mode` buffer now.

Most likely.

Please try the commit I just pushed which changes it to use the heading marker instead.

FYI, in Org 9.7, `org-with-point-at' can take ELEMENT as an argument and it will then set the buffer correctly, according to new :buffer ELEMENT property. Not the case in earlier Org versions though.

…

-- Ihor Radchenko // yantar92, 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>

alphapapa · 2023-09-14T13:22:38Z

@yantar92 Thanks. (And apologies for the ping; I realized afterward that I didn't need to bother you about this, but it was too late.)

alphapapa · 2023-09-14T13:23:41Z

@gdindi Thanks. I'll target this change for v0.8 of org-ql, since it's not a fix per se, and since Org 9.7 is yet to be released. Please do let me know if you find any problems.

See #364.

alphapapa · 2023-09-27T18:42:26Z

I've pushed these fixes to master under v0.8-pre. I hope they resolve this issue, but I'll leave it open for a while in case more problems are found.

To all: Please test and let me know if the problem is resolved for you. Thanks.

kunalomizer · 2023-09-28T02:33:59Z

I just upgraded and it appears to be working now. The org-ql query does execute and display the results as expected. Thank you!
Although I do still see the error in Messages : Error running timer ‘org-reveal’: (error "‘org-element-at-point’ cannot be used in non-Org buffer #<buffer Org QL View: MWTasks> (org-agenda-mode)") [19 times]

alphapapa · 2023-09-28T05:09:36Z

@kunalomizer Thanks. I don't know what's going on with that error from a timer. org-reveal is called from this hook:

org-ql/org-ql-find.el

Line 42 in ca23b1c

(defcustom org-ql-find-goto-hook '(org-show-entry org-reveal)

But that's not called from a timer:

org-ql/org-ql-find.el

Line 89 in ca23b1c

(run-hook-with-args 'org-ql-find-goto-hook))))

And I don't know what would be calling org-element-at-point in the org-ql-view buffer.

treitmaier · 2023-09-28T05:29:14Z

The error was also raised as an org-roam issue here: org-roam/org-roam#2391

alphapapa · 2023-12-16T11:51:01Z

AFAICT this is fixed. Please file a new issue if it happens again after I tag v0.8.

TristanCacqueray · 2024-09-10T11:19:00Z

@alphapapa not sure if that is expected, but the entries returned by org-ql-select (Version: 20240905.2358) may still contain deferred values. In my case I was reformatting them like this:

(defun one/format (item)
  (let* ((properties (cadr item))
         (title (plist-get properties :raw-value))
         (scheduled (plist-get properties :scheduled))
         (ts (format-time-string "%FT%T%z" (org-timestamp-to-time scheduled))))
    (format "%s %s" ts (or/remove-links title))))

This was broken by s-trim: Wrong type argument: stringp, [org-element-deferred org-element--headline-parse-title (nil) t], and I needed this tweak to fix the bug:

-(defun one/format (item)
-  (let* ((properties (cadr item))
+(defun one/format (node)
+  (let* ((item (org-element-properties-resolve node 'force-undefer))
+         (properties (cadr item))

alphapapa · 2024-09-11T00:30:58Z

@TristanCacqueray The commit that resolves this issue, 8250349, resolves the deferred node properties in the function org-ql-view--format-element, which is used in org-ql-view views. If you are directly calling org-ql-select and handling the org-element nodes yourself, you will need to handle property resolution yourself. It would not be appropriate for org-ql-select to do so automatically, because in some cases it could be unnecessary, which would cause an unnecessary performance hit.

alphapapa changed the title ~~Error when I try to run custom agenda-like org-ql command~~ Org 9.7 org-element API incompatible changes Aug 2, 2023

alphapapa added a commit that referenced this issue Sep 4, 2023

Change: Resolve Org element properties on 9.7+

acc4962

See #364.

alphapapa self-assigned this Sep 4, 2023

alphapapa added the compatibility label Sep 4, 2023

alphapapa modified the milestones: 0.7.1, 0.7.2 Sep 4, 2023

maikol-solis mentioned this issue Sep 9, 2023

Request to bump org-mode version doomemacs/doomemacs#7392

Closed

4 tasks

alphapapa added the bug label Sep 11, 2023

alphapapa added a commit that referenced this issue Sep 11, 2023

Change: Resolve Org element properties on 9.7+

635d0d9

See #364.

alphapapa added a commit that referenced this issue Sep 12, 2023

Change: Resolve Org element properties on 9.7+

068a6bc

See #364.

alphapapa added a commit that referenced this issue Sep 12, 2023

Change: Resolve Org element properties on 9.7+

bf2a146

See #364.

alphapapa added a commit that referenced this issue Sep 12, 2023

Fix: (org-ql-view--format-element) Check habit in source buffer

d09608a

See #364.

alphapapa modified the milestones: 0.7.2, 0.8 Sep 14, 2023

This was referenced Sep 22, 2023

temp buffer created in wrong mode error #374

Closed

Org 9.7 agenda appears to not set org-marker property (causing our habit selector to not work) alphapapa/org-super-agenda#247

Closed

Org-ql + doom emacs issues #375

Closed

alphapapa modified the milestones: 0.8, 0.7.3 Sep 27, 2023

alphapapa added a commit that referenced this issue Sep 27, 2023

Change: Resolve Org element properties on 9.7+

0e702ec

See #364.

alphapapa added a commit that referenced this issue Sep 27, 2023

Fix: (org-ql-view--format-element) Check habit in source buffer

9e72bf6

See #364.

alphapapa added a commit that referenced this issue Sep 27, 2023

Merge: Update for Org 9.7 org-element API changes

8250349

See #364.

alphapapa mentioned this issue Sep 28, 2023

Org 9.7 seems to break org-sidebar-tree alphapapa/org-sidebar#64

Closed

alphapapa closed this as completed Dec 16, 2023

jarofromel mentioned this issue Apr 12, 2024

refilling trees to files will stop work in org 9.7 howardabrams/hamacs#1

Open

thomaslaich mentioned this issue Jun 9, 2024

Error on org-habit-stats-view-habit-at-point after recent org-mode update ml729/org-habit-stats#10

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Org 9.7 org-element API incompatible changes #364

Org 9.7 org-element API incompatible changes #364

muntean-alex commented Aug 2, 2023

yantar92 commented Aug 2, 2023 •

edited

Loading

muntean-alex commented Aug 2, 2023

yantar92 commented Aug 2, 2023

muntean-alex commented Aug 2, 2023

yantar92 commented Aug 2, 2023

yantar92 commented Aug 2, 2023

alphapapa commented Aug 2, 2023 •

edited

Loading

yantar92 commented Aug 3, 2023 via email •

edited

Loading

muntean-alex commented Aug 3, 2023

maikol-solis commented Sep 4, 2023

alphapapa commented Sep 4, 2023

gdindi commented Sep 11, 2023

alphapapa commented Sep 11, 2023

gdindi commented Sep 11, 2023

alphapapa commented Sep 11, 2023

gdindi commented Sep 12, 2023

alphapapa commented Sep 12, 2023

gdindi commented Sep 12, 2023 via email

alphapapa commented Sep 12, 2023 •

edited

Loading

gdindi commented Sep 13, 2023

yantar92 commented Sep 13, 2023 via email

yantar92 commented Sep 13, 2023 via email

alphapapa commented Sep 14, 2023

alphapapa commented Sep 14, 2023

alphapapa commented Sep 27, 2023

kunalomizer commented Sep 28, 2023

alphapapa commented Sep 28, 2023

treitmaier commented Sep 28, 2023

alphapapa commented Dec 16, 2023

TristanCacqueray commented Sep 10, 2024

alphapapa commented Sep 11, 2024

Org 9.7 org-element API incompatible changes #364

Org 9.7 org-element API incompatible changes #364

Comments

muntean-alex commented Aug 2, 2023

yantar92 commented Aug 2, 2023 • edited Loading

muntean-alex commented Aug 2, 2023

yantar92 commented Aug 2, 2023

muntean-alex commented Aug 2, 2023

yantar92 commented Aug 2, 2023

yantar92 commented Aug 2, 2023

alphapapa commented Aug 2, 2023 • edited Loading

yantar92 commented Aug 3, 2023 via email • edited Loading

muntean-alex commented Aug 3, 2023

maikol-solis commented Sep 4, 2023

alphapapa commented Sep 4, 2023

gdindi commented Sep 11, 2023

alphapapa commented Sep 11, 2023

gdindi commented Sep 11, 2023

alphapapa commented Sep 11, 2023

gdindi commented Sep 12, 2023

alphapapa commented Sep 12, 2023

gdindi commented Sep 12, 2023 via email

alphapapa commented Sep 12, 2023 • edited Loading

gdindi commented Sep 13, 2023

yantar92 commented Sep 13, 2023 via email

yantar92 commented Sep 13, 2023 via email

alphapapa commented Sep 14, 2023

alphapapa commented Sep 14, 2023

alphapapa commented Sep 27, 2023

kunalomizer commented Sep 28, 2023

alphapapa commented Sep 28, 2023

treitmaier commented Sep 28, 2023

alphapapa commented Dec 16, 2023

TristanCacqueray commented Sep 10, 2024

alphapapa commented Sep 11, 2024

yantar92 commented Aug 2, 2023 •

edited

Loading

alphapapa commented Aug 2, 2023 •

edited

Loading

yantar92 commented Aug 3, 2023 via email •

edited

Loading

alphapapa commented Sep 12, 2023 •

edited

Loading