From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id GBViKppfLmN7CwEAbAwnHQ (envelope-from ) for ; Sat, 24 Sep 2022 03:38:34 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id MJiQKZpfLmMp1QAAG6o9tA (envelope-from ) for ; Sat, 24 Sep 2022 03:38:34 +0200 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 23D6C3F9F2 for ; Sat, 24 Sep 2022 03:38:34 +0200 (CEST) Received: from localhost ([::1]:33836 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1obu7k-00063I-J2 for larch@yhetil.org; Fri, 23 Sep 2022 21:38:32 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:49914) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1obu76-00061o-RV for emacs-orgmode@gnu.org; Fri, 23 Sep 2022 21:37:56 -0400 Received: from mail-pl1-x62d.google.com ([2607:f8b0:4864:20::62d]:33377) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1obu74-0007gE-Ra for emacs-orgmode@gnu.org; Fri, 23 Sep 2022 21:37:52 -0400 Received: by mail-pl1-x62d.google.com with SMTP id iw17so1665780plb.0 for ; Fri, 23 Sep 2022 18:37:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:mime-version:message-id:in-reply-to:date :subject:to:from:user-agent:references:from:to:cc:subject:date; bh=SPa1Yp20K/KAedz2N3g0XD7VJzcvt6NEl6jZZ6eIGQg=; b=JI7VGGSeOshQLEOWWCmCkifYRFEP8CQ0k4XCaBkF8bEWLqwG1uWpcjOauMHU+kawxX +Okf5UD+6Eh2C9Kf3koDJ/2+fhXyfR8/OO53l4XpYQ2wZXTJZWRKXt9bPSL/iZWrggZJ wuN/HGMUW1fmj3LgtY5E5I/f5WLdVffQ2kDpD7GWfpgyOE1t2DKLeAFTg3umgV830PAJ f0UPfcmlybal8o/0WNFui5kKMzW9COD4d2yxxxvWO920mfZGOtwxhSL+03SCIEQ/BNR6 omnKgFcovoyuGgJSyFk2Gf8mtjzpI/HE1yYDS8A35kgwBDPIYLGFaHLU+djyLEbNJmBs arrQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:message-id:in-reply-to:date :subject:to:from:user-agent:references:x-gm-message-state:from:to:cc :subject:date; bh=SPa1Yp20K/KAedz2N3g0XD7VJzcvt6NEl6jZZ6eIGQg=; b=3dy0Y1RvJ6zM8m8knVrDjEQRw+LQG9p9GdsJvk9jcaDTk4TRFq1KE3N/7VDRXNpRPQ 2KZhH+0utsAlc7xa+LT4Gu5wVh5w6+NR6sBYtsYVsC4/S1kaf9MYF44BmlCizgVI8EgO fu1kYQ9eZ86LbiqUpzEUZ88QN0CqeV1BNmkcTP1Bu5Mo/yweu55NUVj0xmA0jFHjWIop 9Y4kghBMzWVbA8xLoN/7UwFZbfCj7U7hbn/e5iYqF4RMx3tzMoCGbmfcNzweBoP/KCfJ E32WQqzvEaDW94FV2i9jaaJsdqxa0tT1Eg1flEzKwHVtJ8ERm3ap9HOxnyO2q8TTA6M7 Op+A== X-Gm-Message-State: ACrzQf1nGENgXicbQrnn6GXDGnptYeHPolUngDo6KTEDOIwChKkcVHdG 6iTheeF5p+lsLph1NpKCql+UPh9cP1k= X-Google-Smtp-Source: AMsMyM5aziF6M1MY45ryNKbzpcGV+Em32iDQpHgMl+GYNSsut6BTuTaMLcvA7yXATRGZsfizLFdz7A== X-Received: by 2002:a17:902:ce8d:b0:178:47e8:6ed8 with SMTP id f13-20020a170902ce8d00b0017847e86ed8mr11558411plg.12.1663983468609; Fri, 23 Sep 2022 18:37:48 -0700 (PDT) Received: from dingbat (2001-44b8-31f2-bb00-842a-7361-87c7-2662.static.ipv6.internode.on.net. [2001:44b8:31f2:bb00:842a:7361:87c7:2662]) by smtp.gmail.com with ESMTPSA id i64-20020a62c143000000b0053617cbe2d2sm6974237pfg.168.2022.09.23.18.37.45 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 23 Sep 2022 18:37:47 -0700 (PDT) References: <87illec6qa.fsf@yandex.com> User-agent: mu4e 1.9.0; emacs 29.0.50 From: Tim Cross To: emacs-orgmode@gnu.org Subject: Re: refresh not working for org-mode from git Date: Sat, 24 Sep 2022 11:12:18 +1000 In-reply-to: <87illec6qa.fsf@yandex.com> Message-ID: <86sfkhmu1l.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=2607:f8b0:4864:20::62d; envelope-from=theophilusx@gmail.com; helo=mail-pl1-x62d.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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 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" X-Migadu-Flow: FLOW_IN X-Migadu-To: larch@yhetil.org X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1663983514; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=SPa1Yp20K/KAedz2N3g0XD7VJzcvt6NEl6jZZ6eIGQg=; b=qNl+Q6nrZ3rvXxZvJaH3O5KKd3Ij4y02RoCpQxOY8sc+zDGxUPmTfVXt94ISbiWiEEX7GY /p8WY0dCXTQ1AvHacMaDA2fla2rDt51aoot7Z4rrifphGTEQmUdxmV297nW511KFNpme4/ 885zil2r/Ii3SgJmup2LSjEMEPYaxRVWLn+JhsabaPPCn2J+vVwoz+kU3PjcIABEDYBmNn obCtDDCo8QOd17mYrqjievomwABo/bH4ceycXW8VYoeYxTh3TeWZjuZpd+rSdbYSpZ70T1 NI55N3wt9z7HHHin8629dyihsWRzy4IdnyjmNxbA/oRiY91zUnbti8Xvg0B/Wg== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1663983514; a=rsa-sha256; cv=none; b=inl44D8kQhtOQgWj2Ea58GuG8RWydRkffZnah63PjsN8b6ul4tkrnGiHRt4mOK1GrCGkQy 1xOXN/vKsjk1QUioq+HnjugHAdonO08VSkBXl4P3BqodSkvA10N4HRKs3FvgknnFyTo2q7 cdQUb9UH9eG2YIcs3M1j10j0+G+oR56hsimKGna5FQ4Mo6j5/1X2x1w9yosOuKVIpT+9q4 dAdygBkvJ7XhSr920uTWr1Lk+3xV4iOZkYTP7MZ4ZuCY2L9dy8ie251ZbHsIfgs8mV277m pjqc3NPMtsDHMreAqugpeQ+XYyDGjccwnCqsFe23PXZXyBYvnILnRHfGGEkPow== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=JI7VGGSe; 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" X-Migadu-Spam-Score: -3.85 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=JI7VGGSe; 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" X-Migadu-Queue-Id: 23D6C3F9F2 X-Spam-Score: -3.85 X-Migadu-Scanner: scn0.migadu.com X-TUID: lj23rs7U2Zo7 Colin Baxter writes: > Recently, if I use C-c C-x ! to refresh org-mode after a git pull, I get = an > error. I then have to close down emacs and launch again. This rather > defeats the object of C-c C-x !. This appears to have happened only recen= tly > > The Backtrace is > > --8<---------------cut here---------------start------------->8--- > Debugger entered--Lisp error: (error "Org version mismatch. Make sure th= at correct `loa...") > (signal error ("Org version mismatch. Make sure that correct `loa...")) > (error "Org version mismatch. Make sure that correct `loa...") > (byte-code "\300\301!\210\302 \303\232\204\23\0\304\305!\210\306\307!\2= 10\300\301!\210\300\310!\210\300\311!\210\300\312!\210\300\313!\210\300\314= !\210\300\315!\210\300\316!..." [require org-macs org-git-version "release_= 9.5.5-821-g9bd8a9" warn "Org version mismatch. Make sure that correct `loa= ..." error "Org version mismatch. Make sure that correct `loa..." org-comp= at org-keys ob-eval ob-core ob-comint ob-exp ob-table ob-lob ob-ref ob-tang= le provide ob] 2) > (load "/home/redknight/git/org-mode/lisp/ob" noerror nil nil mustsuffix) > (#f(compiled-function (f) #) "ob") > (mapcar #f(compiled-function (f) #) ("ob" "ob-C" "= ob-R" "ob-awk" "ob-calc" "ob-comint" "ob-core" "ob-ditaa" "ob-dot" "ob-emac= s-lisp" "ob-eshell" "ob-eval" "ob-exp" "ob-fortran" "ob-gnuplot" "ob-latex"= "ob-lisp" "ob-lob" "ob-org" "ob-perl" "ob-plantuml" "ob-python" "ob-ref" "= ob-ruby" "ob-shell" "ob-sql" "ob-sqlite" "ob-table" "ob-tangle" "obarray" "= oc" "oc-basic" "oclosure" "ol" "ol-bbdb" "ol-bibtex" "ol-docview" "ol-eshel= l" "ol-eww" "ol-gnus" "ol-info" "ol-irc" "ol-mhe" "ol-rmail" "ol-w3m" "org-= agenda" "org-capture" "org-collector" "org-compat" "org-crypt" ...)) > (org-reload nil) > (funcall-interactively org-reload nil) > (call-interactively org-reload) > (popup-menu (keymap "Global Menu" ... ... ... ... ... ... ... "menu-bar= " keymap "Org Mode Menu" ... keymap ...) f10) > (x-menu-bar-open nil) > (menu-bar-open nil 1) > (funcall-interactively menu-bar-open nil 1) > (call-interactively menu-bar-open nil nil) > (command-execute menu-bar-open) > --8<---------------cut here---------------end--------------->8--- > > > I also receive a warning, copied below. I do not use 'packages' but use > org-mode from a git repository and have done so with no previous issues. > > --8<---------------cut here---------------start------------->8--- > =E2=9B=94 Warning (emacs): Org version mismatch. Make sure that correct = `load-path' is set early in init.el > This warning usually appears when a built-in Org version is loaded > prior to the more recent Org version. > > Version mismatch is commonly encountered in the following situations: > 1. Emacs is loaded using literate Org config and more recent Org > version is loaded inside the file loaded by `org-babel-load-file'. > `org-babel-load-file' triggers the built-in Org version clashing > the newer Org version attempted to be loaded later. > > It is recommended to move the Org loading code before the > `org-babel-load-file' call. > > 2. New Org version is loaded manually by setting `load-path', but some > other package depending on Org is loaded before the `load-path' is > configured. > This "other package" is triggering built-in Org version, again > causing the version mismatch. > > It is recommended to set `load-path' as early in the config as > possible. > > 3. New Org version is loaded using straight.el package manager and > other package depending on Org is loaded before straight triggers > loading of the newer Org version. > > It is recommended to put > (straight-use-package 'org) > early in the config. Ideally, right after the straight.el > bootstrap. Moving `use-package' :straight declaration may not be > sufficient if the corresponding `use-package' statement is > deferring the loading. > --8<---------------cut here---------------end--------------->8--- > I wasn't aware that command even existed. However, I suspect it will cause issues in your use case. I'm not sure it is a good command to actually have given the complexities associated with getting a clean org build. In many cases, you may not run into issues - especially if you do a git pull frequently. However, I can see various scenarios which will lead to inconsistent builds. I suspect the error you are seeing is the result of recent work to try and identify builds which are likely to result in an inconsistent 'mixed' version build. Detecting such scenarios is difficult and relies on a number of heuristics, one of which is to flag a problem if the loaded version and the target build version don't match.=20=20 A lot would depend on how you build (re-compile) org mode after doing a git pull. If you compile it in a separate Emacs instance, you should have less issues and reloading after the build will likely work. However, if your trying to build org mode within the running Emacs where you have already loaded org mode, I suspect you will run into issues. You have a slight 'chicken and egg' issue and will run into similar issues as the common mixed build problems. One thing which might work would be to ensure you run the reload command with the option to load from uncompiled sources BEFORE you run the build process and then re-run the load command after the build (loading compiled versions this time). I have no idea how things might break given the new native compilation modes in Emacs. I suspect it will cause all sorts of issue with your workflow. Personally, I always update org in a fresh instance of Emacs (before any org functionality is loaded) and I would always restart Emacs after updating a major packages like org mode. I'm not sure why we have the reload command - I suspect it may be a hang over from earlier attempts to work around the mixed build problem. I do suspect that given new native compilation modes and the additional complexity ths can cause, combined with increasing org mode complexity, the notion of being able to pull down a new version, build and reload it within one emacs instance is perhaps flawed or at the very least, is more complex than just forcing a reload of org *.elc files. .=20