From: Richard Kim <emacs18@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Recommended way to work on main without upgrading Org?
Date: Fri, 23 Dec 2022 08:38:03 -0800 [thread overview]
Message-ID: <87r0wqm5xw.fsf@gmail.com> (raw)
In-Reply-To: 87ili2t7lk.fsf@gmail.com
Richard Kim <emacs18@gmail.com> writes:
> Karthik Chikmagalur <karthikchikmagalur@gmail.com> writes:
>
>> I can get it to work with emacs -Q as well, and this is good for testing, thank you.
>>
>> But I'm looking for a way to retain the rest of my configuration and swap out
>> Org as required. Otherwise I can't do any interactive development. Another
>> alternative is to set up a completely different init directory and run Emacs
>> with a chemacs2 profile or with the new --init-directory flag, but considering
>> the complexity/size of my configuration this would be onerous.
>
> How about specifying org version of your choice on command line like this?
>
> emacs --eval "(add-to-list 'load-path \"/path/to/org\")"
>
> So long as you don't activate another org mode package within your
> start-up files, above should work I think.
If you want to better control where your org path end up in load-path,
then you can use one of several hooks, e.g., following delays updating
load-path till almost the very end of emacs startup process
emacs --eval "(add-hook 'emacs-startup-hook (lambda () (add-to-list 'load-path \"/path/to/org\")) 100)"
See [[info:elisp#Startup Summary]] for emacs startup details.
next prev parent reply other threads:[~2022-12-23 17:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 3:19 Recommended way to work on main without upgrading Org? Karthik Chikmagalur
2022-12-22 3:51 ` Ruijie Yu via General discussions about Org-mode.
2022-12-22 4:52 ` Karthik Chikmagalur
2022-12-22 10:15 ` Max Nikulin
2022-12-23 16:20 ` Richard Kim
2022-12-23 16:38 ` Richard Kim [this message]
2022-12-23 17:07 ` Richard Kim
2022-12-22 4:22 ` Tim Cross
2022-12-22 5:02 ` Greg Minshall
2022-12-22 7:52 ` Milan Glacier
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=87r0wqm5xw.fsf@gmail.com \
--to=emacs18@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).