emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Greg Minshall <minshall@umich.edu>
To: Immanuel Litzroth <immanuel.litzroth@gmail.com>
Cc: TRS-80 <trs-80@isnotmyreal.name>,
	"Dr. Arne Babenhauserheide" <arne_bab@web.de>,
	emacs-orgmode@gnu.org
Subject: Re: best practices query: non-emacs packages based on tangled source
Date: Wed, 28 Oct 2020 16:25:32 +0300	[thread overview]
Message-ID: <711538.1603891532@apollo2.minshall.org> (raw)
In-Reply-To: Your message of "Wed, 28 Oct 2020 09:29:57 +0100." <CAM1nAcxciZEN8bwyx94kfwfwtgexTYHO9dO0upHzk9yMGwXwkw@mail.gmail.com>

Immanuel,

my take

> - Not possible to tangle all code going to a specified file

i'm not sure what this means.

> - Not possible to add line directives without major surgery

yes, that would be a problem (... if i were programming in,
e.g., C, etc., so *is* for other people).

> - Not all language modes do the correct thing

my *sense* here is that the level of standardization across different
babel languages in terms of which header arguments are supported, as
well as their meanings, is moderate.

one solution to this (which seems to have happened, at least to an
extent) is good per-language documentation of which header arguments are
supported, and what they mean within the context of the particular
language.

harder would be agreement and implementation of some "core set" of
header arguments/semantics on which one could count, followed by a list
of per-langugage extensions, or followed by places where "we agree to
disagree", or some such?  anyway, a lot of work.

> - No way to prevent overwriting an unchanged file

yes, i too have a hack i use for this (and, it would be nice if there
were something 'out of the box' that did this).

> - Special casing e.g. Don=E2=80=99t tangle to a file called =E2=80=98no=E2=
> =80=99.

somewhere, some how, fonts were lost. :)

cheers, Greg


      reply	other threads:[~2020-10-28 13:26 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
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 [this message]

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=711538.1603891532@apollo2.minshall.org \
    --to=minshall@umich.edu \
    --cc=arne_bab@web.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=immanuel.litzroth@gmail.com \
    --cc=trs-80@isnotmyreal.name \
    /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).