Nick,
thanks. i've submitted a bug report.
cheers, Greg
ps -- if anyone tried the recipe i gave before, this one seems to
actually work from a clean repository (i don't think the other did):
`(org :type git
:repo "https://code.orgmode.org/bzg/org-mode.git";
:local-repo "org"
Greg Minshall writes:
Nick,
...i have not been getting the updated org-mode info
pages with my org package.
Straight provides its own means of building/installing package
info.
This may be a bug with the Org mode recipe we provide.
Please file a bug report at:
https://github.com/raxod50
Nick,
> I've merged the develop branch into the master branch this morning,
> too. So you should be able to reap that benefit on either branch, but
> I still recommend using the lockfiles to your advantage.
thanks again.
since "we" have you on the line, i wonder if i might impose on you and
ask
Greg Minshall writes:
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.
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
>
> #+
Hi, Greg.
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:
#+begin_src emacs-lisp
(straight-use-package 'org-contrib)
#+end_src
You can see which version of straight you'r
hi, all. i use, but don't know much about, straight.el [1]. in case
it's of use to anyone, here is what is did to bring in the new
org-contrib:
(straight-use-package '(org-contrib :type git
:repo "https://git.sr.ht/~bzg/org-contrib";
