From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Why am I being told to use "straight.el"?
Date: Mon, 24 Apr 2023 17:42:20 +0700 [thread overview]
Message-ID: <u25mee$12je$1@ciao.gmane.io> (raw)
In-Reply-To: <87bkjfivel.fsf@yandex.com>
> 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.
Since it is a custom emacs build, is its folder present in your PATH? Is
it the same binary as reported by the following command in emacs eshell
buffer
sh -c 'command -v emacs'
(it does not work without sh -c since it is a shell built-in)
On 23/04/2023 02:12, Colin Baxter wrote:
> > However accordingly to your description I expect that you do not
> > have Org loaded yet. If you can not load compiled org now it
> > should cause an error after emacs restart as well.
>
> Org-mode is already loaded, that is the git version of org that I am about to
> update is already loaded. If I C-j
Sorry, but I do not see any step that may cause org loaded (step 8 is
corrected):
> 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/org-mode/lisp.
> 9. rm *.elc <RET>
I failed to reproduce the issue.
I compiled and installed emacs
65735cee71c 2023-04-23 12:08:32 -0700 Jim Porter: ; Fix last change
I started from Org commit
> 7c8623be9 HEAD@{4}: clone: from https://git.savannah.gnu.org/git/emacs/org-mode.git
and then repeated for the following ones (from bottom to top)
> 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
1. emacs -L ~/src/org-mode
2. M-x eshell
3. eshell: cd ~/src/org-mode
4. eshell: git checkout f4446ce79 # etc.
5. eshell: make clean
6. eshell: make
7. C-x C-f /tmp/test.org
no error
8. C-c C-x !
should not be necessary, but no error anyway.
9. C-x C-c
repeat from step 1
prev parent reply other threads:[~2023-04-24 10:43 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
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 [this message]
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='u25mee$12je$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).