From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1.migadu.com ([2001:41d0:303:e224::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms13.migadu.com with LMTPS id EKG2AbzEb2bsigAA62LTzQ:P1 (envelope-from ) for ; Mon, 17 Jun 2024 05:08:12 +0000 Received: from aspmx1.migadu.com ([2001:41d0:303:e224::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1.migadu.com with LMTPS id EKG2AbzEb2bsigAA62LTzQ (envelope-from ) for ; Mon, 17 Jun 2024 07:08:12 +0200 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20230601 header.b=jya6o2hd; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" ARC-Seal: i=1; s=key1; d=yhetil.org; t=1718600891; a=rsa-sha256; cv=none; b=PmXZuG3bHR3lVM+q23KnR67+8mr85MbX2yiXrwz3qHA98tqKf0XHXkhiaDYmf7RzZMPgv4 os++77TD/VJUHAd+GPCtZzhCYfbRP4kRsL3SqrinjJ3ToHFx0fBaimUy7ZyCjMzrZnpGW6 i1fkDcff3QTtq4FNb2A37s9fGL51WCYG0JR/QT3eJeX9CBIxTkmopy91QObk5HHw8Lo4EQ 5eCyXiI3JLQN5ZHjKMwkyoWDYIpPYOIfCfhKLQHbsdamu2aNwzRaae7fTwxox51I8Z9eGb vWwErasDV2dGBhGe7UIhkeeJeOFJlBNk67JZmuioEZHD+YI6jEEttFEOW1MIEA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20230601 header.b=jya6o2hd; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1718600891; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=zh9CaVcRV41n81byvCmAnPNDbHRHxgXd1IAdL+0hWXQ=; b=opFLQD7tHT0sxNuhM/T5qUqfmpRahUfo0WUP0LqH7Y/E6yHTbHAxo0j9iulK1zQF9Z8FaL 7ayQzM+GNRawJE6Yb5XrCf2LuGW+htaBLHujuDd7gHLb/tFyC3+dIOw6V7YdO1q7SCAFqa vfRMQ8ysRjm9fHtH5G01OBcIxDd/USsLwPIcpJd9fEB/fB0TpbUUkgJfOX9IuSlLr6ClDG zWys7RcF6s2uZVWFYlJAYM3UM6JRDMX4n0IL0JLBvoGVVxo0kRyuakXN0vsfRUXuUzCC24 MGSuq6nlnMofQKZquabTTQuhqwaM8xkCOrE+9/xiQd1w3CpZ6pWumE26WvA9Ww== Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 7FFB267183 for ; Mon, 17 Jun 2024 07:08:11 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sJ4aS-0002Sd-EJ; Mon, 17 Jun 2024 01:07:24 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sJ4aR-0002SG-2w for emacs-orgmode@gnu.org; Mon, 17 Jun 2024 01:07:23 -0400 Received: from mail-pg1-x536.google.com ([2607:f8b0:4864:20::536]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1sJ4aK-0006MM-P0 for emacs-orgmode@gnu.org; Mon, 17 Jun 2024 01:07:22 -0400 Received: by mail-pg1-x536.google.com with SMTP id 41be03b00d2f7-6e40d54e4a3so2963355a12.0 for ; Sun, 16 Jun 2024 22:07:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1718600835; x=1719205635; darn=gnu.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=zh9CaVcRV41n81byvCmAnPNDbHRHxgXd1IAdL+0hWXQ=; b=jya6o2hdGra4jCKAzdVlVn3Z8K7VvuELEUryOwVZPwpSjwmbu5hlLqj78NGLwjiBOw Cs7D+YBVBFOwp9AKsilVSntLMVBzMHrj3ukMD9dkr5EwJQhBbfz7tfrwxtav4MFCIHIG eM+Z659yTxl7j7bI8ZcRlJ/jyZEh9FDn8xp/HNg+Srro3cg9+tcQ4Jxjl/ZAIvSnPZ6f nq7XHYRAPEcZQaKPEWzxD67X2xrGzmCK6h+IOoOrU66/Shxk+xoN+UsdvbG+8Xj3wWOF 28+X8B0uYpDL+tVvsPDb77R33Yw3PdPerKcuhIt2kX1Ow5BtaLp47CtYIIyXV6FpUlz3 9TMw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718600835; x=1719205635; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=zh9CaVcRV41n81byvCmAnPNDbHRHxgXd1IAdL+0hWXQ=; b=bWjcUqdkl4uGHDHtND4i4zMd5bm7UpNSRaURNq7hPZu4HWBP7+rfZoT6mtagcz8QHJ 7DHooCsU0XBXsjyBkbvMqew4n0NfkBRH4Vh+2WPNd2RZtS/kNjDQ1BPnHh2wI1LGRdzx wr2Kfo/fHZpqEpkXV+NEIF01ZB4GBQEDnEwEBeeAwC6Es1/WNQvs7Jyk9FrVf4FlA9si /yedKNVCHdMETiw9bC9tMxnMv8FlIpJAloJ4BzDKImErf28ua5t9e/jagXBRlkZPV31Y /wR9CKUcwlFozLcAdJQO7P9OCAVXm/wlYLfsNfHsN7FML+TTiN3RzgHwIdtFRab4RxYF qRlg== X-Forwarded-Encrypted: i=1; AJvYcCUzoDQEzeoeBhZZ8aav6u2AE8DhadPvwDHcRQLyBdfNm00rVTwf1mlD0K4rFY0cH4rjRYyVn5X4jcLfFi8RC44/sa6s6Zw= X-Gm-Message-State: AOJu0Yw4h3HjmqYRxEXdtzoW0TODNK+ZmDDvACgbnnAZtmI1zdbP6Eyv 2jsj5RwKMbPrYWWXwCqWt5twS3OLm+00BCF5KLjGEaGx6VyvytfE2ODh4+On0AxKue5rrfAEW/1 2rF+YBzZqlzho9/i8HQAMZgJFEDKbXd+m X-Google-Smtp-Source: AGHT+IFiYvX/u4kZ7feKTATSF5S3jy3NLocj3A/d0JtAlEbaOrCNz1oFm6wZ3zXytSMRg5inTJUaAmd07QDITVZd1sM= X-Received: by 2002:a05:6a20:5601:b0:1af:fff9:30dd with SMTP id adf61e73a8af0-1bae7ed0428mr7551040637.35.1718600834401; Sun, 16 Jun 2024 22:07:14 -0700 (PDT) MIME-Version: 1.0 References: <87le36gwus.fsf@localhost> <87v829t794.fsf@localhost> In-Reply-To: From: Rustom Mody Date: Mon, 17 Jun 2024 10:37:29 +0530 Message-ID: Subject: Re: [BUG] orgalist send bug To: Ihor Radchenko Cc: Nicolas Goaziou , emacs-orgmode@gnu.org Content-Type: multipart/alternative; boundary="0000000000003ed033061b0ef00e" Received-SPF: pass client-ip=2607:f8b0:4864:20::536; envelope-from=rustompmody@gmail.com; helo=mail-pg1-x536.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Spam-Score: -9.69 X-Migadu-Scanner: mx12.migadu.com X-Spam-Score: -9.69 X-Migadu-Queue-Id: 7FFB267183 X-TUID: LbNPFMyBXleG --0000000000003ed033061b0ef00e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Oops after sending the last mail, when I closed the debug window I see this warning window below =E2=9B=94 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 =E2=80=98org-babel-load-file= =E2=80=99. =E2=80=98org-babel-load-file=E2=80=99 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 =E2=80=98org-babel-load-file=E2=80=99 call. 2. New Org version is loaded manually by setting =E2=80=98load-path=E2=80= =99, but some other package depending on Org is loaded before the =E2=80=98load-path= =E2=80=99 is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set =E2=80=98load-path=E2=80=99 as early in the con= fig 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 =E2=80=98use-package=E2=80=99 :straight declaration m= ay not be sufficient if the corresponding =E2=80=98use-package=E2=80=99 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. =E2=9B=94 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 =E2=80=98org-babel-load-file= =E2=80=99. =E2=80=98org-babel-load-file=E2=80=99 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 =E2=80=98org-babel-load-file=E2=80=99 call. 2. New Org version is loaded manually by setting =E2=80=98load-path=E2=80= =99, but some other package depending on Org is loaded before the =E2=80=98load-path= =E2=80=99 is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set =E2=80=98load-path=E2=80=99 as early in the con= fig 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 =E2=80=98use-package=E2=80=99 :straight declaration m= ay not be sufficient if the corresponding =E2=80=98use-package=E2=80=99 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. =E2=9B=94 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 =E2=80=98org-babel-load-file= =E2=80=99. =E2=80=98org-babel-load-file=E2=80=99 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 =E2=80=98org-babel-load-file=E2=80=99 call. 2. New Org version is loaded manually by setting =E2=80=98load-path=E2=80= =99, but some other package depending on Org is loaded before the =E2=80=98load-path= =E2=80=99 is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set =E2=80=98load-path=E2=80=99 as early in the con= fig 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 =E2=80=98use-package=E2=80=99 :straight declaration m= ay not be sufficient if the corresponding =E2=80=98use-package=E2=80=99 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. =E2=9B=94 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 =E2=80=98org-babel-load-file= =E2=80=99. =E2=80=98org-babel-load-file=E2=80=99 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 =E2=80=98org-babel-load-file=E2=80=99 call. 2. New Org version is loaded manually by setting =E2=80=98load-path=E2=80= =99, but some other package depending on Org is loaded before the =E2=80=98load-path= =E2=80=99 is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set =E2=80=98load-path=E2=80=99 as early in the con= fig 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 =E2=80=98use-package=E2=80=99 :straight declaration m= ay not be sufficient if the corresponding =E2=80=98use-package=E2=80=99 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. =E2=9B=94 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 =E2=80=98org-babel-load-file= =E2=80=99. =E2=80=98org-babel-load-file=E2=80=99 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 =E2=80=98org-babel-load-file=E2=80=99 call. 2. New Org version is loaded manually by setting =E2=80=98load-path=E2=80= =99, but some other package depending on Org is loaded before the =E2=80=98load-path= =E2=80=99 is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set =E2=80=98load-path=E2=80=99 as early in the con= fig 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 =E2=80=98use-package=E2=80=99 :straight declaration m= ay not be sufficient if the corresponding =E2=80=98use-package=E2=80=99 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. =E2=9B=94 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 =E2=80=98org-babel-load-file= =E2=80=99. =E2=80=98org-babel-load-file=E2=80=99 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 =E2=80=98org-babel-load-file=E2=80=99 call. 2. New Org version is loaded manually by setting =E2=80=98load-path=E2=80= =99, but some other package depending on Org is loaded before the =E2=80=98load-path= =E2=80=99 is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set =E2=80=98load-path=E2=80=99 as early in the con= fig 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 =E2=80=98use-package=E2=80=99 :straight declaration m= ay not be sufficient if the corresponding =E2=80=98use-package=E2=80=99 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. =E2=9B=94 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 =E2=80=98org-babel-load-file= =E2=80=99. =E2=80=98org-babel-load-file=E2=80=99 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 =E2=80=98org-babel-load-file=E2=80=99 call. 2. New Org version is loaded manually by setting =E2=80=98load-path=E2=80= =99, but some other package depending on Org is loaded before the =E2=80=98load-path= =E2=80=99 is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set =E2=80=98load-path=E2=80=99 as early in the con= fig 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 =E2=80=98use-package=E2=80=99 :straight declaration m= ay not be sufficient if the corresponding =E2=80=98use-package=E2=80=99 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. =E2=9B=94 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 =E2=80=98org-babel-load-file= =E2=80=99. =E2=80=98org-babel-load-file=E2=80=99 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 =E2=80=98org-babel-load-file=E2=80=99 call. 2. New Org version is loaded manually by setting =E2=80=98load-path=E2=80= =99, but some other package depending on Org is loaded before the =E2=80=98load-path= =E2=80=99 is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set =E2=80=98load-path=E2=80=99 as early in the con= fig 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 =E2=80=98use-package=E2=80=99 :straight declaration m= ay not be sufficient if the corresponding =E2=80=98use-package=E2=80=99 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. =E2=9B=94 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 =E2=80=98org-babel-load-file= =E2=80=99. =E2=80=98org-babel-load-file=E2=80=99 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 =E2=80=98org-babel-load-file=E2=80=99 call. 2. New Org version is loaded manually by setting =E2=80=98load-path=E2=80= =99, but some other package depending on Org is loaded before the =E2=80=98load-path= =E2=80=99 is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set =E2=80=98load-path=E2=80=99 as early in the con= fig 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 =E2=80=98use-package=E2=80=99 :straight declaration m= ay not be sufficient if the corresponding =E2=80=98use-package=E2=80=99 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. =E2=9B=94 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 =E2=80=98org-babel-load-file= =E2=80=99. =E2=80=98org-babel-load-file=E2=80=99 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 =E2=80=98org-babel-load-file=E2=80=99 call. 2. New Org version is loaded manually by setting =E2=80=98load-path=E2=80= =99, but some other package depending on Org is loaded before the =E2=80=98load-path= =E2=80=99 is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set =E2=80=98load-path=E2=80=99 as early in the con= fig 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 =E2=80=98use-package=E2=80=99 :straight declaration m= ay not be sufficient if the corresponding =E2=80=98use-package=E2=80=99 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. =E2=9B=94 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 =E2=80=98org-babel-load-file= =E2=80=99. =E2=80=98org-babel-load-file=E2=80=99 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 =E2=80=98org-babel-load-file=E2=80=99 call. 2. New Org version is loaded manually by setting =E2=80=98load-path=E2=80= =99, but some other package depending on Org is loaded before the =E2=80=98load-path= =E2=80=99 is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set =E2=80=98load-path=E2=80=99 as early in the con= fig 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 =E2=80=98use-package=E2=80=99 :straight declaration m= ay not be sufficient if the corresponding =E2=80=98use-package=E2=80=99 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. =E2=9B=94 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 =E2=80=98org-babel-load-file= =E2=80=99. =E2=80=98org-babel-load-file=E2=80=99 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 =E2=80=98org-babel-load-file=E2=80=99 call. 2. New Org version is loaded manually by setting =E2=80=98load-path=E2=80= =99, but some other package depending on Org is loaded before the =E2=80=98load-path= =E2=80=99 is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set =E2=80=98load-path=E2=80=99 as early in the con= fig 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 =E2=80=98use-package=E2=80=99 :straight declaration m= ay not be sufficient if the corresponding =E2=80=98use-package=E2=80=99 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. =E2=9B=94 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 =E2=80=98org-babel-load-file= =E2=80=99. =E2=80=98org-babel-load-file=E2=80=99 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 =E2=80=98org-babel-load-file=E2=80=99 call. 2. New Org version is loaded manually by setting =E2=80=98load-path=E2=80= =99, but some other package depending on Org is loaded before the =E2=80=98load-path= =E2=80=99 is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set =E2=80=98load-path=E2=80=99 as early in the con= fig 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 =E2=80=98use-package=E2=80=99 :straight declaration m= ay not be sufficient if the corresponding =E2=80=98use-package=E2=80=99 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. =E2=9B=94 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 =E2=80=98org-babel-load-file= =E2=80=99. =E2=80=98org-babel-load-file=E2=80=99 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 =E2=80=98org-babel-load-file=E2=80=99 call. 2. New Org version is loaded manually by setting =E2=80=98load-path=E2=80= =99, but some other package depending on Org is loaded before the =E2=80=98load-path= =E2=80=99 is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set =E2=80=98load-path=E2=80=99 as early in the con= fig 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 =E2=80=98use-package=E2=80=99 :straight declaration m= ay not be sufficient if the corresponding =E2=80=98use-package=E2=80=99 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. =E2=9B=94 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 =E2=80=98org-babel-load-file= =E2=80=99. =E2=80=98org-babel-load-file=E2=80=99 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 =E2=80=98org-babel-load-file=E2=80=99 call. 2. New Org version is loaded manually by setting =E2=80=98load-path=E2=80= =99, but some other package depending on Org is loaded before the =E2=80=98load-path= =E2=80=99 is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set =E2=80=98load-path=E2=80=99 as early in the con= fig 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 =E2=80=98use-package=E2=80=99 :straight declaration m= ay not be sufficient if the corresponding =E2=80=98use-package=E2=80=99 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. =E2=9B=94 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 =E2=80=98org-babel-load-file= =E2=80=99. =E2=80=98org-babel-load-file=E2=80=99 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 =E2=80=98org-babel-load-file=E2=80=99 call. 2. New Org version is loaded manually by setting =E2=80=98load-path=E2=80= =99, but some other package depending on Org is loaded before the =E2=80=98load-path= =E2=80=99 is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set =E2=80=98load-path=E2=80=99 as early in the con= fig 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 =E2=80=98use-package=E2=80=99 :straight declaration m= ay not be sufficient if the corresponding =E2=80=98use-package=E2=80=99 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. =E2=9B=94 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 =E2=80=98org-babel-load-file= =E2=80=99. =E2=80=98org-babel-load-file=E2=80=99 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 =E2=80=98org-babel-load-file=E2=80=99 call. 2. New Org version is loaded manually by setting =E2=80=98load-path=E2=80= =99, but some other package depending on Org is loaded before the =E2=80=98load-path= =E2=80=99 is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set =E2=80=98load-path=E2=80=99 as early in the con= fig 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 =E2=80=98use-package=E2=80=99 :straight declaration m= ay not be sufficient if the corresponding =E2=80=98use-package=E2=80=99 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. =E2=9B=94 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 =E2=80=98org-babel-load-file= =E2=80=99. =E2=80=98org-babel-load-file=E2=80=99 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 =E2=80=98org-babel-load-file=E2=80=99 call. 2. New Org version is loaded manually by setting =E2=80=98load-path=E2=80= =99, but some other package depending on Org is loaded before the =E2=80=98load-path= =E2=80=99 is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set =E2=80=98load-path=E2=80=99 as early in the con= fig 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 =E2=80=98use-package=E2=80=99 :straight declaration m= ay not be sufficient if the corresponding =E2=80=98use-package=E2=80=99 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. =E2=9B=94 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 =E2=80=98org-babel-load-file= =E2=80=99. =E2=80=98org-babel-load-file=E2=80=99 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 =E2=80=98org-babel-load-file=E2=80=99 call. 2. New Org version is loaded manually by setting =E2=80=98load-path=E2=80= =99, but some other package depending on Org is loaded before the =E2=80=98load-path= =E2=80=99 is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set =E2=80=98load-path=E2=80=99 as early in the con= fig 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 =E2=80=98use-package=E2=80=99 :straight declaration m= ay not be sufficient if the corresponding =E2=80=98use-package=E2=80=99 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. =E2=9B=94 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 =E2=80=98org-babel-load-file= =E2=80=99. =E2=80=98org-babel-load-file=E2=80=99 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 =E2=80=98org-babel-load-file=E2=80=99 call. 2. New Org version is loaded manually by setting =E2=80=98load-path=E2=80= =99, but some other package depending on Org is loaded before the =E2=80=98load-path= =E2=80=99 is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set =E2=80=98load-path=E2=80=99 as early in the con= fig 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 =E2=80=98use-package=E2=80=99 :straight declaration m= ay not be sufficient if the corresponding =E2=80=98use-package=E2=80=99 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. =E2=9B=94 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 =E2=80=98org-babel-load-file= =E2=80=99. =E2=80=98org-babel-load-file=E2=80=99 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 =E2=80=98org-babel-load-file=E2=80=99 call. 2. New Org version is loaded manually by setting =E2=80=98load-path=E2=80= =99, but some other package depending on Org is loaded before the =E2=80=98load-path= =E2=80=99 is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set =E2=80=98load-path=E2=80=99 as early in the con= fig 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 =E2=80=98use-package=E2=80=99 :straight declaration m= ay not be sufficient if the corresponding =E2=80=98use-package=E2=80=99 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. =E2=9B=94 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 =E2=80=98org-babel-load-file= =E2=80=99. =E2=80=98org-babel-load-file=E2=80=99 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 =E2=80=98org-babel-load-file=E2=80=99 call. 2. New Org version is loaded manually by setting =E2=80=98load-path=E2=80= =99, but some other package depending on Org is loaded before the =E2=80=98load-path= =E2=80=99 is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set =E2=80=98load-path=E2=80=99 as early in the con= fig 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 =E2=80=98use-package=E2=80=99 :straight declaration m= ay not be sufficient if the corresponding =E2=80=98use-package=E2=80=99 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. =E2=9B=94 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 =E2=80=98org-babel-load-file= =E2=80=99. =E2=80=98org-babel-load-file=E2=80=99 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 =E2=80=98org-babel-load-file=E2=80=99 call. 2. New Org version is loaded manually by setting =E2=80=98load-path=E2=80= =99, but some other package depending on Org is loaded before the =E2=80=98load-path= =E2=80=99 is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set =E2=80=98load-path=E2=80=99 as early in the con= fig 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 =E2=80=98use-package=E2=80=99 :straight declaration m= ay not be sufficient if the corresponding =E2=80=98use-package=E2=80=99 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. =E2=9B=94 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 =E2=80=98org-babel-load-file= =E2=80=99. =E2=80=98org-babel-load-file=E2=80=99 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 =E2=80=98org-babel-load-file=E2=80=99 call. 2. New Org version is loaded manually by setting =E2=80=98load-path=E2=80= =99, but some other package depending on Org is loaded before the =E2=80=98load-path= =E2=80=99 is configured. This "other package" is triggering built-in Org version, again causing the version mismatch. It is recommended to set =E2=80=98load-path=E2=80=99 as early in the con= fig 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 =E2=80=98use-package=E2=80=99 :straight declaration m= ay not be sufficient if the corresponding =E2=80=98use-package=E2=80=99 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. --0000000000003ed033061b0ef00e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Oops after sending the last mail, wh= en I closed the debug window I see this warning window below

=
=E2=9B=94 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
=C2=A0 =C2=A0version is loaded inside the file loade= d by =E2=80=98org-babel-load-file=E2=80=99.
=C2=A0 =C2=A0=E2=80=98org-ba= bel-load-file=E2=80=99 triggers the built-in Org version clashing
=C2=A0= =C2=A0the newer Org version attempt to be loaded later.

=C2=A0 =C2= =A0It is recommended to move the Org loading code before the
=C2=A0 =C2= =A0=E2=80=98org-babel-load-file=E2=80=99 call.

2. New Org version is= loaded manually by setting =E2=80=98load-path=E2=80=99, but some
=C2=A0= =C2=A0other package depending on Org is loaded before the =E2=80=98load-pa= th=E2=80=99 is
=C2=A0 =C2=A0configured.
=C2=A0 =C2=A0This "other= package" is triggering built-in Org version, again
=C2=A0 =C2=A0ca= using the version mismatch.

=C2=A0 =C2=A0It is recommended to set = =E2=80=98load-path=E2=80=99 as early in the config as
=C2=A0 =C2=A0possi= ble.

3. New Org version is loaded using straight.el package manager = and
=C2=A0 =C2=A0other package depending on Org is loaded before straigh= t triggers
=C2=A0 =C2=A0loading of the newer Org version.

=C2=A0 = =C2=A0It is recommended to put

=C2=A0 =C2=A0 (straight-use-package &= #39;org)

=C2=A0 =C2=A0early in the config.=C2=A0 Ideally, right afte= r the straight.el
=C2=A0 =C2=A0bootstrap.=C2=A0 Moving =E2=80=98use-pack= age=E2=80=99 :straight declaration may not be
=C2=A0 =C2=A0sufficient if= the corresponding =E2=80=98use-package=E2=80=99 statement is
=C2=A0 =C2= =A0deferring the loading.

4. A new Org version is synchronized with = Emacs git repository and
=C2=A0 =C2=A0stale .elc files are still left fr= om the previous build.

=C2=A0 =C2=A0It is recommended to remove .elc= files from lisp/org directory and
=C2=A0 =C2=A0re-compile.
=E2=9B=94= Warning (emacs): Org version mismatch.
This warning usually appears whe= n a built-in Org version is loaded
prior to the more recent Org version.=

Version mismatch is commonly encountered in the following situation= s:

1. Emacs is loaded using literate Org config and more recent Org<= br>=C2=A0 =C2=A0version is loaded inside the file loaded by =E2=80=98org-ba= bel-load-file=E2=80=99.
=C2=A0 =C2=A0=E2=80=98org-babel-load-file=E2=80= =99 triggers the built-in Org version clashing
=C2=A0 =C2=A0the newer Or= g version attempt to be loaded later.

=C2=A0 =C2=A0It is recommended= to move the Org loading code before the
=C2=A0 =C2=A0=E2=80=98org-babel= -load-file=E2=80=99 call.

2. New Org version is loaded manually by s= etting =E2=80=98load-path=E2=80=99, but some
=C2=A0 =C2=A0other package = depending on Org is loaded before the =E2=80=98load-path=E2=80=99 is
=C2= =A0 =C2=A0configured.
=C2=A0 =C2=A0This "other package" is tri= ggering built-in Org version, again
=C2=A0 =C2=A0causing the version mis= match.

=C2=A0 =C2=A0It is recommended to set =E2=80=98load-path=E2= =80=99 as early in the config as
=C2=A0 =C2=A0possible.

3. New Or= g version is loaded using straight.el package manager and
=C2=A0 =C2=A0o= ther package depending on Org is loaded before straight triggers
=C2=A0 = =C2=A0loading of the newer Org version.

=C2=A0 =C2=A0It is recommend= ed to put

=C2=A0 =C2=A0 (straight-use-package 'org)

=C2= =A0 =C2=A0early in the config.=C2=A0 Ideally, right after the straight.el=C2=A0 =C2=A0bootstrap.=C2=A0 Moving =E2=80=98use-package=E2=80=99 :strai= ght declaration may not be
=C2=A0 =C2=A0sufficient if the corresponding = =E2=80=98use-package=E2=80=99 statement is
=C2=A0 =C2=A0deferring the lo= ading.

4. A new Org version is synchronized with Emacs git repositor= y and
=C2=A0 =C2=A0stale .elc files are still left from the previous bui= ld.

=C2=A0 =C2=A0It is recommended to remove .elc files from lisp/or= g directory and
=C2=A0 =C2=A0re-compile.
=E2=9B=94 Warning (emacs): O= rg version mismatch.
This warning usually appears when a built-in Org ve= rsion is loaded
prior to the more recent Org version.

Version mis= match is commonly encountered in the following situations:

1. Emacs = is loaded using literate Org config and more recent Org
=C2=A0 =C2=A0ver= sion is loaded inside the file loaded by =E2=80=98org-babel-load-file=E2=80= =99.
=C2=A0 =C2=A0=E2=80=98org-babel-load-file=E2=80=99 triggers the bui= lt-in Org version clashing
=C2=A0 =C2=A0the newer Org version attempt to= be loaded later.

=C2=A0 =C2=A0It is recommended to move the Org loa= ding code before the
=C2=A0 =C2=A0=E2=80=98org-babel-load-file=E2=80=99 = call.

2. New Org version is loaded manually by setting =E2=80=98load= -path=E2=80=99, but some
=C2=A0 =C2=A0other package depending on Org is = loaded before the =E2=80=98load-path=E2=80=99 is
=C2=A0 =C2=A0configured= .
=C2=A0 =C2=A0This "other package" is triggering built-in Org= version, again
=C2=A0 =C2=A0causing the version mismatch.

=C2=A0= =C2=A0It is recommended to set =E2=80=98load-path=E2=80=99 as early in the= config as
=C2=A0 =C2=A0possible.

3. New Org version is loaded us= ing straight.el package manager and
=C2=A0 =C2=A0other package depending= on Org is loaded before straight triggers
=C2=A0 =C2=A0loading of the n= ewer Org version.

=C2=A0 =C2=A0It is recommended to put

=C2= =A0 =C2=A0 (straight-use-package 'org)

=C2=A0 =C2=A0early in the= config.=C2=A0 Ideally, right after the straight.el
=C2=A0 =C2=A0bootstr= ap.=C2=A0 Moving =E2=80=98use-package=E2=80=99 :straight declaration may no= t be
=C2=A0 =C2=A0sufficient if the corresponding =E2=80=98use-package= =E2=80=99 statement is
=C2=A0 =C2=A0deferring the loading.

4. A n= ew Org version is synchronized with Emacs git repository and
=C2=A0 =C2= =A0stale .elc files are still left from the previous build.

=C2=A0 = =C2=A0It is recommended to remove .elc files from lisp/org directory and=C2=A0 =C2=A0re-compile.
=E2=9B=94 Warning (emacs): Org version mismatc= h.
This warning usually appears when a built-in Org version is loadedprior to the more recent Org version.

Version mismatch is commonly = encountered in the following situations:

1. Emacs is loaded using li= terate Org config and more recent Org
=C2=A0 =C2=A0version is loaded ins= ide the file loaded by =E2=80=98org-babel-load-file=E2=80=99.
=C2=A0 =C2= =A0=E2=80=98org-babel-load-file=E2=80=99 triggers the built-in Org version = clashing
=C2=A0 =C2=A0the newer Org version attempt to be loaded later.<= br>
=C2=A0 =C2=A0It is recommended to move the Org loading code before t= he
=C2=A0 =C2=A0=E2=80=98org-babel-load-file=E2=80=99 call.

2. Ne= w Org version is loaded manually by setting =E2=80=98load-path=E2=80=99, bu= t some
=C2=A0 =C2=A0other package depending on Org is loaded before the = =E2=80=98load-path=E2=80=99 is
=C2=A0 =C2=A0configured.
=C2=A0 =C2=A0= This "other package" is triggering built-in Org version, again=C2=A0 =C2=A0causing the version mismatch.

=C2=A0 =C2=A0It is recom= mended to set =E2=80=98load-path=E2=80=99 as early in the config as
=C2= =A0 =C2=A0possible.

3. New Org version is loaded using straight.el p= ackage manager and
=C2=A0 =C2=A0other package depending on Org is loaded= before straight triggers
=C2=A0 =C2=A0loading of the newer Org version.=

=C2=A0 =C2=A0It is recommended to put

=C2=A0 =C2=A0 (straigh= t-use-package 'org)

=C2=A0 =C2=A0early in the config.=C2=A0 Idea= lly, right after the straight.el
=C2=A0 =C2=A0bootstrap.=C2=A0 Moving = =E2=80=98use-package=E2=80=99 :straight declaration may not be
=C2=A0 = =C2=A0sufficient if the corresponding =E2=80=98use-package=E2=80=99 stateme= nt is
=C2=A0 =C2=A0deferring the loading.

4. A new Org version is= synchronized with Emacs git repository and
=C2=A0 =C2=A0stale .elc file= s are still left from the previous build.

=C2=A0 =C2=A0It is recomme= nded to remove .elc files from lisp/org directory and
=C2=A0 =C2=A0re-co= mpile.
=E2=9B=94 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 a= nd more recent Org
=C2=A0 =C2=A0version is loaded inside the file loaded= by =E2=80=98org-babel-load-file=E2=80=99.
=C2=A0 =C2=A0=E2=80=98org-bab= el-load-file=E2=80=99 triggers the built-in Org version clashing
=C2=A0 = =C2=A0the newer Org version attempt to be loaded later.

=C2=A0 =C2= =A0It is recommended to move the Org loading code before the
=C2=A0 =C2= =A0=E2=80=98org-babel-load-file=E2=80=99 call.

2. New Org version is= loaded manually by setting =E2=80=98load-path=E2=80=99, but some
=C2=A0= =C2=A0other package depending on Org is loaded before the =E2=80=98load-pa= th=E2=80=99 is
=C2=A0 =C2=A0configured.
=C2=A0 =C2=A0This "other= package" is triggering built-in Org version, again
=C2=A0 =C2=A0ca= using the version mismatch.

=C2=A0 =C2=A0It is recommended to set = =E2=80=98load-path=E2=80=99 as early in the config as
=C2=A0 =C2=A0possi= ble.

3. New Org version is loaded using straight.el package manager = and
=C2=A0 =C2=A0other package depending on Org is loaded before straigh= t triggers
=C2=A0 =C2=A0loading of the newer Org version.

=C2=A0 = =C2=A0It is recommended to put

=C2=A0 =C2=A0 (straight-use-package &= #39;org)

=C2=A0 =C2=A0early in the config.=C2=A0 Ideally, right afte= r the straight.el
=C2=A0 =C2=A0bootstrap.=C2=A0 Moving =E2=80=98use-pack= age=E2=80=99 :straight declaration may not be
=C2=A0 =C2=A0sufficient if= the corresponding =E2=80=98use-package=E2=80=99 statement is
=C2=A0 =C2= =A0deferring the loading.

4. A new Org version is synchronized with = Emacs git repository and
=C2=A0 =C2=A0stale .elc files are still left fr= om the previous build.

=C2=A0 =C2=A0It is recommended to remove .elc= files from lisp/org directory and
=C2=A0 =C2=A0re-compile.
=E2=9B=94= Warning (emacs): Org version mismatch.
This warning usually appears whe= n a built-in Org version is loaded
prior to the more recent Org version.=

Version mismatch is commonly encountered in the following situation= s:

1. Emacs is loaded using literate Org config and more recent Org<= br>=C2=A0 =C2=A0version is loaded inside the file loaded by =E2=80=98org-ba= bel-load-file=E2=80=99.
=C2=A0 =C2=A0=E2=80=98org-babel-load-file=E2=80= =99 triggers the built-in Org version clashing
=C2=A0 =C2=A0the newer Or= g version attempt to be loaded later.

=C2=A0 =C2=A0It is recommended= to move the Org loading code before the
=C2=A0 =C2=A0=E2=80=98org-babel= -load-file=E2=80=99 call.

2. New Org version is loaded manually by s= etting =E2=80=98load-path=E2=80=99, but some
=C2=A0 =C2=A0other package = depending on Org is loaded before the =E2=80=98load-path=E2=80=99 is
=C2= =A0 =C2=A0configured.
=C2=A0 =C2=A0This "other package" is tri= ggering built-in Org version, again
=C2=A0 =C2=A0causing the version mis= match.

=C2=A0 =C2=A0It is recommended to set =E2=80=98load-path=E2= =80=99 as early in the config as
=C2=A0 =C2=A0possible.

3. New Or= g version is loaded using straight.el package manager and
=C2=A0 =C2=A0o= ther package depending on Org is loaded before straight triggers
=C2=A0 = =C2=A0loading of the newer Org version.

=C2=A0 =C2=A0It is recommend= ed to put

=C2=A0 =C2=A0 (straight-use-package 'org)

=C2= =A0 =C2=A0early in the config.=C2=A0 Ideally, right after the straight.el=C2=A0 =C2=A0bootstrap.=C2=A0 Moving =E2=80=98use-package=E2=80=99 :strai= ght declaration may not be
=C2=A0 =C2=A0sufficient if the corresponding = =E2=80=98use-package=E2=80=99 statement is
=C2=A0 =C2=A0deferring the lo= ading.

4. A new Org version is synchronized with Emacs git repositor= y and
=C2=A0 =C2=A0stale .elc files are still left from the previous bui= ld.

=C2=A0 =C2=A0It is recommended to remove .elc files from lisp/or= g directory and
=C2=A0 =C2=A0re-compile.
=E2=9B=94 Warning (emacs): O= rg version mismatch.
This warning usually appears when a built-in Org ve= rsion is loaded
prior to the more recent Org version.

Version mis= match is commonly encountered in the following situations:

1. Emacs = is loaded using literate Org config and more recent Org
=C2=A0 =C2=A0ver= sion is loaded inside the file loaded by =E2=80=98org-babel-load-file=E2=80= =99.
=C2=A0 =C2=A0=E2=80=98org-babel-load-file=E2=80=99 triggers the bui= lt-in Org version clashing
=C2=A0 =C2=A0the newer Org version attempt to= be loaded later.

=C2=A0 =C2=A0It is recommended to move the Org loa= ding code before the
=C2=A0 =C2=A0=E2=80=98org-babel-load-file=E2=80=99 = call.

2. New Org version is loaded manually by setting =E2=80=98load= -path=E2=80=99, but some
=C2=A0 =C2=A0other package depending on Org is = loaded before the =E2=80=98load-path=E2=80=99 is
=C2=A0 =C2=A0configured= .
=C2=A0 =C2=A0This "other package" is triggering built-in Org= version, again
=C2=A0 =C2=A0causing the version mismatch.

=C2=A0= =C2=A0It is recommended to set =E2=80=98load-path=E2=80=99 as early in the= config as
=C2=A0 =C2=A0possible.

3. New Org version is loaded us= ing straight.el package manager and
=C2=A0 =C2=A0other package depending= on Org is loaded before straight triggers
=C2=A0 =C2=A0loading of the n= ewer Org version.

=C2=A0 =C2=A0It is recommended to put

=C2= =A0 =C2=A0 (straight-use-package 'org)

=C2=A0 =C2=A0early in the= config.=C2=A0 Ideally, right after the straight.el
=C2=A0 =C2=A0bootstr= ap.=C2=A0 Moving =E2=80=98use-package=E2=80=99 :straight declaration may no= t be
=C2=A0 =C2=A0sufficient if the corresponding =E2=80=98use-package= =E2=80=99 statement is
=C2=A0 =C2=A0deferring the loading.

4. A n= ew Org version is synchronized with Emacs git repository and
=C2=A0 =C2= =A0stale .elc files are still left from the previous build.

=C2=A0 = =C2=A0It is recommended to remove .elc files from lisp/org directory and=C2=A0 =C2=A0re-compile.
=E2=9B=94 Warning (emacs): Org version mismatc= h.
This warning usually appears when a built-in Org version is loadedprior to the more recent Org version.

Version mismatch is commonly = encountered in the following situations:

1. Emacs is loaded using li= terate Org config and more recent Org
=C2=A0 =C2=A0version is loaded ins= ide the file loaded by =E2=80=98org-babel-load-file=E2=80=99.
=C2=A0 =C2= =A0=E2=80=98org-babel-load-file=E2=80=99 triggers the built-in Org version = clashing
=C2=A0 =C2=A0the newer Org version attempt to be loaded later.<= br>
=C2=A0 =C2=A0It is recommended to move the Org loading code before t= he
=C2=A0 =C2=A0=E2=80=98org-babel-load-file=E2=80=99 call.

2. Ne= w Org version is loaded manually by setting =E2=80=98load-path=E2=80=99, bu= t some
=C2=A0 =C2=A0other package depending on Org is loaded before the = =E2=80=98load-path=E2=80=99 is
=C2=A0 =C2=A0configured.
=C2=A0 =C2=A0= This "other package" is triggering built-in Org version, again=C2=A0 =C2=A0causing the version mismatch.

=C2=A0 =C2=A0It is recom= mended to set =E2=80=98load-path=E2=80=99 as early in the config as
=C2= =A0 =C2=A0possible.

3. New Org version is loaded using straight.el p= ackage manager and
=C2=A0 =C2=A0other package depending on Org is loaded= before straight triggers
=C2=A0 =C2=A0loading of the newer Org version.=

=C2=A0 =C2=A0It is recommended to put

=C2=A0 =C2=A0 (straigh= t-use-package 'org)

=C2=A0 =C2=A0early in the config.=C2=A0 Idea= lly, right after the straight.el
=C2=A0 =C2=A0bootstrap.=C2=A0 Moving = =E2=80=98use-package=E2=80=99 :straight declaration may not be
=C2=A0 = =C2=A0sufficient if the corresponding =E2=80=98use-package=E2=80=99 stateme= nt is
=C2=A0 =C2=A0deferring the loading.

4. A new Org version is= synchronized with Emacs git repository and
=C2=A0 =C2=A0stale .elc file= s are still left from the previous build.

=C2=A0 =C2=A0It is recomme= nded to remove .elc files from lisp/org directory and
=C2=A0 =C2=A0re-co= mpile.
=E2=9B=94 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 a= nd more recent Org
=C2=A0 =C2=A0version is loaded inside the file loaded= by =E2=80=98org-babel-load-file=E2=80=99.
=C2=A0 =C2=A0=E2=80=98org-bab= el-load-file=E2=80=99 triggers the built-in Org version clashing
=C2=A0 = =C2=A0the newer Org version attempt to be loaded later.

=C2=A0 =C2= =A0It is recommended to move the Org loading code before the
=C2=A0 =C2= =A0=E2=80=98org-babel-load-file=E2=80=99 call.

2. New Org version is= loaded manually by setting =E2=80=98load-path=E2=80=99, but some
=C2=A0= =C2=A0other package depending on Org is loaded before the =E2=80=98load-pa= th=E2=80=99 is
=C2=A0 =C2=A0configured.
=C2=A0 =C2=A0This "other= package" is triggering built-in Org version, again
=C2=A0 =C2=A0ca= using the version mismatch.

=C2=A0 =C2=A0It is recommended to set = =E2=80=98load-path=E2=80=99 as early in the config as
=C2=A0 =C2=A0possi= ble.

3. New Org version is loaded using straight.el package manager = and
=C2=A0 =C2=A0other package depending on Org is loaded before straigh= t triggers
=C2=A0 =C2=A0loading of the newer Org version.

=C2=A0 = =C2=A0It is recommended to put

=C2=A0 =C2=A0 (straight-use-package &= #39;org)

=C2=A0 =C2=A0early in the config.=C2=A0 Ideally, right afte= r the straight.el
=C2=A0 =C2=A0bootstrap.=C2=A0 Moving =E2=80=98use-pack= age=E2=80=99 :straight declaration may not be
=C2=A0 =C2=A0sufficient if= the corresponding =E2=80=98use-package=E2=80=99 statement is
=C2=A0 =C2= =A0deferring the loading.

4. A new Org version is synchronized with = Emacs git repository and
=C2=A0 =C2=A0stale .elc files are still left fr= om the previous build.

=C2=A0 =C2=A0It is recommended to remove .elc= files from lisp/org directory and
=C2=A0 =C2=A0re-compile.
=E2=9B=94= Warning (emacs): Org version mismatch.
This warning usually appears whe= n a built-in Org version is loaded
prior to the more recent Org version.=

Version mismatch is commonly encountered in the following situation= s:

1. Emacs is loaded using literate Org config and more recent Org<= br>=C2=A0 =C2=A0version is loaded inside the file loaded by =E2=80=98org-ba= bel-load-file=E2=80=99.
=C2=A0 =C2=A0=E2=80=98org-babel-load-file=E2=80= =99 triggers the built-in Org version clashing
=C2=A0 =C2=A0the newer Or= g version attempt to be loaded later.

=C2=A0 =C2=A0It is recommended= to move the Org loading code before the
=C2=A0 =C2=A0=E2=80=98org-babel= -load-file=E2=80=99 call.

2. New Org version is loaded manually by s= etting =E2=80=98load-path=E2=80=99, but some
=C2=A0 =C2=A0other package = depending on Org is loaded before the =E2=80=98load-path=E2=80=99 is
=C2= =A0 =C2=A0configured.
=C2=A0 =C2=A0This "other package" is tri= ggering built-in Org version, again
=C2=A0 =C2=A0causing the version mis= match.

=C2=A0 =C2=A0It is recommended to set =E2=80=98load-path=E2= =80=99 as early in the config as
=C2=A0 =C2=A0possible.

3. New Or= g version is loaded using straight.el package manager and
=C2=A0 =C2=A0o= ther package depending on Org is loaded before straight triggers
=C2=A0 = =C2=A0loading of the newer Org version.

=C2=A0 =C2=A0It is recommend= ed to put

=C2=A0 =C2=A0 (straight-use-package 'org)

=C2= =A0 =C2=A0early in the config.=C2=A0 Ideally, right after the straight.el=C2=A0 =C2=A0bootstrap.=C2=A0 Moving =E2=80=98use-package=E2=80=99 :strai= ght declaration may not be
=C2=A0 =C2=A0sufficient if the corresponding = =E2=80=98use-package=E2=80=99 statement is
=C2=A0 =C2=A0deferring the lo= ading.

4. A new Org version is synchronized with Emacs git repositor= y and
=C2=A0 =C2=A0stale .elc files are still left from the previous bui= ld.

=C2=A0 =C2=A0It is recommended to remove .elc files from lisp/or= g directory and
=C2=A0 =C2=A0re-compile.
=E2=9B=94 Warning (emacs): O= rg version mismatch.
This warning usually appears when a built-in Org ve= rsion is loaded
prior to the more recent Org version.

Version mis= match is commonly encountered in the following situations:

1. Emacs = is loaded using literate Org config and more recent Org
=C2=A0 =C2=A0ver= sion is loaded inside the file loaded by =E2=80=98org-babel-load-file=E2=80= =99.
=C2=A0 =C2=A0=E2=80=98org-babel-load-file=E2=80=99 triggers the bui= lt-in Org version clashing
=C2=A0 =C2=A0the newer Org version attempt to= be loaded later.

=C2=A0 =C2=A0It is recommended to move the Org loa= ding code before the
=C2=A0 =C2=A0=E2=80=98org-babel-load-file=E2=80=99 = call.

2. New Org version is loaded manually by setting =E2=80=98load= -path=E2=80=99, but some
=C2=A0 =C2=A0other package depending on Org is = loaded before the =E2=80=98load-path=E2=80=99 is
=C2=A0 =C2=A0configured= .
=C2=A0 =C2=A0This "other package" is triggering built-in Org= version, again
=C2=A0 =C2=A0causing the version mismatch.

=C2=A0= =C2=A0It is recommended to set =E2=80=98load-path=E2=80=99 as early in the= config as
=C2=A0 =C2=A0possible.

3. New Org version is loaded us= ing straight.el package manager and
=C2=A0 =C2=A0other package depending= on Org is loaded before straight triggers
=C2=A0 =C2=A0loading of the n= ewer Org version.

=C2=A0 =C2=A0It is recommended to put

=C2= =A0 =C2=A0 (straight-use-package 'org)

=C2=A0 =C2=A0early in the= config.=C2=A0 Ideally, right after the straight.el
=C2=A0 =C2=A0bootstr= ap.=C2=A0 Moving =E2=80=98use-package=E2=80=99 :straight declaration may no= t be
=C2=A0 =C2=A0sufficient if the corresponding =E2=80=98use-package= =E2=80=99 statement is
=C2=A0 =C2=A0deferring the loading.

4. A n= ew Org version is synchronized with Emacs git repository and
=C2=A0 =C2= =A0stale .elc files are still left from the previous build.

=C2=A0 = =C2=A0It is recommended to remove .elc files from lisp/org directory and=C2=A0 =C2=A0re-compile.
=E2=9B=94 Warning (emacs): Org version mismatc= h.
This warning usually appears when a built-in Org version is loadedprior to the more recent Org version.

Version mismatch is commonly = encountered in the following situations:

1. Emacs is loaded using li= terate Org config and more recent Org
=C2=A0 =C2=A0version is loaded ins= ide the file loaded by =E2=80=98org-babel-load-file=E2=80=99.
=C2=A0 =C2= =A0=E2=80=98org-babel-load-file=E2=80=99 triggers the built-in Org version = clashing
=C2=A0 =C2=A0the newer Org version attempt to be loaded later.<= br>
=C2=A0 =C2=A0It is recommended to move the Org loading code before t= he
=C2=A0 =C2=A0=E2=80=98org-babel-load-file=E2=80=99 call.

2. Ne= w Org version is loaded manually by setting =E2=80=98load-path=E2=80=99, bu= t some
=C2=A0 =C2=A0other package depending on Org is loaded before the = =E2=80=98load-path=E2=80=99 is
=C2=A0 =C2=A0configured.
=C2=A0 =C2=A0= This "other package" is triggering built-in Org version, again=C2=A0 =C2=A0causing the version mismatch.

=C2=A0 =C2=A0It is recom= mended to set =E2=80=98load-path=E2=80=99 as early in the config as
=C2= =A0 =C2=A0possible.

3. New Org version is loaded using straight.el p= ackage manager and
=C2=A0 =C2=A0other package depending on Org is loaded= before straight triggers
=C2=A0 =C2=A0loading of the newer Org version.=

=C2=A0 =C2=A0It is recommended to put

=C2=A0 =C2=A0 (straigh= t-use-package 'org)

=C2=A0 =C2=A0early in the config.=C2=A0 Idea= lly, right after the straight.el
=C2=A0 =C2=A0bootstrap.=C2=A0 Moving = =E2=80=98use-package=E2=80=99 :straight declaration may not be
=C2=A0 = =C2=A0sufficient if the corresponding =E2=80=98use-package=E2=80=99 stateme= nt is
=C2=A0 =C2=A0deferring the loading.

4. A new Org version is= synchronized with Emacs git repository and
=C2=A0 =C2=A0stale .elc file= s are still left from the previous build.

=C2=A0 =C2=A0It is recomme= nded to remove .elc files from lisp/org directory and
=C2=A0 =C2=A0re-co= mpile.
=E2=9B=94 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 a= nd more recent Org
=C2=A0 =C2=A0version is loaded inside the file loaded= by =E2=80=98org-babel-load-file=E2=80=99.
=C2=A0 =C2=A0=E2=80=98org-bab= el-load-file=E2=80=99 triggers the built-in Org version clashing
=C2=A0 = =C2=A0the newer Org version attempt to be loaded later.

=C2=A0 =C2= =A0It is recommended to move the Org loading code before the
=C2=A0 =C2= =A0=E2=80=98org-babel-load-file=E2=80=99 call.

2. New Org version is= loaded manually by setting =E2=80=98load-path=E2=80=99, but some
=C2=A0= =C2=A0other package depending on Org is loaded before the =E2=80=98load-pa= th=E2=80=99 is
=C2=A0 =C2=A0configured.
=C2=A0 =C2=A0This "other= package" is triggering built-in Org version, again
=C2=A0 =C2=A0ca= using the version mismatch.

=C2=A0 =C2=A0It is recommended to set = =E2=80=98load-path=E2=80=99 as early in the config as
=C2=A0 =C2=A0possi= ble.

3. New Org version is loaded using straight.el package manager = and
=C2=A0 =C2=A0other package depending on Org is loaded before straigh= t triggers
=C2=A0 =C2=A0loading of the newer Org version.

=C2=A0 = =C2=A0It is recommended to put

=C2=A0 =C2=A0 (straight-use-package &= #39;org)

=C2=A0 =C2=A0early in the config.=C2=A0 Ideally, right afte= r the straight.el
=C2=A0 =C2=A0bootstrap.=C2=A0 Moving =E2=80=98use-pack= age=E2=80=99 :straight declaration may not be
=C2=A0 =C2=A0sufficient if= the corresponding =E2=80=98use-package=E2=80=99 statement is
=C2=A0 =C2= =A0deferring the loading.

4. A new Org version is synchronized with = Emacs git repository and
=C2=A0 =C2=A0stale .elc files are still left fr= om the previous build.

=C2=A0 =C2=A0It is recommended to remove .elc= files from lisp/org directory and
=C2=A0 =C2=A0re-compile.
=E2=9B=94= Warning (emacs): Org version mismatch.
This warning usually appears whe= n a built-in Org version is loaded
prior to the more recent Org version.=

Version mismatch is commonly encountered in the following situation= s:

1. Emacs is loaded using literate Org config and more recent Org<= br>=C2=A0 =C2=A0version is loaded inside the file loaded by =E2=80=98org-ba= bel-load-file=E2=80=99.
=C2=A0 =C2=A0=E2=80=98org-babel-load-file=E2=80= =99 triggers the built-in Org version clashing
=C2=A0 =C2=A0the newer Or= g version attempt to be loaded later.

=C2=A0 =C2=A0It is recommended= to move the Org loading code before the
=C2=A0 =C2=A0=E2=80=98org-babel= -load-file=E2=80=99 call.

2. New Org version is loaded manually by s= etting =E2=80=98load-path=E2=80=99, but some
=C2=A0 =C2=A0other package = depending on Org is loaded before the =E2=80=98load-path=E2=80=99 is
=C2= =A0 =C2=A0configured.
=C2=A0 =C2=A0This "other package" is tri= ggering built-in Org version, again
=C2=A0 =C2=A0causing the version mis= match.

=C2=A0 =C2=A0It is recommended to set =E2=80=98load-path=E2= =80=99 as early in the config as
=C2=A0 =C2=A0possible.

3. New Or= g version is loaded using straight.el package manager and
=C2=A0 =C2=A0o= ther package depending on Org is loaded before straight triggers
=C2=A0 = =C2=A0loading of the newer Org version.

=C2=A0 =C2=A0It is recommend= ed to put

=C2=A0 =C2=A0 (straight-use-package 'org)

=C2= =A0 =C2=A0early in the config.=C2=A0 Ideally, right after the straight.el=C2=A0 =C2=A0bootstrap.=C2=A0 Moving =E2=80=98use-package=E2=80=99 :strai= ght declaration may not be
=C2=A0 =C2=A0sufficient if the corresponding = =E2=80=98use-package=E2=80=99 statement is
=C2=A0 =C2=A0deferring the lo= ading.

4. A new Org version is synchronized with Emacs git repositor= y and
=C2=A0 =C2=A0stale .elc files are still left from the previous bui= ld.

=C2=A0 =C2=A0It is recommended to remove .elc files from lisp/or= g directory and
=C2=A0 =C2=A0re-compile.
=E2=9B=94 Warning (emacs): O= rg version mismatch.
This warning usually appears when a built-in Org ve= rsion is loaded
prior to the more recent Org version.

Version mis= match is commonly encountered in the following situations:

1. Emacs = is loaded using literate Org config and more recent Org
=C2=A0 =C2=A0ver= sion is loaded inside the file loaded by =E2=80=98org-babel-load-file=E2=80= =99.
=C2=A0 =C2=A0=E2=80=98org-babel-load-file=E2=80=99 triggers the bui= lt-in Org version clashing
=C2=A0 =C2=A0the newer Org version attempt to= be loaded later.

=C2=A0 =C2=A0It is recommended to move the Org loa= ding code before the
=C2=A0 =C2=A0=E2=80=98org-babel-load-file=E2=80=99 = call.

2. New Org version is loaded manually by setting =E2=80=98load= -path=E2=80=99, but some
=C2=A0 =C2=A0other package depending on Org is = loaded before the =E2=80=98load-path=E2=80=99 is
=C2=A0 =C2=A0configured= .
=C2=A0 =C2=A0This "other package" is triggering built-in Org= version, again
=C2=A0 =C2=A0causing the version mismatch.

=C2=A0= =C2=A0It is recommended to set =E2=80=98load-path=E2=80=99 as early in the= config as
=C2=A0 =C2=A0possible.

3. New Org version is loaded us= ing straight.el package manager and
=C2=A0 =C2=A0other package depending= on Org is loaded before straight triggers
=C2=A0 =C2=A0loading of the n= ewer Org version.

=C2=A0 =C2=A0It is recommended to put

=C2= =A0 =C2=A0 (straight-use-package 'org)

=C2=A0 =C2=A0early in the= config.=C2=A0 Ideally, right after the straight.el
=C2=A0 =C2=A0bootstr= ap.=C2=A0 Moving =E2=80=98use-package=E2=80=99 :straight declaration may no= t be
=C2=A0 =C2=A0sufficient if the corresponding =E2=80=98use-package= =E2=80=99 statement is
=C2=A0 =C2=A0deferring the loading.

4. A n= ew Org version is synchronized with Emacs git repository and
=C2=A0 =C2= =A0stale .elc files are still left from the previous build.

=C2=A0 = =C2=A0It is recommended to remove .elc files from lisp/org directory and=C2=A0 =C2=A0re-compile.
=E2=9B=94 Warning (emacs): Org version mismatc= h.
This warning usually appears when a built-in Org version is loadedprior to the more recent Org version.

Version mismatch is commonly = encountered in the following situations:

1. Emacs is loaded using li= terate Org config and more recent Org
=C2=A0 =C2=A0version is loaded ins= ide the file loaded by =E2=80=98org-babel-load-file=E2=80=99.
=C2=A0 =C2= =A0=E2=80=98org-babel-load-file=E2=80=99 triggers the built-in Org version = clashing
=C2=A0 =C2=A0the newer Org version attempt to be loaded later.<= br>
=C2=A0 =C2=A0It is recommended to move the Org loading code before t= he
=C2=A0 =C2=A0=E2=80=98org-babel-load-file=E2=80=99 call.

2. Ne= w Org version is loaded manually by setting =E2=80=98load-path=E2=80=99, bu= t some
=C2=A0 =C2=A0other package depending on Org is loaded before the = =E2=80=98load-path=E2=80=99 is
=C2=A0 =C2=A0configured.
=C2=A0 =C2=A0= This "other package" is triggering built-in Org version, again=C2=A0 =C2=A0causing the version mismatch.

=C2=A0 =C2=A0It is recom= mended to set =E2=80=98load-path=E2=80=99 as early in the config as
=C2= =A0 =C2=A0possible.

3. New Org version is loaded using straight.el p= ackage manager and
=C2=A0 =C2=A0other package depending on Org is loaded= before straight triggers
=C2=A0 =C2=A0loading of the newer Org version.=

=C2=A0 =C2=A0It is recommended to put

=C2=A0 =C2=A0 (straigh= t-use-package 'org)

=C2=A0 =C2=A0early in the config.=C2=A0 Idea= lly, right after the straight.el
=C2=A0 =C2=A0bootstrap.=C2=A0 Moving = =E2=80=98use-package=E2=80=99 :straight declaration may not be
=C2=A0 = =C2=A0sufficient if the corresponding =E2=80=98use-package=E2=80=99 stateme= nt is
=C2=A0 =C2=A0deferring the loading.

4. A new Org version is= synchronized with Emacs git repository and
=C2=A0 =C2=A0stale .elc file= s are still left from the previous build.

=C2=A0 =C2=A0It is recomme= nded to remove .elc files from lisp/org directory and
=C2=A0 =C2=A0re-co= mpile.
=E2=9B=94 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 a= nd more recent Org
=C2=A0 =C2=A0version is loaded inside the file loaded= by =E2=80=98org-babel-load-file=E2=80=99.
=C2=A0 =C2=A0=E2=80=98org-bab= el-load-file=E2=80=99 triggers the built-in Org version clashing
=C2=A0 = =C2=A0the newer Org version attempt to be loaded later.

=C2=A0 =C2= =A0It is recommended to move the Org loading code before the
=C2=A0 =C2= =A0=E2=80=98org-babel-load-file=E2=80=99 call.

2. New Org version is= loaded manually by setting =E2=80=98load-path=E2=80=99, but some
=C2=A0= =C2=A0other package depending on Org is loaded before the =E2=80=98load-pa= th=E2=80=99 is
=C2=A0 =C2=A0configured.
=C2=A0 =C2=A0This "other= package" is triggering built-in Org version, again
=C2=A0 =C2=A0ca= using the version mismatch.

=C2=A0 =C2=A0It is recommended to set = =E2=80=98load-path=E2=80=99 as early in the config as
=C2=A0 =C2=A0possi= ble.

3. New Org version is loaded using straight.el package manager = and
=C2=A0 =C2=A0other package depending on Org is loaded before straigh= t triggers
=C2=A0 =C2=A0loading of the newer Org version.

=C2=A0 = =C2=A0It is recommended to put

=C2=A0 =C2=A0 (straight-use-package &= #39;org)

=C2=A0 =C2=A0early in the config.=C2=A0 Ideally, right afte= r the straight.el
=C2=A0 =C2=A0bootstrap.=C2=A0 Moving =E2=80=98use-pack= age=E2=80=99 :straight declaration may not be
=C2=A0 =C2=A0sufficient if= the corresponding =E2=80=98use-package=E2=80=99 statement is
=C2=A0 =C2= =A0deferring the loading.

4. A new Org version is synchronized with = Emacs git repository and
=C2=A0 =C2=A0stale .elc files are still left fr= om the previous build.

=C2=A0 =C2=A0It is recommended to remove .elc= files from lisp/org directory and
=C2=A0 =C2=A0re-compile.
=E2=9B=94= Warning (emacs): Org version mismatch.
This warning usually appears whe= n a built-in Org version is loaded
prior to the more recent Org version.=

Version mismatch is commonly encountered in the following situation= s:

1. Emacs is loaded using literate Org config and more recent Org<= br>=C2=A0 =C2=A0version is loaded inside the file loaded by =E2=80=98org-ba= bel-load-file=E2=80=99.
=C2=A0 =C2=A0=E2=80=98org-babel-load-file=E2=80= =99 triggers the built-in Org version clashing
=C2=A0 =C2=A0the newer Or= g version attempt to be loaded later.

=C2=A0 =C2=A0It is recommended= to move the Org loading code before the
=C2=A0 =C2=A0=E2=80=98org-babel= -load-file=E2=80=99 call.

2. New Org version is loaded manually by s= etting =E2=80=98load-path=E2=80=99, but some
=C2=A0 =C2=A0other package = depending on Org is loaded before the =E2=80=98load-path=E2=80=99 is
=C2= =A0 =C2=A0configured.
=C2=A0 =C2=A0This "other package" is tri= ggering built-in Org version, again
=C2=A0 =C2=A0causing the version mis= match.

=C2=A0 =C2=A0It is recommended to set =E2=80=98load-path=E2= =80=99 as early in the config as
=C2=A0 =C2=A0possible.

3. New Or= g version is loaded using straight.el package manager and
=C2=A0 =C2=A0o= ther package depending on Org is loaded before straight triggers
=C2=A0 = =C2=A0loading of the newer Org version.

=C2=A0 =C2=A0It is recommend= ed to put

=C2=A0 =C2=A0 (straight-use-package 'org)

=C2= =A0 =C2=A0early in the config.=C2=A0 Ideally, right after the straight.el=C2=A0 =C2=A0bootstrap.=C2=A0 Moving =E2=80=98use-package=E2=80=99 :strai= ght declaration may not be
=C2=A0 =C2=A0sufficient if the corresponding = =E2=80=98use-package=E2=80=99 statement is
=C2=A0 =C2=A0deferring the lo= ading.

4. A new Org version is synchronized with Emacs git repositor= y and
=C2=A0 =C2=A0stale .elc files are still left from the previous bui= ld.

=C2=A0 =C2=A0It is recommended to remove .elc files from lisp/or= g directory and
=C2=A0 =C2=A0re-compile.
=E2=9B=94 Warning (emacs): O= rg version mismatch.
This warning usually appears when a built-in Org ve= rsion is loaded
prior to the more recent Org version.

Version mis= match is commonly encountered in the following situations:

1. Emacs = is loaded using literate Org config and more recent Org
=C2=A0 =C2=A0ver= sion is loaded inside the file loaded by =E2=80=98org-babel-load-file=E2=80= =99.
=C2=A0 =C2=A0=E2=80=98org-babel-load-file=E2=80=99 triggers the bui= lt-in Org version clashing
=C2=A0 =C2=A0the newer Org version attempt to= be loaded later.

=C2=A0 =C2=A0It is recommended to move the Org loa= ding code before the
=C2=A0 =C2=A0=E2=80=98org-babel-load-file=E2=80=99 = call.

2. New Org version is loaded manually by setting =E2=80=98load= -path=E2=80=99, but some
=C2=A0 =C2=A0other package depending on Org is = loaded before the =E2=80=98load-path=E2=80=99 is
=C2=A0 =C2=A0configured= .
=C2=A0 =C2=A0This "other package" is triggering built-in Org= version, again
=C2=A0 =C2=A0causing the version mismatch.

=C2=A0= =C2=A0It is recommended to set =E2=80=98load-path=E2=80=99 as early in the= config as
=C2=A0 =C2=A0possible.

3. New Org version is loaded us= ing straight.el package manager and
=C2=A0 =C2=A0other package depending= on Org is loaded before straight triggers
=C2=A0 =C2=A0loading of the n= ewer Org version.

=C2=A0 =C2=A0It is recommended to put

=C2= =A0 =C2=A0 (straight-use-package 'org)

=C2=A0 =C2=A0early in the= config.=C2=A0 Ideally, right after the straight.el
=C2=A0 =C2=A0bootstr= ap.=C2=A0 Moving =E2=80=98use-package=E2=80=99 :straight declaration may no= t be
=C2=A0 =C2=A0sufficient if the corresponding =E2=80=98use-package= =E2=80=99 statement is
=C2=A0 =C2=A0deferring the loading.

4. A n= ew Org version is synchronized with Emacs git repository and
=C2=A0 =C2= =A0stale .elc files are still left from the previous build.

=C2=A0 = =C2=A0It is recommended to remove .elc files from lisp/org directory and=C2=A0 =C2=A0re-compile.
=E2=9B=94 Warning (emacs): Org version mismatc= h.
This warning usually appears when a built-in Org version is loadedprior to the more recent Org version.

Version mismatch is commonly = encountered in the following situations:

1. Emacs is loaded using li= terate Org config and more recent Org
=C2=A0 =C2=A0version is loaded ins= ide the file loaded by =E2=80=98org-babel-load-file=E2=80=99.
=C2=A0 =C2= =A0=E2=80=98org-babel-load-file=E2=80=99 triggers the built-in Org version = clashing
=C2=A0 =C2=A0the newer Org version attempt to be loaded later.<= br>
=C2=A0 =C2=A0It is recommended to move the Org loading code before t= he
=C2=A0 =C2=A0=E2=80=98org-babel-load-file=E2=80=99 call.

2. Ne= w Org version is loaded manually by setting =E2=80=98load-path=E2=80=99, bu= t some
=C2=A0 =C2=A0other package depending on Org is loaded before the = =E2=80=98load-path=E2=80=99 is
=C2=A0 =C2=A0configured.
=C2=A0 =C2=A0= This "other package" is triggering built-in Org version, again=C2=A0 =C2=A0causing the version mismatch.

=C2=A0 =C2=A0It is recom= mended to set =E2=80=98load-path=E2=80=99 as early in the config as
=C2= =A0 =C2=A0possible.

3. New Org version is loaded using straight.el p= ackage manager and
=C2=A0 =C2=A0other package depending on Org is loaded= before straight triggers
=C2=A0 =C2=A0loading of the newer Org version.=

=C2=A0 =C2=A0It is recommended to put

=C2=A0 =C2=A0 (straigh= t-use-package 'org)

=C2=A0 =C2=A0early in the config.=C2=A0 Idea= lly, right after the straight.el
=C2=A0 =C2=A0bootstrap.=C2=A0 Moving = =E2=80=98use-package=E2=80=99 :straight declaration may not be
=C2=A0 = =C2=A0sufficient if the corresponding =E2=80=98use-package=E2=80=99 stateme= nt is
=C2=A0 =C2=A0deferring the loading.

4. A new Org version is= synchronized with Emacs git repository and
=C2=A0 =C2=A0stale .elc file= s are still left from the previous build.

=C2=A0 =C2=A0It is recomme= nded to remove .elc files from lisp/org directory and
=C2=A0 =C2=A0re-co= mpile.
=E2=9B=94 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 a= nd more recent Org
=C2=A0 =C2=A0version is loaded inside the file loaded= by =E2=80=98org-babel-load-file=E2=80=99.
=C2=A0 =C2=A0=E2=80=98org-bab= el-load-file=E2=80=99 triggers the built-in Org version clashing
=C2=A0 = =C2=A0the newer Org version attempt to be loaded later.

=C2=A0 =C2= =A0It is recommended to move the Org loading code before the
=C2=A0 =C2= =A0=E2=80=98org-babel-load-file=E2=80=99 call.

2. New Org version is= loaded manually by setting =E2=80=98load-path=E2=80=99, but some
=C2=A0= =C2=A0other package depending on Org is loaded before the =E2=80=98load-pa= th=E2=80=99 is
=C2=A0 =C2=A0configured.
=C2=A0 =C2=A0This "other= package" is triggering built-in Org version, again
=C2=A0 =C2=A0ca= using the version mismatch.

=C2=A0 =C2=A0It is recommended to set = =E2=80=98load-path=E2=80=99 as early in the config as
=C2=A0 =C2=A0possi= ble.

3. New Org version is loaded using straight.el package manager = and
=C2=A0 =C2=A0other package depending on Org is loaded before straigh= t triggers
=C2=A0 =C2=A0loading of the newer Org version.

=C2=A0 = =C2=A0It is recommended to put

=C2=A0 =C2=A0 (straight-use-package &= #39;org)

=C2=A0 =C2=A0early in the config.=C2=A0 Ideally, right afte= r the straight.el
=C2=A0 =C2=A0bootstrap.=C2=A0 Moving =E2=80=98use-pack= age=E2=80=99 :straight declaration may not be
=C2=A0 =C2=A0sufficient if= the corresponding =E2=80=98use-package=E2=80=99 statement is
=C2=A0 =C2= =A0deferring the loading.

4. A new Org version is synchronized with = Emacs git repository and
=C2=A0 =C2=A0stale .elc files are still left fr= om the previous build.

=C2=A0 =C2=A0It is recommended to remove .elc= files from lisp/org directory and
=C2=A0 =C2=A0re-compile.
=E2=9B=94= Warning (emacs): Org version mismatch.
This warning usually appears whe= n a built-in Org version is loaded
prior to the more recent Org version.=

Version mismatch is commonly encountered in the following situation= s:

1. Emacs is loaded using literate Org config and more recent Org<= br>=C2=A0 =C2=A0version is loaded inside the file loaded by =E2=80=98org-ba= bel-load-file=E2=80=99.
=C2=A0 =C2=A0=E2=80=98org-babel-load-file=E2=80= =99 triggers the built-in Org version clashing
=C2=A0 =C2=A0the newer Or= g version attempt to be loaded later.

=C2=A0 =C2=A0It is recommended= to move the Org loading code before the
=C2=A0 =C2=A0=E2=80=98org-babel= -load-file=E2=80=99 call.

2. New Org version is loaded manually by s= etting =E2=80=98load-path=E2=80=99, but some
=C2=A0 =C2=A0other package = depending on Org is loaded before the =E2=80=98load-path=E2=80=99 is
=C2= =A0 =C2=A0configured.
=C2=A0 =C2=A0This "other package" is tri= ggering built-in Org version, again
=C2=A0 =C2=A0causing the version mis= match.

=C2=A0 =C2=A0It is recommended to set =E2=80=98load-path=E2= =80=99 as early in the config as
=C2=A0 =C2=A0possible.

3. New Or= g version is loaded using straight.el package manager and
=C2=A0 =C2=A0o= ther package depending on Org is loaded before straight triggers
=C2=A0 = =C2=A0loading of the newer Org version.

=C2=A0 =C2=A0It is recommend= ed to put

=C2=A0 =C2=A0 (straight-use-package 'org)

=C2= =A0 =C2=A0early in the config.=C2=A0 Ideally, right after the straight.el=C2=A0 =C2=A0bootstrap.=C2=A0 Moving =E2=80=98use-package=E2=80=99 :strai= ght declaration may not be
=C2=A0 =C2=A0sufficient if the corresponding = =E2=80=98use-package=E2=80=99 statement is
=C2=A0 =C2=A0deferring the lo= ading.

4. A new Org version is synchronized with Emacs git repositor= y and
=C2=A0 =C2=A0stale .elc files are still left from the previous bui= ld.

=C2=A0 =C2=A0It is recommended to remove .elc files from lisp/or= g directory and
=C2=A0 =C2=A0re-compile.
=E2=9B=94 Warning (emacs): O= rg version mismatch.
This warning usually appears when a built-in Org ve= rsion is loaded
prior to the more recent Org version.

Version mis= match is commonly encountered in the following situations:

1. Emacs = is loaded using literate Org config and more recent Org
=C2=A0 =C2=A0ver= sion is loaded inside the file loaded by =E2=80=98org-babel-load-file=E2=80= =99.
=C2=A0 =C2=A0=E2=80=98org-babel-load-file=E2=80=99 triggers the bui= lt-in Org version clashing
=C2=A0 =C2=A0the newer Org version attempt to= be loaded later.

=C2=A0 =C2=A0It is recommended to move the Org loa= ding code before the
=C2=A0 =C2=A0=E2=80=98org-babel-load-file=E2=80=99 = call.

2. New Org version is loaded manually by setting =E2=80=98load= -path=E2=80=99, but some
=C2=A0 =C2=A0other package depending on Org is = loaded before the =E2=80=98load-path=E2=80=99 is
=C2=A0 =C2=A0configured= .
=C2=A0 =C2=A0This "other package" is triggering built-in Org= version, again
=C2=A0 =C2=A0causing the version mismatch.

=C2=A0= =C2=A0It is recommended to set =E2=80=98load-path=E2=80=99 as early in the= config as
=C2=A0 =C2=A0possible.

3. New Org version is loaded us= ing straight.el package manager and
=C2=A0 =C2=A0other package depending= on Org is loaded before straight triggers
=C2=A0 =C2=A0loading of the n= ewer Org version.

=C2=A0 =C2=A0It is recommended to put

=C2= =A0 =C2=A0 (straight-use-package 'org)

=C2=A0 =C2=A0early in the= config.=C2=A0 Ideally, right after the straight.el
=C2=A0 =C2=A0bootstr= ap.=C2=A0 Moving =E2=80=98use-package=E2=80=99 :straight declaration may no= t be
=C2=A0 =C2=A0sufficient if the corresponding =E2=80=98use-package= =E2=80=99 statement is
=C2=A0 =C2=A0deferring the loading.

4. A n= ew Org version is synchronized with Emacs git repository and
=C2=A0 =C2= =A0stale .elc files are still left from the previous build.

=C2=A0 = =C2=A0It is recommended to remove .elc files from lisp/org directory and=C2=A0 =C2=A0re-compile.
=E2=9B=94 Warning (emacs): Org version mismatc= h.
This warning usually appears when a built-in Org version is loadedprior to the more recent Org version.

Version mismatch is commonly = encountered in the following situations:

1. Emacs is loaded using li= terate Org config and more recent Org
=C2=A0 =C2=A0version is loaded ins= ide the file loaded by =E2=80=98org-babel-load-file=E2=80=99.
=C2=A0 =C2= =A0=E2=80=98org-babel-load-file=E2=80=99 triggers the built-in Org version = clashing
=C2=A0 =C2=A0the newer Org version attempt to be loaded later.<= br>
=C2=A0 =C2=A0It is recommended to move the Org loading code before t= he
=C2=A0 =C2=A0=E2=80=98org-babel-load-file=E2=80=99 call.

2. Ne= w Org version is loaded manually by setting =E2=80=98load-path=E2=80=99, bu= t some
=C2=A0 =C2=A0other package depending on Org is loaded before the = =E2=80=98load-path=E2=80=99 is
=C2=A0 =C2=A0configured.
=C2=A0 =C2=A0= This "other package" is triggering built-in Org version, again=C2=A0 =C2=A0causing the version mismatch.

=C2=A0 =C2=A0It is recom= mended to set =E2=80=98load-path=E2=80=99 as early in the config as
=C2= =A0 =C2=A0possible.

3. New Org version is loaded using straight.el p= ackage manager and
=C2=A0 =C2=A0other package depending on Org is loaded= before straight triggers
=C2=A0 =C2=A0loading of the newer Org version.=

=C2=A0 =C2=A0It is recommended to put

=C2=A0 =C2=A0 (straigh= t-use-package 'org)

=C2=A0 =C2=A0early in the config.=C2=A0 Idea= lly, right after the straight.el
=C2=A0 =C2=A0bootstrap.=C2=A0 Moving = =E2=80=98use-package=E2=80=99 :straight declaration may not be
=C2=A0 = =C2=A0sufficient if the corresponding =E2=80=98use-package=E2=80=99 stateme= nt is
=C2=A0 =C2=A0deferring the loading.

4. A new Org version is= synchronized with Emacs git repository and
=C2=A0 =C2=A0stale .elc file= s are still left from the previous build.

=C2=A0 =C2=A0It is recomme= nded to remove .elc files from lisp/org directory and
=C2=A0 =C2=A0re-co= mpile.


--0000000000003ed033061b0ef00e--