From: Colin Baxter <m43cap@yandex.com>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Why am I being told to use "straight.el"?
Date: Fri, 21 Apr 2023 17:17:44 +0100 [thread overview]
Message-ID: <87h6t9dxav.fsf@yandex.com> (raw)
In-Reply-To: <u1u5ru$ak2$1@ciao.gmane.io> (Max Nikulin's message of "Fri, 21 Apr 2023 21:16:27 +0700")
>>>>> Max Nikulin <manikulin@gmail.com> writes:
> On 21/04/2023 20:25, Colin Baxter wrote:
>>>>>>> Max Nikulin writes:
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.
> Please, specify Emacs version.
GNU Emacs 30.0.50 (build 1, i686-pc-linux-gnu, X toolkit, cairo version
1.14.8, Xaw3d scroll bars) of 2023-04-19.
My system is Linux 4.9.0-19-686-pae #1 SMP Debian 4.9.320-2 (2022-06-30)
i686 GNU/Linux.
>> > Did you get this warning when you restarted emacs? No.
> Then I am completely confused what happened. Org compiled by make
> should not be affected by the mixed compile issue, especially
> after "make clean". How do you load updated version without
> restarting of Emacs? Do you use `org-reload'? Please, try to
> specify all you steps from "git pull" to first time when you got
> the warning.
1. emacs <RET>
2. M-x vc-dir <RET>
3. Navigate to ~/git/org-mode.
4. + (to pull)
5. M-x compile <RET>
6. make clean <RET>
7. make <RET>
8. In an eshell buffer navigate to ~/git/emacs/lisp.
9. rm *.elc <RET>
10. Open any org-mode file or buffer and do C-c C-x !
11. Return to vc-dir or eshell
12. make clean <RET>
13. make <RET>
15. Return to org-mode buffer and do C-c C-x ! again.
16. Update complete, usually with no warnings or errors.
Colin.
next prev parent reply other threads:[~2023-04-21 17:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 9:42 Why am I being told to use "straight.el"? Colin Baxter
2023-04-21 11:04 ` Max Nikulin
2023-04-21 13:25 ` Colin Baxter
2023-04-21 14:16 ` Max Nikulin
2023-04-21 14:32 ` William Denton
2023-04-21 16:17 ` Colin Baxter [this message]
2023-04-21 19:13 ` Colin Baxter
2023-04-22 3:29 ` Max Nikulin
2023-04-22 7:51 ` Colin Baxter
2023-04-22 15:53 ` Max Nikulin
2023-04-22 19:12 ` Colin Baxter
2023-04-24 10:42 ` Max Nikulin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h6t9dxav.fsf@yandex.com \
--to=m43cap@yandex.com \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).