From: Diego Zamboni <diego@zzamboni.org>
To: Greg Minshall <minshall@umich.edu>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: best practices query: non-emacs packages based on tangled source
Date: Fri, 16 Oct 2020 16:52:45 +0200 [thread overview]
Message-ID: <CAGY83EfbikoDSCq0qyFhrDBc7EKFLU9UWsDwf0td3gYBBEJuLg@mail.gmail.com> (raw)
In-Reply-To: <1695924.1602785484@apollo2.minshall.org>
[-- Attachment #1: Type: text/plain, Size: 900 bytes --]
Hi Greg,
What I do with my Elvish modules (https://github.com/zzamboni/elvish-modules
, https://github.com/zzamboni/elvish-completions) is to just include the
Org files together with the tangled .elv files.
--Diego
On Thu, Oct 15, 2020 at 8:28 PM Greg Minshall <minshall@umich.edu> wrote:
> hi. i apologize if this has been asked before (especially if by me).
> but, since i had a question recently about Org Src... buffers, this came
> up.
>
> i'm wondering what people do who want to release a non-emacs'y package
> (an R package, say, or ...), and who did their development "from within"
> a .org file.
>
> i can "build" whatever files are needed to release the package. but,
> it's nice to be able to let people look at the sources, maybe submit
> 'pull requests', etc.
>
> if anyone has any techniques they've used, liked (or hated), i'd love to
> hear.
>
> thank you very much, Greg
>
>
[-- Attachment #2: Type: text/html, Size: 1462 bytes --]
next prev parent reply other threads:[~2020-10-16 14:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 18:11 best practices query: non-emacs packages based on tangled source Greg Minshall
2020-10-15 21:22 ` Tim Cross
2020-10-16 9:09 ` Eric S Fraga
2020-10-16 14:52 ` Diego Zamboni [this message]
2020-10-16 15:04 ` TEC
2020-10-18 6:01 ` Tom Gillespie
2020-10-27 17:38 ` Greg Minshall
2020-10-27 18:09 ` TRS-80
2020-10-27 22:28 ` Dr. Arne Babenhauserheide
2020-10-28 8:29 ` Immanuel Litzroth
2020-10-28 13:25 ` 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=CAGY83EfbikoDSCq0qyFhrDBc7EKFLU9UWsDwf0td3gYBBEJuLg@mail.gmail.com \
--to=diego@zzamboni.org \
--cc=emacs-orgmode@gnu.org \
--cc=minshall@umich.edu \
/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).