From: Greg Minshall <minshall@umich.edu>
To: No Wayman <iarchivedmywholelife@gmail.com>
Cc: bzg@gnu.org, emacs-orgmode@gnu.org
Subject: Re: new org-contrib and straight.el
Date: Wed, 19 May 2021 20:36:43 +0300 [thread overview]
Message-ID: <2710160.1621445803@apollo2.minshall.org> (raw)
In-Reply-To: Your message of "Wed, 19 May 2021 00:42:15 -0400." <87im3fnx5s.fsf@gmail.com>
Nick,
> The recent changes to org-contrib's location/structure have been
> accounted for on straight's "develop" branch. Once on that branch you
> can rely on the default recipe:
thanks very much. i'll look at switching to the development branch,
freezing and thawing.
cheers, Greg
----
>
> #+begin_src emacs-lisp
> (straight-use-package 'org-contrib)
> #+end_src
>
> You can see which version of straight you're currently using via `M-x
> straight-version`.
> If you're on the "master" branch (commit e1390a9 as of this writing),
> you can update to the "develop"
> branch by adding:
>
> #+begin_src emacs-lisp
> (setq straight-repository-branch "develop")
> #+end_src
>
> prior to straight's bootstrapping snippet in your in init file.
> I recommend using the develop branch and utilizing the lockfile system
> via
> `straight-freeze-versions` and `straight-thaw-versions` to define your
> own "stable releases".
>
> Hope that helps.
> If you have any other questions or run into problems feel free to
> reach out on our issue tracker:
>
> https://github.com/raxod502/straight.el/issues/new/choose
>
> Hope that helps,
>
> Nick
>
next prev parent reply other threads:[~2021-05-19 17:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-16 2:37 new org-contrib and straight.el Greg Minshall
2021-05-19 4:42 ` No Wayman
2021-05-19 17:36 ` Greg Minshall [this message]
2021-05-19 18:07 ` No Wayman
2021-05-20 13:56 ` Greg Minshall
2021-05-21 13:23 ` No Wayman
2021-05-21 15:28 ` Greg Minshall
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=2710160.1621445803@apollo2.minshall.org \
--to=minshall@umich.edu \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=iarchivedmywholelife@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).