emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Nikolaus Rath <nikolaus@rath.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] error: Invalid search bound [9.6.11 ( @ /home/nikratio/.emacs.d/elpa/28.2/develop/org-9.6.11/)]
Date: Tue, 05 Dec 2023 12:51:04 +0000	[thread overview]
Message-ID: <87zfyovmmf.fsf@localhost> (raw)
In-Reply-To: <c0e357ef-84c7-48d9-9dfa-b0a7cbe46985@app.fastmail.com>

"Nikolaus Rath" <nikolaus@rath.org> writes:

>> May you please try the latest bugfix branch and let us know if you are
>> still seeing the warning?
>
> Thanks for the quick response! Could you point me in the direction of how to do that? I'm a bit confused by the layering of Emac's builtin-org, the Elpa installed one (which I seem to be using) and Spacemacs (whih I think takes over management of Emacs packages). 
>
> Should it work to clone the git branch and do "(add-to-list 'load-path "~/src/org-mode/lisp") or will this result in some terrible mess?

If you are using ELPA-devel, it will be enough to update Org mode.

Otherwise, (add-to-list 'load-path "~/src/org-mode/lisp") should do as
long as you put it early enough in your config, so that built-in Org
version is not yet loaded.
Also, see https://orgmode.org/manual/Installation.html

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


      reply	other threads:[~2023-12-05 12:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-30 10:33 [BUG] error: Invalid search bound [9.6.11 ( @ /home/nikratio/.emacs.d/elpa/28.2/develop/org-9.6.11/)] Nikolaus Rath
2023-12-04 14:53 ` Ihor Radchenko
2023-12-05  9:56   ` Nikolaus Rath
2023-12-05 12:51     ` Ihor Radchenko [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=87zfyovmmf.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=nikolaus@rath.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).