From: Colin Baxter <m43cap@yandex.com>
To: emacs-orgmode@gnu.org
Subject: Why am I being told to use "straight.el"?
Date: Fri, 21 Apr 2023 10:42:27 +0100 [thread overview]
Message-ID: <87ildpbmgs.fsf@yandex.com> (raw)
I load org-mode directly from my local copy of the org-mode git
repository and update on the fly. It works well, until today.
After an initial 'pull', 'make clean' and 'make', I 'cd' to lisp and 'rm
*.elc'. I then updated from an org-mode buffer, successfully. I 'make
clean' again followed by 'make'. I then did a further update from an
org-mode buffer. The second update was successfully loaded, and
subsequent launches of emacs cause no errors. 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
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 do not use "packages" nor "straight", so why the recommendation? My
method works perfectly well. As well as the above warning, the debugger
clicked in with an "Org version mismatch" error. The path to org-mode is
already loaded early (very early) in my ~/.emacs.
After the update, I received no further warnings or errors from emacs,
from both the active and subsequent sessions. In my opinion, all the
update warnings were essentially wrong and unnecessary. So why are
they there?
Colin.
next reply other threads:[~2023-04-21 10:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 9:42 Colin Baxter [this message]
2023-04-21 11:04 ` Why am I being told to use "straight.el"? 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
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=87ildpbmgs.fsf@yandex.com \
--to=m43cap@yandex.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).