From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id IPjhN0OSQ2TRMgAASxT56A (envelope-from ) for ; Sat, 22 Apr 2023 09:52:35 +0200 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id ZIzcN0OSQ2SG3wAA9RJhRA (envelope-from ) for ; Sat, 22 Apr 2023 09:52:35 +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 66F091F726 for ; Sat, 22 Apr 2023 09:52:35 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pq81v-0000AA-S0; Sat, 22 Apr 2023 03:51:35 -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 1pq81t-00009m-Np for emacs-orgmode@gnu.org; Sat, 22 Apr 2023 03:51:33 -0400 Received: from forward500c.mail.yandex.net ([2a02:6b8:c03:500:1:45:d181:d500]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pq81q-0004CY-NB for emacs-orgmode@gnu.org; Sat, 22 Apr 2023 03:51:33 -0400 Received: from mail-nwsmtp-smtp-production-main-69.iva.yp-c.yandex.net (mail-nwsmtp-smtp-production-main-69.iva.yp-c.yandex.net [IPv6:2a02:6b8:c0c:610a:0:640:be20:0]) by forward500c.mail.yandex.net (Yandex) with ESMTP id 2C9535EDDB; Sat, 22 Apr 2023 10:51:25 +0300 (MSK) Received: by mail-nwsmtp-smtp-production-main-69.iva.yp-c.yandex.net (smtp/Yandex) with ESMTPSA id NpaFwB7DY0U0-i72v5dmR; Sat, 22 Apr 2023 10:51:24 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1682149884; bh=U5m8mWlLe0T4KJMtmz6Tyffb/uWgndOykXFh9DBGdzM=; h=Message-ID:References:Date:Reply-To:In-Reply-To:Cc:To:Subject: From; b=PPLFH3k7Kut4xijnj4u28TdciQCKth8AxSKz0otE/gIN/8VBB8xi2UksrDDW81U21 8Ao/eEi2UFHXLodqR2L7ZQDXaRQE5gCwmIPi1E2DVo4D4KYzVjvwC5212Fm2oNRTxv WIHGdVVWjb5yf8iullnDHqJxOnLqougc0arr3Tc4= From: Colin Baxter To: Max Nikulin Cc: emacs-orgmode@gnu.org Subject: Re: Why am I being told to use "straight.el"? References: <87ildpbmgs.fsf@yandex.com> <87edodbc54.fsf@yandex.com> <87h6t9dxav.fsf@yandex.com> X-Face: BHjiJOg/Qmj'BQgsAKL@])L)e62P)C"Y=6T Date: Sat, 22 Apr 2023 08:51:23 +0100 In-Reply-To: (Max Nikulin's message of "Sat, 22 Apr 2023 10:29:12 +0700") Message-ID: <87354swe10.fsf@yandex.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux) Face: iVBORw0KGgoAAAANSUhEUgAAAEkAAAATAgMAAAChCMjeAAAABGdBTUEAALGPC/xhBQAAACBj SFJNAAB6JgAAgIQAAPoAAACA6AAAdTAAAOpgAAA6mAAAF3CculE8AAAACVBMVEX/zAABCWP///8I RHjYAAAAAWJLR0QCZgt8ZAAAAAlwSFlzAAALEwAACxMBAJqcGAAAAAd0SU1FB+UFEAk5BvqS634A AAAbSURBVBjTY2BgCA1hYA0FAxDDgQEERsXoIAYA2F9Eb3cpB+AAAAAldEVYdGRhdGU6Y3JlYXRl ADIwMjEtMDUtMTZUMTA6NTY6MTcrMDE6MDCh/kkpAAAAJXRFWHRkYXRlOm1vZGlmeQAyMDIxLTA1 LTE2VDA5OjU3OjA2KzAxOjAwTyZ6HwAAAABJRU5ErkJggg== MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=2a02:6b8:c03:500:1:45:d181:d500; envelope-from=m43cap@yandex.com; helo=forward500c.mail.yandex.net X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 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_LOW=-0.7, 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: , Reply-To: m43cap@yandex.com Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN ARC-Seal: i=1; s=key1; d=yhetil.org; t=1682149955; a=rsa-sha256; cv=none; b=FYoPMCF2YtCmZ9H1olcA02ZQka061tnc0nu93G7uFrbCgrpPASiSfBoPmvzDkUFq0IEy0X qA51eHTWIpM7aSIvW15JYR8w0ujP2eVBwaq3xWZwOdLM2WgyNtAhgZpIpPROOpQ60BkJBn 2M+9YK1hEIHiYPB04/WEps/8nSp5wwDeY8qK42FGnVA87AtEKaj6llgNIvzeMT+c0gCnQv kK/kuIsic4JWj7Tjm8OCmpGq1+S6Hps2ursC1w8aS/Gz0Vwc9uc0RJfRpZmXndgjQCng5k lvctxnMJut6ls8RLGFb5QHFLqwnCoUUvBBX4RIxS8ni+aKqj64qrHw82tPVepg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=yandex.com header.s=mail header.b=PPLFH3k7; dmarc=pass (policy=none) header.from=yandex.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=1682149955; h=from:from:sender:sender:reply-to: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=U5m8mWlLe0T4KJMtmz6Tyffb/uWgndOykXFh9DBGdzM=; b=cek+BNKzdcVsOwQXjGq//3o8do0WMdzIZaN/Me2ewJZsDL2ZF0mhsfr8YOSuCV9fWrYLWu iab+2170iJ1jJjEF5mK/xphYME2RHuTn4zc2DGg7DOZ1jCBVquTRE0HRyldirwHqhL+XTb OQ3WgHDM0YEntAKNG/nEV9Hr+q+vxufk+HlpwKpOL2+/LJalBuY9s6P6ObKCnBkSJPcbQe 1J7wOxnMLRRmIhO9146z8Xp6sHux3zuokNMm10P5vso6JzdfmpRAR2hz4cjB0m35iUI1Be Nz28wlmB0Ihq4wnKH8Z3aa+E7p6henRn8NedrfOHqRm5gANrdgqNTe/VeWwKyw== X-Migadu-Spam-Score: -5.30 X-Spam-Score: -5.30 X-Migadu-Queue-Id: 66F091F726 X-Migadu-Scanner: scn0.migadu.com Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=yandex.com header.s=mail header.b=PPLFH3k7; dmarc=pass (policy=none) header.from=yandex.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-TUID: tZ1nWnf64nzE >>>>> Max Nikulin writes: > On 21/04/2023 23:17, Colin Baxter wrote: >> I will address the other points in your reply the next time I >> update org-mode. In the meantime, I can answer some of your other >> questions immediately. > Thanks for info. I have asked for org git branch. I am almost sure > it is main, but to be sure > git -C ~/git/org-mode branch --show-current git -C > ~/git/org-mode describe main > If the issue was caused by specific order of file changes, even in > the current state output of the following command may be used for > attempt to replay updates by git checkout + make > git -C ~/git/org-mode reflog --max-count 20 f81ba451a (HEAD -> main, origin/main, origin/HEAD) HEAD@{0}: pull --stat: Fast-forward 3c449cc43 HEAD@{1}: pull: Fast-forward 4929f0c55 HEAD@{2}: pull: Fast-forward f4446ce79 HEAD@{3}: pull: Fast-forward 7c8623be9 HEAD@{4}: clone: from https://git.savannah.gnu.org/git/emacs/org-mode.git > I assume you build it yourself. Do you run emacs binary from > source+build tree or from install tree (make install)? >From a local install-tree. > The latter > has .el.gz files instead of .el, and at least in Emacs-28 it > affects behavior of compilation of ELPA packages by package.el. > Another point is that the origin of your issue might be in > built-in version of Org. It has `org-assert-version' as > well. Perhaps there is a bug in make rules for Org in Emacs > tree. Could you, please, try the following for your *current* > emacs build? > emacs -Q -l org-agenda Only message and scratch buffers present. >> 1. emacs > Till `org-reload' C-c C-x ! at the step 10 org is not > involved. Does you init file loads some Org component or some Org > buffer is created at startup? To be sure > M-: (featurep 'org) "No match." This figures since loading org-mode is only the second load-path adjustment done by my ~/.emacs. The first is setting the path to slime. All other load-path adjustments, such as other org-mode application libraries come later after org-mode itself. > I assume that ~/git/org-mode/lisp is added to `load-path' in your > init file. Yes, via (add-to-list 'load-path (expand-file-name "~/git/org-mode/lisp")) >> 2. M-x vc-dir 3. Navigate to ~/git/org-mode. 4. + (to >> pull) 5. M-x compile 6. make clean 7. make > I am sorry for my ignorance, I usually run make from a terminal > independent of emacs. Doesn't M-x compile runs make, so I expect > it is the same as In the case of build org-mode, I first select "make clean" from the history of "M-x compile". Then I do "M-x compile" again and select "make" from the history. The effect is the same using the terminal, except the outputs are now contained in emacs buffers. > make; make clean; make > and it is a bit strange for me. >> 8. In an eshell buffer navigate to ~/git/emacs/lisp. >> Typo! I meant navigate to ~/git/org-mode/lisp. >> 9. rm *.elc > Why did you decided to manually delete *.elc files? I have lost at > which step you got the warning. I expect that "make clean" should > remove .elc files. If I don't delete the elc files in ~/git/org-mode/lisp after the first build then I do get errors. I find that a running emacs-session at this stage of the process is happy to load new org-mode .el files but not .elc files. I then repeat "make clean" and "make". Now the running emacs will load the .elc files and complete the update. >> 10. Open any org-mode file or buffer and do C-c C-x ! > `org-reload' immediately after removing of .elc files sounds > strange for me. At least since previous command was "make", not > "make clean", org-loaddefs.el should exist at this moment, so > uncompiled version should be loaded, but prefix argument should be > used to load Org uncompiled > C-u C-c C-x ! > If org has not been loaded before the step 10, then `org-reload' > should-not be necessary at all. >> 11. Return to vc-dir or eshell 12. make clean 13. make >> 15. Return to org-mode buffer and do C-c C-x ! again. >> 16. Update complete, usually with no warnings or errors. > Is org-loaddefs loaded from ~/git/org-mode/lisp? It is a sanity > check for working Org and more interesting when it is broken. I think it must be because ~/git/org-mode/ is the first org-mode found and not the org-mode within emacs itself. How can I check? > emacs -Q -L ~/git/org-mode/lisp -l org-agenda > is not affected, so the problem is solely with reloading of > updated version without emacs restart. Ok. I will do that. Colin.