emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Greg Minshall <minshall@umich.edu>
To: Tom Gillespie <tgbugs@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>, TEC <tecosaur@gmail.com>
Subject: Re: best practices query: non-emacs packages based on tangled source
Date: Tue, 27 Oct 2020 20:38:45 +0300	[thread overview]
Message-ID: <571606.1603820325@apollo2.minshall.org> (raw)
In-Reply-To: Your message of "Sun, 18 Oct 2020 02:01:20 -0400." <CA+G3_PNo8i8U9rOrC8BBydjEv9=LKgtJBopwX9J6vyNXdnjtXg@mail.gmail.com>

Tom,

thanks very much for your very detailed analysis and explanation of the
issues you've had.  it's taken me this long to read through it
carefully.

the issues with python source blocks [C-c C-c] versus [C-c C-v C-t] are
in fact unfortunate, as it does make it hard to develop without lots of
tangling.  (i've run into that before with Python/org, but without
really understanding what was going on.)

i mostly write R code these days, and it's pretty happy either way.
however, i also write javascript code, and while i do it for front end
(so, don't execute it inside of org mode), i suspect it has the same
issues python does of conflating file names and modules, and might
benefit from some enhancement you suggest about treating source blocks
as "things" to be imported into the running babel session (maybe an
enhancement of <<noweb>>?).

for me, my ideal will be when the org "language" is documented as an
RFC, and people have produced stand alone tanglers, so i can release
code, and others, without emacs, without org mode, can edit the "source
of truth that is the org file", and run make to tangle and build
whatever random software package i'm releasing.

again, thank you for the reply.

cheers, Greg

next prev parent reply	other threads:[~2020-10-27 17:46 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
2020-10-16 15:04 ` TEC
2020-10-18  6:01   ` Tom Gillespie
2020-10-27 17:38     ` Greg Minshall [this message]
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=571606.1603820325@apollo2.minshall.org \
    --to=minshall@umich.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=tecosaur@gmail.com \
    --cc=tgbugs@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

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).