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 18:04:11 +0700 [thread overview]
Message-ID: <u1tqjd$1vk$1@ciao.gmane.io> (raw)
In-Reply-To: <87ildpbmgs.fsf@yandex.com>
On 21/04/2023 16:42, Colin Baxter wrote:
>
> After an initial 'pull', 'make clean' and 'make',
...
> However, I did initially
> receive the following warning:
>
> --8<---------------cut here---------------start------------->8---
> It is recommended to put
>
> (straight-use-package 'org)
>
> early in the config. Ideally, right after the straight.el
> --8<---------------cut here---------------end--------------->8---
You got this warning because it is assumed that straight.el users are
mostly affected by the mixed compile/mixed load issue.
https://orgmode.org/worg/org-faq.html#mixed-install
Did you get this warning when you restarted emacs?
Next time please, save result of "ls -ltr lisp/". It sounds like some
issue with dependencies in makefiles. Perhaps something was wrong with
org-version.el, org-macs.el, org-loaddefs.el and .elc files.
Another way to get mixed versions issue is to put some require, e.g.
(require 'org-protocol)
before adding the directory to `load-path'. There are long threads on
errors due to compiling ELPA package from Emacs when old Org version is
already loaded.
next prev parent reply other threads:[~2023-04-21 11:05 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 [this message]
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
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='u1tqjd$1vk$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).