From: Greg Minshall <email@example.com> To: No Wayman <firstname.lastname@example.org> Cc: email@example.com, firstname.lastname@example.org Subject: Re: new org-contrib and straight.el Date: Thu, 20 May 2021 16:56:03 +0300 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: Your message of "Wed, 19 May 2021 14:07:17 -0400." <firstname.lastname@example.org> 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 if you might have any comment on the following: using straight.el, i have not been getting the updated org-mode info pages with my org package. in preparing to answer you, i cobbled together a possible recipe, that seems to give me the info pages. ---- `(org :type git :repo "https://code.orgmode.org/bzg/org-mode.git" :local-repo "org" :depth full :pre-build ,(list (concat (when (eq system-type 'berkeley-unix) "g") "make") "autoloads" "./doc/org.texi" "./doc/orgguide.texi" (concat "EMACS=" invocation-directory invocation-name)) :build (:not autoloads) :files (:defaults "lisp/*.el" ("etc/styles/" "etc/styles/*") "doc/*.texi")) ---- is there some better way to do this? (i think someone else on this list does get the info pages, but, iirc, without doing anything special.) cheers, Greg ps -- for anyone curious, i use it in my .emacs with : (straight-use-package `(org...) where i might normally have had : (use-package org ...
next prev parent reply other threads:[~2021-05-20 13:58 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-16 2:37 Greg Minshall 2021-05-19 4:42 ` No Wayman 2021-05-19 17:36 ` Greg Minshall 2021-05-19 18:07 ` No Wayman 2021-05-20 13:56 ` Greg Minshall [this message] 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: new org-contrib and straight.el' \ /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
Code repositories for project(s) associated with this 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).