Oops after sending the last mail, when I closed the debug window I see this warning window below ⛔ Warning (emacs): Org version mismatch. This warning usually appears when a built-in Org version is loaded prior to the more recent Org version. Version mismatch is commonly encountered in the following situations: 1. Emacs is loaded using literate Org config and more recent Org version is loaded inside the file loaded by ‘org-babel-load-file’. ‘org-babel-load-file’ triggers the built-in Org version clashing the newer Org version attempt to be loaded later. It is recommended to move the Org loading code before the ‘org-babel-load-file’ call. 2. New Org version is loaded manually by setting ‘load-path’, but some other package depending on Org is loaded before the ‘load-path’ is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set ‘load-path’ as early in the config as possible. 3. New Org version is loaded using straight.el package manager and other package depending on Org is loaded before straight triggers loading of the newer Org version. It is recommended to put (straight-use-package 'org) early in the config. Ideally, right after the straight.el bootstrap. Moving ‘use-package’ :straight declaration may not be sufficient if the corresponding ‘use-package’ statement is deferring the loading. 4. A new Org version is synchronized with Emacs git repository and stale .elc files are still left from the previous build. It is recommended to remove .elc files from lisp/org directory and re-compile. ⛔ Warning (emacs): Org version mismatch. This warning usually appears when a built-in Org version is loaded prior to the more recent Org version. Version mismatch is commonly encountered in the following situations: 1. Emacs is loaded using literate Org config and more recent Org version is loaded inside the file loaded by ‘org-babel-load-file’. ‘org-babel-load-file’ triggers the built-in Org version clashing the newer Org version attempt to be loaded later. It is recommended to move the Org loading code before the ‘org-babel-load-file’ call. 2. New Org version is loaded manually by setting ‘load-path’, but some other package depending on Org is loaded before the ‘load-path’ is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set ‘load-path’ as early in the config as possible. 3. New Org version is loaded using straight.el package manager and other package depending on Org is loaded before straight triggers loading of the newer Org version. It is recommended to put (straight-use-package 'org) early in the config. Ideally, right after the straight.el bootstrap. Moving ‘use-package’ :straight declaration may not be sufficient if the corresponding ‘use-package’ statement is deferring the loading. 4. A new Org version is synchronized with Emacs git repository and stale .elc files are still left from the previous build. It is recommended to remove .elc files from lisp/org directory and re-compile. ⛔ Warning (emacs): Org version mismatch. This warning usually appears when a built-in Org version is loaded prior to the more recent Org version. Version mismatch is commonly encountered in the following situations: 1. Emacs is loaded using literate Org config and more recent Org version is loaded inside the file loaded by ‘org-babel-load-file’. ‘org-babel-load-file’ triggers the built-in Org version clashing the newer Org version attempt to be loaded later. It is recommended to move the Org loading code before the ‘org-babel-load-file’ call. 2. New Org version is loaded manually by setting ‘load-path’, but some other package depending on Org is loaded before the ‘load-path’ is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set ‘load-path’ as early in the config as possible. 3. New Org version is loaded using straight.el package manager and other package depending on Org is loaded before straight triggers loading of the newer Org version. It is recommended to put (straight-use-package 'org) early in the config. Ideally, right after the straight.el bootstrap. Moving ‘use-package’ :straight declaration may not be sufficient if the corresponding ‘use-package’ statement is deferring the loading. 4. A new Org version is synchronized with Emacs git repository and stale .elc files are still left from the previous build. It is recommended to remove .elc files from lisp/org directory and re-compile. ⛔ Warning (emacs): Org version mismatch. This warning usually appears when a built-in Org version is loaded prior to the more recent Org version. Version mismatch is commonly encountered in the following situations: 1. Emacs is loaded using literate Org config and more recent Org version is loaded inside the file loaded by ‘org-babel-load-file’. ‘org-babel-load-file’ triggers the built-in Org version clashing the newer Org version attempt to be loaded later. It is recommended to move the Org loading code before the ‘org-babel-load-file’ call. 2. New Org version is loaded manually by setting ‘load-path’, but some other package depending on Org is loaded before the ‘load-path’ is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set ‘load-path’ as early in the config as possible. 3. New Org version is loaded using straight.el package manager and other package depending on Org is loaded before straight triggers loading of the newer Org version. It is recommended to put (straight-use-package 'org) early in the config. Ideally, right after the straight.el bootstrap. Moving ‘use-package’ :straight declaration may not be sufficient if the corresponding ‘use-package’ statement is deferring the loading. 4. A new Org version is synchronized with Emacs git repository and stale .elc files are still left from the previous build. It is recommended to remove .elc files from lisp/org directory and re-compile. ⛔ Warning (emacs): Org version mismatch. This warning usually appears when a built-in Org version is loaded prior to the more recent Org version. Version mismatch is commonly encountered in the following situations: 1. Emacs is loaded using literate Org config and more recent Org version is loaded inside the file loaded by ‘org-babel-load-file’. ‘org-babel-load-file’ triggers the built-in Org version clashing the newer Org version attempt to be loaded later. It is recommended to move the Org loading code before the ‘org-babel-load-file’ call. 2. New Org version is loaded manually by setting ‘load-path’, but some other package depending on Org is loaded before the ‘load-path’ is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set ‘load-path’ as early in the config as possible. 3. New Org version is loaded using straight.el package manager and other package depending on Org is loaded before straight triggers loading of the newer Org version. It is recommended to put (straight-use-package 'org) early in the config. Ideally, right after the straight.el bootstrap. Moving ‘use-package’ :straight declaration may not be sufficient if the corresponding ‘use-package’ statement is deferring the loading. 4. A new Org version is synchronized with Emacs git repository and stale .elc files are still left from the previous build. It is recommended to remove .elc files from lisp/org directory and re-compile. ⛔ Warning (emacs): Org version mismatch. This warning usually appears when a built-in Org version is loaded prior to the more recent Org version. Version mismatch is commonly encountered in the following situations: 1. Emacs is loaded using literate Org config and more recent Org version is loaded inside the file loaded by ‘org-babel-load-file’. ‘org-babel-load-file’ triggers the built-in Org version clashing the newer Org version attempt to be loaded later. It is recommended to move the Org loading code before the ‘org-babel-load-file’ call. 2. New Org version is loaded manually by setting ‘load-path’, but some other package depending on Org is loaded before the ‘load-path’ is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set ‘load-path’ as early in the config as possible. 3. New Org version is loaded using straight.el package manager and other package depending on Org is loaded before straight triggers loading of the newer Org version. It is recommended to put (straight-use-package 'org) early in the config. Ideally, right after the straight.el bootstrap. Moving ‘use-package’ :straight declaration may not be sufficient if the corresponding ‘use-package’ statement is deferring the loading. 4. A new Org version is synchronized with Emacs git repository and stale .elc files are still left from the previous build. It is recommended to remove .elc files from lisp/org directory and re-compile. ⛔ Warning (emacs): Org version mismatch. This warning usually appears when a built-in Org version is loaded prior to the more recent Org version. Version mismatch is commonly encountered in the following situations: 1. Emacs is loaded using literate Org config and more recent Org version is loaded inside the file loaded by ‘org-babel-load-file’. ‘org-babel-load-file’ triggers the built-in Org version clashing the newer Org version attempt to be loaded later. It is recommended to move the Org loading code before the ‘org-babel-load-file’ call. 2. New Org version is loaded manually by setting ‘load-path’, but some other package depending on Org is loaded before the ‘load-path’ is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set ‘load-path’ as early in the config as possible. 3. New Org version is loaded using straight.el package manager and other package depending on Org is loaded before straight triggers loading of the newer Org version. It is recommended to put (straight-use-package 'org) early in the config. Ideally, right after the straight.el bootstrap. Moving ‘use-package’ :straight declaration may not be sufficient if the corresponding ‘use-package’ statement is deferring the loading. 4. A new Org version is synchronized with Emacs git repository and stale .elc files are still left from the previous build. It is recommended to remove .elc files from lisp/org directory and re-compile. ⛔ Warning (emacs): Org version mismatch. This warning usually appears when a built-in Org version is loaded prior to the more recent Org version. Version mismatch is commonly encountered in the following situations: 1. Emacs is loaded using literate Org config and more recent Org version is loaded inside the file loaded by ‘org-babel-load-file’. ‘org-babel-load-file’ triggers the built-in Org version clashing the newer Org version attempt to be loaded later. It is recommended to move the Org loading code before the ‘org-babel-load-file’ call. 2. New Org version is loaded manually by setting ‘load-path’, but some other package depending on Org is loaded before the ‘load-path’ is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set ‘load-path’ as early in the config as possible. 3. New Org version is loaded using straight.el package manager and other package depending on Org is loaded before straight triggers loading of the newer Org version. It is recommended to put (straight-use-package 'org) early in the config. Ideally, right after the straight.el bootstrap. Moving ‘use-package’ :straight declaration may not be sufficient if the corresponding ‘use-package’ statement is deferring the loading. 4. A new Org version is synchronized with Emacs git repository and stale .elc files are still left from the previous build. It is recommended to remove .elc files from lisp/org directory and re-compile. ⛔ Warning (emacs): Org version mismatch. This warning usually appears when a built-in Org version is loaded prior to the more recent Org version. Version mismatch is commonly encountered in the following situations: 1. Emacs is loaded using literate Org config and more recent Org version is loaded inside the file loaded by ‘org-babel-load-file’. ‘org-babel-load-file’ triggers the built-in Org version clashing the newer Org version attempt to be loaded later. It is recommended to move the Org loading code before the ‘org-babel-load-file’ call. 2. New Org version is loaded manually by setting ‘load-path’, but some other package depending on Org is loaded before the ‘load-path’ is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set ‘load-path’ as early in the config as possible. 3. New Org version is loaded using straight.el package manager and other package depending on Org is loaded before straight triggers loading of the newer Org version. It is recommended to put (straight-use-package 'org) early in the config. Ideally, right after the straight.el bootstrap. Moving ‘use-package’ :straight declaration may not be sufficient if the corresponding ‘use-package’ statement is deferring the loading. 4. A new Org version is synchronized with Emacs git repository and stale .elc files are still left from the previous build. It is recommended to remove .elc files from lisp/org directory and re-compile. ⛔ Warning (emacs): Org version mismatch. This warning usually appears when a built-in Org version is loaded prior to the more recent Org version. Version mismatch is commonly encountered in the following situations: 1. Emacs is loaded using literate Org config and more recent Org version is loaded inside the file loaded by ‘org-babel-load-file’. ‘org-babel-load-file’ triggers the built-in Org version clashing the newer Org version attempt to be loaded later. It is recommended to move the Org loading code before the ‘org-babel-load-file’ call. 2. New Org version is loaded manually by setting ‘load-path’, but some other package depending on Org is loaded before the ‘load-path’ is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set ‘load-path’ as early in the config as possible. 3. New Org version is loaded using straight.el package manager and other package depending on Org is loaded before straight triggers loading of the newer Org version. It is recommended to put (straight-use-package 'org) early in the config. Ideally, right after the straight.el bootstrap. Moving ‘use-package’ :straight declaration may not be sufficient if the corresponding ‘use-package’ statement is deferring the loading. 4. A new Org version is synchronized with Emacs git repository and stale .elc files are still left from the previous build. It is recommended to remove .elc files from lisp/org directory and re-compile. ⛔ Warning (emacs): Org version mismatch. This warning usually appears when a built-in Org version is loaded prior to the more recent Org version. Version mismatch is commonly encountered in the following situations: 1. Emacs is loaded using literate Org config and more recent Org version is loaded inside the file loaded by ‘org-babel-load-file’. ‘org-babel-load-file’ triggers the built-in Org version clashing the newer Org version attempt to be loaded later. It is recommended to move the Org loading code before the ‘org-babel-load-file’ call. 2. New Org version is loaded manually by setting ‘load-path’, but some other package depending on Org is loaded before the ‘load-path’ is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set ‘load-path’ as early in the config as possible. 3. New Org version is loaded using straight.el package manager and other package depending on Org is loaded before straight triggers loading of the newer Org version. It is recommended to put (straight-use-package 'org) early in the config. Ideally, right after the straight.el bootstrap. Moving ‘use-package’ :straight declaration may not be sufficient if the corresponding ‘use-package’ statement is deferring the loading. 4. A new Org version is synchronized with Emacs git repository and stale .elc files are still left from the previous build. It is recommended to remove .elc files from lisp/org directory and re-compile. ⛔ Warning (emacs): Org version mismatch. This warning usually appears when a built-in Org version is loaded prior to the more recent Org version. Version mismatch is commonly encountered in the following situations: 1. Emacs is loaded using literate Org config and more recent Org version is loaded inside the file loaded by ‘org-babel-load-file’. ‘org-babel-load-file’ triggers the built-in Org version clashing the newer Org version attempt to be loaded later. It is recommended to move the Org loading code before the ‘org-babel-load-file’ call. 2. New Org version is loaded manually by setting ‘load-path’, but some other package depending on Org is loaded before the ‘load-path’ is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set ‘load-path’ as early in the config as possible. 3. New Org version is loaded using straight.el package manager and other package depending on Org is loaded before straight triggers loading of the newer Org version. It is recommended to put (straight-use-package 'org) early in the config. Ideally, right after the straight.el bootstrap. Moving ‘use-package’ :straight declaration may not be sufficient if the corresponding ‘use-package’ statement is deferring the loading. 4. A new Org version is synchronized with Emacs git repository and stale .elc files are still left from the previous build. It is recommended to remove .elc files from lisp/org directory and re-compile. ⛔ Warning (emacs): Org version mismatch. This warning usually appears when a built-in Org version is loaded prior to the more recent Org version. Version mismatch is commonly encountered in the following situations: 1. Emacs is loaded using literate Org config and more recent Org version is loaded inside the file loaded by ‘org-babel-load-file’. ‘org-babel-load-file’ triggers the built-in Org version clashing the newer Org version attempt to be loaded later. It is recommended to move the Org loading code before the ‘org-babel-load-file’ call. 2. New Org version is loaded manually by setting ‘load-path’, but some other package depending on Org is loaded before the ‘load-path’ is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set ‘load-path’ as early in the config as possible. 3. New Org version is loaded using straight.el package manager and other package depending on Org is loaded before straight triggers loading of the newer Org version. It is recommended to put (straight-use-package 'org) early in the config. Ideally, right after the straight.el bootstrap. Moving ‘use-package’ :straight declaration may not be sufficient if the corresponding ‘use-package’ statement is deferring the loading. 4. A new Org version is synchronized with Emacs git repository and stale .elc files are still left from the previous build. It is recommended to remove .elc files from lisp/org directory and re-compile. ⛔ Warning (emacs): Org version mismatch. This warning usually appears when a built-in Org version is loaded prior to the more recent Org version. Version mismatch is commonly encountered in the following situations: 1. Emacs is loaded using literate Org config and more recent Org version is loaded inside the file loaded by ‘org-babel-load-file’. ‘org-babel-load-file’ triggers the built-in Org version clashing the newer Org version attempt to be loaded later. It is recommended to move the Org loading code before the ‘org-babel-load-file’ call. 2. New Org version is loaded manually by setting ‘load-path’, but some other package depending on Org is loaded before the ‘load-path’ is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set ‘load-path’ as early in the config as possible. 3. New Org version is loaded using straight.el package manager and other package depending on Org is loaded before straight triggers loading of the newer Org version. It is recommended to put (straight-use-package 'org) early in the config. Ideally, right after the straight.el bootstrap. Moving ‘use-package’ :straight declaration may not be sufficient if the corresponding ‘use-package’ statement is deferring the loading. 4. A new Org version is synchronized with Emacs git repository and stale .elc files are still left from the previous build. It is recommended to remove .elc files from lisp/org directory and re-compile. ⛔ Warning (emacs): Org version mismatch. This warning usually appears when a built-in Org version is loaded prior to the more recent Org version. Version mismatch is commonly encountered in the following situations: 1. Emacs is loaded using literate Org config and more recent Org version is loaded inside the file loaded by ‘org-babel-load-file’. ‘org-babel-load-file’ triggers the built-in Org version clashing the newer Org version attempt to be loaded later. It is recommended to move the Org loading code before the ‘org-babel-load-file’ call. 2. New Org version is loaded manually by setting ‘load-path’, but some other package depending on Org is loaded before the ‘load-path’ is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set ‘load-path’ as early in the config as possible. 3. New Org version is loaded using straight.el package manager and other package depending on Org is loaded before straight triggers loading of the newer Org version. It is recommended to put (straight-use-package 'org) early in the config. Ideally, right after the straight.el bootstrap. Moving ‘use-package’ :straight declaration may not be sufficient if the corresponding ‘use-package’ statement is deferring the loading. 4. A new Org version is synchronized with Emacs git repository and stale .elc files are still left from the previous build. It is recommended to remove .elc files from lisp/org directory and re-compile. ⛔ Warning (emacs): Org version mismatch. This warning usually appears when a built-in Org version is loaded prior to the more recent Org version. Version mismatch is commonly encountered in the following situations: 1. Emacs is loaded using literate Org config and more recent Org version is loaded inside the file loaded by ‘org-babel-load-file’. ‘org-babel-load-file’ triggers the built-in Org version clashing the newer Org version attempt to be loaded later. It is recommended to move the Org loading code before the ‘org-babel-load-file’ call. 2. New Org version is loaded manually by setting ‘load-path’, but some other package depending on Org is loaded before the ‘load-path’ is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set ‘load-path’ as early in the config as possible. 3. New Org version is loaded using straight.el package manager and other package depending on Org is loaded before straight triggers loading of the newer Org version. It is recommended to put (straight-use-package 'org) early in the config. Ideally, right after the straight.el bootstrap. Moving ‘use-package’ :straight declaration may not be sufficient if the corresponding ‘use-package’ statement is deferring the loading. 4. A new Org version is synchronized with Emacs git repository and stale .elc files are still left from the previous build. It is recommended to remove .elc files from lisp/org directory and re-compile. ⛔ Warning (emacs): Org version mismatch. This warning usually appears when a built-in Org version is loaded prior to the more recent Org version. Version mismatch is commonly encountered in the following situations: 1. Emacs is loaded using literate Org config and more recent Org version is loaded inside the file loaded by ‘org-babel-load-file’. ‘org-babel-load-file’ triggers the built-in Org version clashing the newer Org version attempt to be loaded later. It is recommended to move the Org loading code before the ‘org-babel-load-file’ call. 2. New Org version is loaded manually by setting ‘load-path’, but some other package depending on Org is loaded before the ‘load-path’ is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set ‘load-path’ as early in the config as possible. 3. New Org version is loaded using straight.el package manager and other package depending on Org is loaded before straight triggers loading of the newer Org version. It is recommended to put (straight-use-package 'org) early in the config. Ideally, right after the straight.el bootstrap. Moving ‘use-package’ :straight declaration may not be sufficient if the corresponding ‘use-package’ statement is deferring the loading. 4. A new Org version is synchronized with Emacs git repository and stale .elc files are still left from the previous build. It is recommended to remove .elc files from lisp/org directory and re-compile. ⛔ Warning (emacs): Org version mismatch. This warning usually appears when a built-in Org version is loaded prior to the more recent Org version. Version mismatch is commonly encountered in the following situations: 1. Emacs is loaded using literate Org config and more recent Org version is loaded inside the file loaded by ‘org-babel-load-file’. ‘org-babel-load-file’ triggers the built-in Org version clashing the newer Org version attempt to be loaded later. It is recommended to move the Org loading code before the ‘org-babel-load-file’ call. 2. New Org version is loaded manually by setting ‘load-path’, but some other package depending on Org is loaded before the ‘load-path’ is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set ‘load-path’ as early in the config as possible. 3. New Org version is loaded using straight.el package manager and other package depending on Org is loaded before straight triggers loading of the newer Org version. It is recommended to put (straight-use-package 'org) early in the config. Ideally, right after the straight.el bootstrap. Moving ‘use-package’ :straight declaration may not be sufficient if the corresponding ‘use-package’ statement is deferring the loading. 4. A new Org version is synchronized with Emacs git repository and stale .elc files are still left from the previous build. It is recommended to remove .elc files from lisp/org directory and re-compile. ⛔ Warning (emacs): Org version mismatch. This warning usually appears when a built-in Org version is loaded prior to the more recent Org version. Version mismatch is commonly encountered in the following situations: 1. Emacs is loaded using literate Org config and more recent Org version is loaded inside the file loaded by ‘org-babel-load-file’. ‘org-babel-load-file’ triggers the built-in Org version clashing the newer Org version attempt to be loaded later. It is recommended to move the Org loading code before the ‘org-babel-load-file’ call. 2. New Org version is loaded manually by setting ‘load-path’, but some other package depending on Org is loaded before the ‘load-path’ is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set ‘load-path’ as early in the config as possible. 3. New Org version is loaded using straight.el package manager and other package depending on Org is loaded before straight triggers loading of the newer Org version. It is recommended to put (straight-use-package 'org) early in the config. Ideally, right after the straight.el bootstrap. Moving ‘use-package’ :straight declaration may not be sufficient if the corresponding ‘use-package’ statement is deferring the loading. 4. A new Org version is synchronized with Emacs git repository and stale .elc files are still left from the previous build. It is recommended to remove .elc files from lisp/org directory and re-compile. ⛔ Warning (emacs): Org version mismatch. This warning usually appears when a built-in Org version is loaded prior to the more recent Org version. Version mismatch is commonly encountered in the following situations: 1. Emacs is loaded using literate Org config and more recent Org version is loaded inside the file loaded by ‘org-babel-load-file’. ‘org-babel-load-file’ triggers the built-in Org version clashing the newer Org version attempt to be loaded later. It is recommended to move the Org loading code before the ‘org-babel-load-file’ call. 2. New Org version is loaded manually by setting ‘load-path’, but some other package depending on Org is loaded before the ‘load-path’ is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set ‘load-path’ as early in the config as possible. 3. New Org version is loaded using straight.el package manager and other package depending on Org is loaded before straight triggers loading of the newer Org version. It is recommended to put (straight-use-package 'org) early in the config. Ideally, right after the straight.el bootstrap. Moving ‘use-package’ :straight declaration may not be sufficient if the corresponding ‘use-package’ statement is deferring the loading. 4. A new Org version is synchronized with Emacs git repository and stale .elc files are still left from the previous build. It is recommended to remove .elc files from lisp/org directory and re-compile. ⛔ Warning (emacs): Org version mismatch. This warning usually appears when a built-in Org version is loaded prior to the more recent Org version. Version mismatch is commonly encountered in the following situations: 1. Emacs is loaded using literate Org config and more recent Org version is loaded inside the file loaded by ‘org-babel-load-file’. ‘org-babel-load-file’ triggers the built-in Org version clashing the newer Org version attempt to be loaded later. It is recommended to move the Org loading code before the ‘org-babel-load-file’ call. 2. New Org version is loaded manually by setting ‘load-path’, but some other package depending on Org is loaded before the ‘load-path’ is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set ‘load-path’ as early in the config as possible. 3. New Org version is loaded using straight.el package manager and other package depending on Org is loaded before straight triggers loading of the newer Org version. It is recommended to put (straight-use-package 'org) early in the config. Ideally, right after the straight.el bootstrap. Moving ‘use-package’ :straight declaration may not be sufficient if the corresponding ‘use-package’ statement is deferring the loading. 4. A new Org version is synchronized with Emacs git repository and stale .elc files are still left from the previous build. It is recommended to remove .elc files from lisp/org directory and re-compile. ⛔ Warning (emacs): Org version mismatch. This warning usually appears when a built-in Org version is loaded prior to the more recent Org version. Version mismatch is commonly encountered in the following situations: 1. Emacs is loaded using literate Org config and more recent Org version is loaded inside the file loaded by ‘org-babel-load-file’. ‘org-babel-load-file’ triggers the built-in Org version clashing the newer Org version attempt to be loaded later. It is recommended to move the Org loading code before the ‘org-babel-load-file’ call. 2. New Org version is loaded manually by setting ‘load-path’, but some other package depending on Org is loaded before the ‘load-path’ is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set ‘load-path’ as early in the config as possible. 3. New Org version is loaded using straight.el package manager and other package depending on Org is loaded before straight triggers loading of the newer Org version. It is recommended to put (straight-use-package 'org) early in the config. Ideally, right after the straight.el bootstrap. Moving ‘use-package’ :straight declaration may not be sufficient if the corresponding ‘use-package’ statement is deferring the loading. 4. A new Org version is synchronized with Emacs git repository and stale .elc files are still left from the previous build. It is recommended to remove .elc files from lisp/org directory and re-compile. ⛔ Warning (emacs): Org version mismatch. This warning usually appears when a built-in Org version is loaded prior to the more recent Org version. Version mismatch is commonly encountered in the following situations: 1. Emacs is loaded using literate Org config and more recent Org version is loaded inside the file loaded by ‘org-babel-load-file’. ‘org-babel-load-file’ triggers the built-in Org version clashing the newer Org version attempt to be loaded later. It is recommended to move the Org loading code before the ‘org-babel-load-file’ call. 2. New Org version is loaded manually by setting ‘load-path’, but some other package depending on Org is loaded before the ‘load-path’ is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set ‘load-path’ as early in the config as possible. 3. New Org version is loaded using straight.el package manager and other package depending on Org is loaded before straight triggers loading of the newer Org version. It is recommended to put (straight-use-package 'org) early in the config. Ideally, right after the straight.el bootstrap. Moving ‘use-package’ :straight declaration may not be sufficient if the corresponding ‘use-package’ statement is deferring the loading. 4. A new Org version is synchronized with Emacs git repository and stale .elc files are still left from the previous build. It is recommended to remove .elc files from lisp/org directory and re-compile. ⛔ Warning (emacs): Org version mismatch. This warning usually appears when a built-in Org version is loaded prior to the more recent Org version. Version mismatch is commonly encountered in the following situations: 1. Emacs is loaded using literate Org config and more recent Org version is loaded inside the file loaded by ‘org-babel-load-file’. ‘org-babel-load-file’ triggers the built-in Org version clashing the newer Org version attempt to be loaded later. It is recommended to move the Org loading code before the ‘org-babel-load-file’ call. 2. New Org version is loaded manually by setting ‘load-path’, but some other package depending on Org is loaded before the ‘load-path’ is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set ‘load-path’ as early in the config as possible. 3. New Org version is loaded using straight.el package manager and other package depending on Org is loaded before straight triggers loading of the newer Org version. It is recommended to put (straight-use-package 'org) early in the config. Ideally, right after the straight.el bootstrap. Moving ‘use-package’ :straight declaration may not be sufficient if the corresponding ‘use-package’ statement is deferring the loading. 4. A new Org version is synchronized with Emacs git repository and stale .elc files are still left from the previous build. It is recommended to remove .elc files from lisp/org directory and re-compile.