From: Greg Minshall <minshall@umich.edu>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Noboru Ota <me@nobiot.com>, emacs-orgmode@gnu.org
Subject: transclusion, tangling, flycheck/flymake, etc.
Date: Wed, 03 Nov 2021 11:15:54 +0300 [thread overview]
Message-ID: <1673748.1635927354@apollo2.minshall.org> (raw)
Ihor,
(Noboru Ota -- i do find transclusion very interesting.)
> 2. A much faster tangle system. If we can directly transclude and sync
> contents of source blocks with actual programming language buffer,
> C-c ' can trivially support flycheck-mode and provide a more
> IDE-like experience while still benefiting from literate
> programming style.
in general, i would like to keep bits of my code in a single .org file,
maybe broken into separate source blocks, with preceding/succeeding
commentary. then, pulled together in a tangle by a =:tangle= property
(within a subtree) and/or =<<noweb>>= references.
my thought about flycheck, flymake, whatever, is that (optionally) a
silent, background, =tangle= and/or =<<noweb>> expansion= would take
place to produce a "full source file buffer"[*], then the narrowed
version of that (corresponding to the part where =C-c '= was issued)
buffer is presented for the user's editing convenience.
your thought here, iiuc, is that source files would live in the file
system, and be transcluded into the .org file. i can see the utility of
that. but, i would miss =<<noweb>>= and also the ability to break the
source code into small chunks for purposes of documentation.
obviously, the two approaches are not mutually exclusive. but, partly
to make sure i understand your suggestion, i thought i'd mention it.
cheers, Greg
[*] in my scenario, i would find it convenient for the buffer the user
edits to have a file name, with the tangled file's extension; i have a
'package-in-waiting' which has to do some head standing to figure out
the appropriate language [parser] to send to a program =prettier=.
https://git.sr.ht/~minshall/prettied-diff
next reply other threads:[~2021-11-03 8:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 8:15 Greg Minshall [this message]
2021-11-03 12:01 ` transclusion, tangling, flycheck/flymake, etc Ihor Radchenko
2021-11-03 12:55 ` Greg Minshall
2021-11-06 10:55 ` Noboru Ota
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=1673748.1635927354@apollo2.minshall.org \
--to=minshall@umich.edu \
--cc=emacs-orgmode@gnu.org \
--cc=me@nobiot.com \
--cc=yantar92@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
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).