emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: William Denton <wtd@pobox.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 10:32:59 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2304211030360.8135@shell3.miskatonic.org> (raw)
In-Reply-To: <u1u5ru$ak2$1@ciao.gmane.io>

[-- Attachment #1: Type: text/plain, Size: 866 bytes --]

On 21 April 2023, Max Nikulin wrote:

> 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.

If I remember right---this may be related or not---I saw this warning myself 
little while ago, but "make maintainer-clean" in the Emacs source (I track the 
development tree) and recompiling made it go away.  (I find I need to do that a 
couple of times a year, for one reason or another.)

Bill

--
William Denton
https://www.miskatonic.org/
Librarian, artist and licensed private investigator.
Toronto, Canada
CO₂: 423.25 ppm (Mauna Loa Observatory, 2023-04-20)

  reply	other threads:[~2023-04-21 14:33 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 [this message]
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=alpine.DEB.2.22.394.2304211030360.8135@shell3.miskatonic.org \
    --to=wtd@pobox.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).