From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Why am I being told to use "straight.el"?
Date: Fri, 21 Apr 2023 21:16:27 +0700 [thread overview]
Message-ID: <u1u5ru$ak2$1@ciao.gmane.io> (raw)
In-Reply-To: <87edodbc54.fsf@yandex.com>
On 21/04/2023 20:25, Colin Baxter wrote:
>>>>>> Max Nikulin writes:
>
> I have never used straight
That warning message is rather long and I suspect you may miss its
beginning because it was scrolled out of the warnings buffer. If so,
have a look into `org-assert-version' definition in lisp/org-macs.el or
you may try something like
emacs -Q -l org -L ~/path/to/your/org/repository/lisp -l ob-shell
> and I update my org-mode every couple of
> days. Today was the first time I received the warning.
What branch is tracked there, main or bugfix? I am unsure that it will
be possible to reproduce the issue, but the following command may shed
some light on updates history
git reflog | head -n 20
Please, specify Emacs version.
> > 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.
> > (require 'org-protocol)
>
> There is no org-protocol anywhere in my ~/.emacs.
It is not necessary org-protocol, any org file loaded before load path
is changed may cause the issue. It might be e.g. building agenda buffer
during startup.
next prev parent reply other threads:[~2023-04-21 14:17 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 [this message]
2023-04-21 14:32 ` William Denton
2023-04-21 16:17 ` Colin Baxter
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='u1u5ru$ak2$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).